Bluetooth examples are in infinity loop

[Despair1337]

Device: nRF5340DK, PCA10095

I'm using latest nRF Connect SDK, installed by nRF Connect - Toolchain application.

I opened central_uart sample:

I added only "LOG_INF("main executed");" into the main, to see if it's seen in logs. Then I burned it and started debugging.
I have following log:

[00:00:00.004,852] <inf> central_uart: main executed!!!
[00:00:00.007,019] <inf> fs_nvs: 2 Sectors of 4096 bytes
[00:00:00.007,019] <inf> fs_nvs: alloc wra: 0, ff0
[00:00:00.007,019] <inf> fs_nvs: data wra: 0, 0

So, main was executed, but it didn't printed "Bluetooth initialized" and it does nothing right now.
I traced the issue, and the app is in infinity loop here:
bt_enable (main.c@551)
err = bt_dev.drv->open(); (hci_core.c@6559)

I traced what executes the last line, and it executes "bt_rpmsg_open" at rpmsg.c file.
It loops on while with "bt_rpmsg_platform_endpoint_is_bound".

Any ideas where can be issue? It's totally fresh untouched SDK.

Also, the same example works absolutely fine on nRF52840DK

Thanks

[Vidar Berg]

Hello,

Have you programmed the the HCI RPMsg sample onto the network core? As noted in the documentation here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_nrf5340.html#application-samples, Segger does not support automatic programming of the network core image.

Best regards,

Vidar

[Despair1337]

Dear Vidar,

I didn't knew about this. I tried to flash the HCI RPMsg via Segger, sadly, on upload, it written "no input file" for some reason. I flashed it via nrfjprog and it worked out well. Thanks