How can I debug in Segger Embedded Studio when bootloader exists?

Question

I am using NRF52840DK with SDK15.2 to test the DFU. 
 I use Segger Embedded Studio to compile both the secure_bootloader project and ble_app_buttonless_dfu project. 
 Then I use nrfjprog to program the hex files including the setting , SD, and application .into nrf52840dk 
 and DFU works perfectly. 
 
 My Question is : 
 How can I debug in Segger Embedded Studio when bootloader exists? 
 I mean using the Debug > Go in the SES for the debugging. 
 I can debug line by line in the bootloader project after programming the merged image, 
 but I cannot debug line by line with the ble_app_buttonless_dfu project. It fail to start at "main". 
 I cannot debug the application when bootloader exist. 
 
 How to debug in Segger Embedded Studio when bootloader is used. ? 
 Thank you.

Edvin · Accepted Answer

Hello, 
 I just tested what you described, and I get the same behavior as you do. Sometimes I actually manage to debug, but when I reset, it goes back into bootloader mode. The reason for this is that the .hex file which you program with SES is a bit different than the .elf file that is used, so the CRC doesn't mach. 
 
 The solution is to use the secure_bootloader\pca10056_ble_ debug bootloader when you want to debug, which skips the CRC check. Use this for development, and switch to the non-debug bootloader for your final checks. The bootloader behaves the same, except that the CRC check is enabled. 
 
 You still need to add keys (just use the same ones as you did in the debug bootloader), and create either the bootloader settings page or perform the DFU first, in order to update the bootloader settings to go into the application. The debug bootloader still checks the other requirements for the application. 
 
 I hope that works. Let me know if it doesn't. 
 Best regards, 
 Edvin

How can I debug in Segger Embedded Studio when bootloader exists?

Top Replies