Logging via SWO

RE: Logging via SWO

Kenneth — Thu, 23 Apr 2026 14:42:02 GMT

Hello,

Since you are debugging I don't expect current consumption is much important, does enabling CONFIG_SOC_NRF_FORCE_CONSTLAT=y help? Then you should be able to use k_msleep() instead of spin_wait_ms().

Kenneth

RE: Logging via SWO

dp-hqv — Mon, 20 Apr 2026 06:47:53 GMT

Hi Marte,

1. I use the config CONFIG_LOG_MODE_IMMEDIATE=y. The thing is that the logs are not truncated, they are sent among other random bytes (not printable), it can be seen in the `hello_world_sleep.sal` attached to my previous comment.

2. I get it, thanks.

Best Regards,
Damian

RE: Logging via SWO

Marte Myrvold — Thu, 16 Apr 2026 19:28:29 GMT

Hi Damian,

1. It is likely caused by the HF clock being turned off when k_msleep() is called. The logging module uses deferred logging, so when LOG_INF() is called, the message is not sent immediately. Instead, it is queued and sent later by the logging thread. After the logging thread finishes writing all the bytes into the ITM FIFO (with ITM_SendChar()), the CPU goes to sleep. But the TPIU is still slowly serializing those bytes out over the SWO wire, and when the CPU sleeps, HFCLK is gated, cutting power to the TPIU mid-transmission, causing the message to be truncated.

With a spin wait, the CPU stays awake, and HFCLK stays on, so the TPIU always finishes transmitting before sleep.

I recommend using deferred logging, but you can log immediately instead of queuing logs by enabling CONFIG_LOG_MODE_IMMEDIATE.

2. No, this is not possible. CONFIG_LOG_BACKEND_SWO must be enabled at build time to include the backend code. This includes log_backend_swo_init(), which enables ITM and TPIU on boot.

Best regards,
Marte

RE: Logging via SWO

dp-hqv — Wed, 15 Apr 2026 12:21:15 GMT

Hi Marte,

The debugger I use is SEGGER J-Link Base.

The reason behind using SWO is that in our project we would like to have two builds: release and test. Release one uses SWO log backend but the application does not enable SWO. It can be enabled and set up by the attached debugger when needed.
Test build which is used for measuring power consumption. Here the enables SWO by itself. No debugger is attached, only one wire to the SWO pin to gather the logs.

I have an update regarding the logs in SEGGER J-Link SWO Viewer, I can get the logs, I just had to power cycle the target device. So after the reboot the logs are received. Setting `CONFIG_LOG_BACKEND_SWO=y` was enough. My apologies, it was my mistake.

Nevertheless, the logs look corrupted. When running the simple application (from the code snippet above) every couple of lines of logs the ending of the line is incorrect.

*** Booting nRF Connect SDK v3.2.1-d8887f6f32df ***

*** Using Zephyr OS v4.2.99-ec78104f1569 ***

Hello World! hcm200/nrf54l10/app

Hello World! hcm200/nrf54l10/cpuapp

Hello World! hcm200/nrf54l10/app

Hello World! hcm200/nrf54l10/p

Hello World! hcm200/nrf54l10/cuapp

Hello World! hcm200/nrf54l10/uapp

Hello World! hcm200/nrf54l10/puapp

The correct ending should be `cpuapp`.

I have attached a logic analyzer to SWO pin to see what really is happening on the wire. It occurs, there is unexpected data sent via SWO. Here are the waveforms:

devzone.nordicsemi.com/.../hello_5F00_world_5F00_sleep.sal

I modified the application so that it does not use `k_msleep` function but a spin wait instead, like this:

static void spin_wait_ms(int64_t duration_ms)
{
    const int64_t start_ms = k_uptime_get();

    while ((k_uptime_get() - start_ms) < duration_ms) {}
}

After that the logs look correctly. The waveforms:

devzone.nordicsemi.com/.../hello_5F00_world_5F00_spin.sal

It has been run on a custom board with nRF54L10 SoC on it.

I have the following questions:

1. Do you know why the logs are corrupted when using a sleep function in the code?
2. Is there a way to use SWO log backend in Zephyr/NCS but not enabling SWO? Only the debugger would enable it when attached. It would save some power when the debugger is not attached.

