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

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

Allan P — Thu, 27 May 2021 11:51:49 GMT

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.

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

Fran89 — Thu, 27 May 2021 11:38:30 GMT

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.

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

Allan P — Tue, 18 May 2021 07:50:05 GMT

I've made it work..

I think that the programing didn't go well.

First, I programed "hci_rpmsg" on the net core, just downloaded (Target -> Download Zephyr/Zephyr.elf). I think the debugging was messing with it.
Next I did the same with the project "peripheral_lbs" on the app core.

Then I tested it with the android app and it worked well. I don't really know what I was doing wrong.

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

Mike Mascari — Mon, 17 May 2021 19:35:15 GMT

I've encountered the same issue on both the same tool-chain (nRF Connect SDK) as well as SDK v.1.5.1.