nRF54L15 blinky will not return from k_msleep()

[Ryan S]

Hi, 

I am currently developing on the BL54L15 Ezurio development kit with the Nordic chip. 

I am using the Nordic v3.0.1 SDK and toolchain with the new manufacturer board files from the zephyr repository https://github.com/zephyrproject-rtos/zephyr/tree/main/boards/ezurio/bl54l15_dvk

I have tried both the blinky and button sample - but code execution seems to stop when reaching the k_msleep() function. I have not had this issue with the nRF54L15 development kit using the same SDK and toolchain.

When I try to enter debug mode (following the usual way outlined in the dev academy course) - I get the following message: 

'Unable to start debugging. GDP exited unexpectedly with exit code -3 (0xFFFFFFFD). Could not connect to target. No target voltage detected or connection failed.'

I understand that nordic is not responsible for manufacturing this board - however I was wondering if you could suggest any starting points for debugging the fault in k_msleep in case there is an error in the board files or hardware. 

Thank you very much. 

[Ryan S]

Figured out the issue. 

For anyone who has the same devkit, make sure you enable the following config:

# Start SYSCOUNTER on driver init
CONFIG_NRF_GRTC_START_SYSCOUNTER=y

It seems to be missing from bl54l15_dvk_nrf54l15_cpuapp_defconfig on the current zephyr repo.

[H. Dekker]

Hi Ryan,

Thanks a lot for sharing your findings!

I'm currently testing on the Raytac AN54L15Q-DB (raytac_an54l15q_db) and I ran into the exact same issue you described — although in my case it happened while using just the k_sleep() function. It's a bit unfortunate that this behavior and the required configurations are not better documented.

I also added the following line to my prj.conf file:

# Start SYSCOUNTER on driver init 
CONFIG_NRF_GRTC_START_SYSCOUNTER=y

After doing that, everything works perfectly on the Raytac AN54L15Q-DB!

Thanks again for pointing this out!

Best regards,
Herke