Debugging nRF54L15PDK

Hi all,

I'm currently trying to setup my development environment for the nRF54L15PDK (revision 0.2.1) as we are going to use the nRF54L15 in a custom hardware.

Unfortunately, the debug experience under Windows 10 Enterprise (22H2, Build 19045.4651) is odd when I enable the BLE stack on the target (i.e. CONF_BT=y). I tried to reproduce my issues during the last days and additionally utilized Ubuntu 22.04 for my investigations.

I tried with both nRF Connect SDK & toolchain versions 2.6.1 and 2.7.0.

For nRF Connect for VS Code I tried versions v2024.7.12, v2027.7.13 and v2024.7.18.

For instance I try the zephyr\samples\bluetooth\peripheral_hr with optimization level -Og and additional CMake arguments -DCONFIG_CORTEX_M_DEBUG_MONITOR_HOOK=y and -DCONFIG_SEGGER_DEBUGMON (source Debugging in nRF Connect for VS Code).

After the debugger launched, I have to pause program execution and execute -exec monitor halt and -exec monitor reset commands manually in the debugger console.


Under Ubuntu 22.04 the debugger then acts as expected most of the time. For instance I set a breakpoint in blink_stop, continue program execution, wait a while and connect to the target via BLE with the iOS nRF Connect App. The breakpoint is hit, I step through some lines of code and continue program execution. I can repeat this over and over again.

In contrast in Windows, while performing the same steps, I most of the time get a GDB error after the breakpoint in blink_stop is hit and I execute a single step or try to continue execution.

/_w/_temp/workspace/build/.build/HOST-x86_64-w64-mingw/arm-zephyr-eabi/src/gdb/gdb/infrun.c:5825: internal-error: finish_step_over: Assertion `ecs->event_thread->control.trap_expected' failed.  

There's already a similar thread for the nRF54L15, but it's not obvious which OS is used.

Furthermore, in another thread crashing of GDB was experienced too. But SDK and toolchain versions are older and the accepted answer does not help either.

So I'm wondering, if nRF Connect (SDK, toolchain, extension) is mature enough to be used in production when it comes to the nRF54L15?

  

Best regards,
Christian

Parents
  • Hi Christian,

    the nRF54L15 is not in production yet, and neither the SoC itself nor the tools are suitable for production at this point in time. I recomend you contact sales regarding timeline for when it will be production ready if you need to know that.

    Regarding debugging issues, I reomend you continue with v2024.7.18, which is the latest preview release that I see you also tested. However, this only have experimental support for the nRF54L15 and there are issues as you have seen. We are aware of this and are workign on it.

    Br,

    Einar

Reply
  • Hi Christian,

    the nRF54L15 is not in production yet, and neither the SoC itself nor the tools are suitable for production at this point in time. I recomend you contact sales regarding timeline for when it will be production ready if you need to know that.

    Regarding debugging issues, I reomend you continue with v2024.7.18, which is the latest preview release that I see you also tested. However, this only have experimental support for the nRF54L15 and there are issues as you have seen. We are aware of this and are workign on it.

    Br,

    Einar

Children
Related