nRF5340 Debugging using "Segger Embedded Studio" for Bluetooth related APIs

[selvam]

Hi Nordic Team,

1. Actually we try to debug "Mesh Light" sample code using "Build and Debug" option of Segger Embedded Studio..
2. Unfortunately debugging stopped at below line of API bt_enable() of hci_core.c
err = bt_dev.drv->open();
3. But by programming the "merged_domains.hex" through nRF connect programmer , able to see the only serial print message(in putty)
like "printk("BT driver opened...\n");
printk("Bluetooth initialized\n");
printk("Mesh initialized\n");

Please clarify the below queries:
1. shall we know which file will be loaded when clicking the
"Build and Debug" option of "Segger Embedded Studio"
2. Is any option present to choose the file to be loaded for debug in
"Segger Embedded Studio"

3. What is the proper option of "Segger Embedded Studio" for debugging of
blue mesh related codes?

Thanks
Selvam

[selvam]

Hi Hung Bui,

Thanks for the update.

We followed the suggested steps.

For the case of update the code (to add print messages) in network core code ,

Please suggest the steps to be followed. 

Thanks

Selvam

[Hung Bui]

Hi Selvam, 

By default the network core has logging supported. If you plan to do more modification on the network core, I would suggest to open the hci_rpmsg directly and modify the code there. You then can just compile and flash the hci_rpmsg separately (made sure you select board nrf5340dk_nrf5340_cpunet ) when you open the project. 

In the application core, you don't need to flash/combine the hci_rpmsg core any more.