Debugging/Programming Access

RE: Debugging/Programming Access

Naeem Maroof — Wed, 24 May 2023 16:25:09 GMT

The SWO (and other) trace pins are used for tracing that collects data from ETM and ITM through TPIU.

For debugging, you use SWDCLK and SWDIO.

RE: Debugging/Programming Access

0x00 — Wed, 24 May 2023 12:38:38 GMT

Hi,

therefore the SWO, in canonical case in which we have as pgrammer/debugger a JLINK for example, is an "optional" line. Correct? ... i need to double check!

Many Thanks

RE: Debugging/Programming Access

Naeem Maroof — Wed, 24 May 2023 10:45:56 GMT

Hello,

Thank you for contacting DevZone at NordicSemi.

As per the product specification of nrf5340:

External debugger is connected to SW-DP through SWDCLK and SWDIO ports.
This SW-DP is connected to the DAP bus interconnect, and you can see that both cores (app core and the net core) are connected to the DAP bus through their respective AHB-AP.
This means that both of the core could be accessed through the debugger.

The TPIU (Trace Port Interface Unit) could be used to trace data from the ETM and ITM of the app core. It could use 4-bit wide parallel trace (TRACEDATA[0:3]) or serial trace (via SWO protocol). The dedicated trace pins (P0.08 to P0.12) are multiplexed with GPIOs and must use specified drive configurations.

Regards,

Naeem

RE: Debugging/Programming Access

0x00 — Tue, 23 May 2023 13:31:15 GMT

Probably the TRAVCE port is optional... since the AppCore is connected also to the DAP.

But a confirmation will be appreciated! :)!

Thanks again