nrf5340 custom board not running after enabling Bluetooth (CONFIG_BT)

RE: nrf5340 custom board not running after enabling Bluetooth (CONFIG_BT)

Susheel Nuguru — Wed, 31 Jul 2024 10:12:14 GMT

Can you please attach your project here so that I could see if it is missing anything to include the net files. I think the child image is pulled from the board configuration mentioned in zephyr\boards\nordic\nrf5340dk\Kconfig->DOMAIN_CPUNET_BOARD which inturn pulls zephyr\boards\nordic\nrf5340dk\Kconfig.defconfig->BT_HCI_BUS_TYPE

RE: nrf5340 custom board not running after enabling Bluetooth (CONFIG_BT)

responsible_duck — Wed, 31 Jul 2024 06:39:36 GMT

Is there a proper sample that incorporates the net and app core? I can't seem to find one and the dev academy course only briefly covers this. Note that our custom board is already based off of /zephyr/boards/arm/nrf5340dk_nrf5340/ files

RE: nrf5340 custom board not running after enabling Bluetooth (CONFIG_BT)

Susheel Nuguru — Tue, 30 Jul 2024 10:47:40 GMT

It looks that way that the network core is not configured at all.

It should be best to take a sample as template and copy the nRF53 board folder and make changes to it to reflect to your custom board. Seems like something is missing in your configuration that says that you need a child image

RE: nrf5340 custom board not running after enabling Bluetooth (CONFIG_BT)

responsible_duck — Tue, 30 Jul 2024 09:02:42 GMT

When I try to Debug with JLink it shows this in gdb-server:

Starting target CPU...
...Target halted (DBGRQ, PC = 0xEFFFFFFE)

Debug console shows:

Thread
2 received signal SIGTRAP, Trace/breakpoint trap.
[Switching to Remote target]
0xeffffffe in ?? ()

This is just with CONFIG_BT=y and CONFIG_BOARD_ENABLE_CPUNET=y.

I am seeing this log when building, No install step for hci_ipc_subimage:

[460/471] Linking C static library app/libapp.a
[462/471] No install step for 'hci_ipc_subimage'
[463/471] Completed 'hci_ipc_subimage'
[464/471] Linking C executable zephyr/zephyr_pre0.elf
[465/471] Generating linker.cmd
[466/471] Generating isr_tables.c, isr_tables_vt.ld, isr_tables_swi.ld
[467/471] Building C object zephyr/CMakeFiles/zephyr_final.dir/misc/empty_file.c.obj
[468/471] Building C object zephyr/CMakeFiles/zephyr_final.dir/isr_tables.c.obj
[469/471] Linking C executable zephyr/zephyr.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:      415204 B       944 KB     42.95%
             RAM:      307932 B       448 KB     67.12%
        IDT_LIST:          0 GB        32 KB      0.00%
[470/471] Generating zephyr/merged.hex
[471/471] Generating zephyr/merged_domains.hex
 *  Terminal will be reused by tasks, press any key to close it.

Does that mean its not actually installing anything on the network core and that is why its not responding? I also don't see anything network core related in the Memory Report. I suspect something is wrong with how the network core or hci_ipc subimage is configured, although we tried to maintain everything close to the nrf5340 DK default configurations...

RE: nrf5340 custom board not running after enabling Bluetooth (CONFIG_BT)

Susheel Nuguru — Tue, 30 Jul 2024 05:42:29 GMT

Hi Ever,

[quote user=""]

Our project builds and flashes however as soon as the app starts the device seems unresponsive. It can be connected to in Serial Terminal but we are unable to run any shell commands or even turn on the device's LED within main(). This usually happens when we run out of RAM but we are currently at 86% usage so there seems to be enough margin...

Any thoughts on what might be going on?

[/quote]

I would first try to run the application in the debugger for a while and halt/pause the debugger to understand the context of the current execution in your application. It might give us some hints if the application is running properly on the application core or if it has asserted. Unable to get any logs can be a different issue with the device tree but we can come to that later.

Have you tried running the compiled binary with your custom board device tree on the nRF53DK in the debugger? Just a quick look at your device files does not obviously show that binary for your custom board should not run on nRF53DK. The reason I am asking to do this is because it is easy to run the debugger on the DK.