Best Regards,
Damian

RE: Logging via SWO

Marte Myrvold — Tue, 14 Apr 2026 17:01:47 GMT

Hi Damian,

What debugger are you using? The debugger must be SWO capable to work.

Is there a specific reason for using SWO instead of RTT?

Best regards,
Marte

RE: Logging via SWO

dp-hqv — Tue, 14 Apr 2026 08:19:11 GMT

Hi Marte,

Thanks for clarifying how the board configurator works and what it does.

I have added the above code snippet but it did not help. I still cannot see the logs in SEGGER J-Link SWO Viewer.

Best Regards,

Damian

RE: Logging via SWO

Marte Myrvold — Fri, 10 Apr 2026 17:48:11 GMT

Hi Damian,

The board configurator tool configures the board controller (interface MCU) on the DK itself, it does not configure the nRF54L chip. This means what you want to replicate in firmware is the trace port enablement on the nRF54L chip itself, not the DK board controller configuration.

For the nRF54L, the following sequence is required to enable SWO support:

/* Trace configuration */
#define TRACE_PORT                  NRF_P2_S
#define TRACE_TRACECLK_PIN          (6ul)
#define TRACE_TRACEDATA0_PIN        (7ul)
#define TRACE_TRACEDATA1_PIN        (8ul)
#define TRACE_TRACEDATA2_PIN        (9ul)
#define TRACE_TRACEDATA3_PIN        (10ul)
#define TRACE_PIN_CONFIG            ((GPIO_PIN_CNF_DRIVE0_E0 << GPIO_PIN_CNF_DRIVE0_Pos) \
| (GPIO_PIN_CNF_DRIVE1_E1 << GPIO_PIN_CNF_DRIVE1_Pos) \
| (GPIO_PIN_CNF_DIR_Output << GPIO_PIN_CNF_DIR_Pos))

#define TRACE_PIN_CLEAR             (~(GPIO_PIN_CNF_CTRLSEL_Msk | GPIO_PIN_CNF_DRIVE0_Msk | GPIO_PIN_CNF_DRIVE1_Msk | GPIO_PIN_CNF_DIR_Msk))
/* End Trace configuration */


// Enable trace and debug
NRF_TAD_S->ENABLE = TAD_ENABLE_ENABLE_Msk;

// Configure trace port pads
TRACE_PORT->PIN_CNF[TRACE_TRACECLK_PIN] &= TRACE_PIN_CLEAR;
TRACE_PORT->PIN_CNF[TRACE_TRACEDATA0_PIN] &= TRACE_PIN_CLEAR;

TRACE_PORT->PIN_CNF[TRACE_TRACECLK_PIN] |= TRACE_PIN_CONFIG;
TRACE_PORT->PIN_CNF[TRACE_TRACEDATA0_PIN] |= TRACE_PIN_CONFIG;

// Configure trace port speed
NRF_TAD_S->TRACEPORTSPEED = TAD_TRACEPORTSPEED_TRACEPORTSPEED_DIV2;

However, this should automatically be set when you have SWO enabled with CONFIG_LOG=y and CONFIG_LOG_BACKEND_SWO=y as you can see from these files:

https://github.com/nrfconnect/sdk-zephyr/blob/main/modules/hal_nordic/nrfx/CMakeLists.txt#L116

https://github.com/nordicsemi/nrfx/blob/master/bsp/stable/mdk/system_nrf54l.c#L260-L278

Since this is not working in your case, can you try manually enabling SWO using the code above? If this does not work, please let me know.

Best regards,
Marte

RE: Logging via SWO

dp-hqv — Fri, 10 Apr 2026 06:08:34 GMT

Hi Marte,

Unfortunately, the version of my DK is 0.9.1.

Do you know how to enable SWO on a custom board with nRF54L10 SoC? I am asking about nRF54L10 since in our project we use our custom board with this SoC and we have exactly the same issue with SWO as described above for nRF54L15-DK.

Best Regards,

Damian

RE: Logging via SWO

Marte Myrvold — Thu, 09 Apr 2026 20:05:25 GMT

Hi Damian,

You need to enable SWO control in the board configurator:

Please note that this is only supported on nRF54L15 DK v1.0.0 and newer.

Best regards,
Marte