nRF5340-DK - Stuck in bt_enable forever (nRF Connect SDK) (SES)

[Allan P]

Hello,

I'm trying to use the nRF5340 and got some trouble with the nRF Connect SDK (installed from nRF Connect and working with SES).

Working on the development kit (nRF5340-DK) and no problems with a project like blinky.

When using BLE template the app core got stuck in “bt_enable()”. Same problem with all template (for example : beacon).

I tried to program the “hci_rpmsg” project on the net core, but the debugger is not working on this core
After programing nothing has changed for the app core (got stuck again in bt_enable).

I'm not familiar with Zephyr and the new SDK and i'm starting to turn around.

I founded this topic : https://devzone.nordicsemi.com/f/nordic-q-a/60684/nrf5340-pdk---debugger-in-ses-remains-in-bt_enable-forever

But the solution was no help.

###  ###  ###  ###
OS : Windows 10
nRF Connect SDK installed from the nRF Connect app (Toolchain Manager) (SDK v1.5.0)
Working with SES
###  ###  ###  ###

I hope someone can help me.
Have a nice day.

[Fran89]

I have the same issue. "beacon" is not working when you compile and download the firmware. According to the debugger, is stays in bt_enable() forever.

The fix of the other thread didn't work either for me. v1.5.1, and I just unboxed the nRF5340-DK.

Can't find the "Test beacon" with the nRF Connect app.

The verified answer didn't work for me either.

[Allan P]

When you build your project, there is multiple ".hex" file. Try programming the "merged_domain.hex" (in zephyr folder inside of your project folder)

This file contains both net core and app core. You must program it with the nRF Programmer.

After that you can edit your code and run it from SEGGER.

This solution is working for me in V1.5.1.