IoT Hardware Hacking: Debug Hacks (JTAG and SWD) | EXPLIoT

JTAG and SWD are debugged peripherals for a microcontroller. Attacking these ports can get your sensitive data from a device.
In this webinar, our speaker Yashodhan Mandke covered,
Basics of JTAG and SWD
-Security issues with JTAG and SWD
-Finding out JTAG and SWD pins on IoT device
-Use EXPLIoT tools to identify debug port pins and extract data from the device
ENROLL NOW:
training.expli...
A special discount awaits the first few Learners.
Ready to become a leading professional in the world of IoT security?
Our training programs offer a wide range of courses to help you reach your full potential.
From basics to the most advanced techniques, we've got you covered.
Plus, with an emphasis on practical knowledge and hands-on experience, you will be able to apply your skills in real-world scenarios.
By joining us, you will not only gain expertise and proficiency, but also the confidence to excel in your career and stand out in the world of IoT security.

[@bennguyen1313]

I'm interested in streaming/tracing.. but the segger low-end debuggers say they support SWV (SWD+SWO) but only their TRACE debuggers support ITM, ETB, or MTB.. what's that?
To add to the confusion, there's also
ITM: Instruction Trace Macrocell: 32 32 bit registers that output data to the outside world using SWV.
Trace Port: A 4 bit port (4 data and 1 clock) that ULINKpro uses to collect ETM frames and optionally SWV (rather via the SWO pin). What pins are these?
ETM: Embedded Trace Macrocell: Provides all the program counter values. Only ULINKpro provides ETM
What about the requirements of the chip.. does it only need to SWV?
And what is the requirement for the software-layer that talks to the debug adapter? Would Eclipse + GDB/OpenOCD support trace/streaming?