Secure DFU Bootloader debugging for nRF51822_xxAA

RE: Secure DFU Bootloader debugging for nRF51822_xxAA

Vidar Berg — Fri, 15 Dec 2017 14:28:40 GMT

Can you post another screenshot that shows the debug session in Keil (dissasembly view, source view and register view)? Also, read memory at 0x10001014 to confirm that it contains the BL start address (0x36000)

RE: Secure DFU Bootloader debugging for nRF51822_xxAA

Plutok Oleg — Fri, 15 Dec 2017 14:26:53 GMT

I tried, the result is the same.

RE: Secure DFU Bootloader debugging for nRF51822_xxAA

Vidar Berg — Fri, 15 Dec 2017 14:01:41 GMT

Yes, you can use nRFgo studio to load the softdevice. Did you load the bootlaoder with nrfgo studio / nrfjprog before you started the debug session?

RE: Secure DFU Bootloader debugging for nRF51822_xxAA

Plutok Oleg — Fri, 15 Dec 2017 13:57:17 GMT

I do erasing and programming sd through nRFgo

RE: Secure DFU Bootloader debugging for nRF51822_xxAA

Vidar Berg — Fri, 15 Dec 2017 12:22:27 GMT

Strange. Attached is the project you sent me, only modification is that I added a space between the nrfjprog arguments to allow it to program. Please try the following:

Do a full chiperase and load softdevice (nrfjprog --program s130_nrf51_2.0.1_softdevice.hex --chiperase)
Open Keil project and build the example. Then load it by clicking F8.
Start debug session

RE: Secure DFU Bootloader debugging for nRF51822_xxAA

Plutok Oleg — Thu, 14 Dec 2017 15:55:30 GMT

yes, but the result is the same

RE: Secure DFU Bootloader debugging for nRF51822_xxAA

Vidar Berg — Thu, 14 Dec 2017 15:43:41 GMT

I've not seen this issue before and it's quite puzzling considering that you are able to debug the SDK 11 example and that I'm able to debug the project you sent me. Did you try the same with a new copy of SDK 12.3.0?

RE: Secure DFU Bootloader debugging for nRF51822_xxAA

Plutok Oleg — Wed, 13 Dec 2017 19:32:56 GMT

I can not set the breakpoint at line 108 in main.c

RE: Secure DFU Bootloader debugging for nRF51822_xxAA

Plutok Oleg — Wed, 13 Dec 2017 14:04:19 GMT

"._build\nrf51422_xxac_s130.axf" - 0 Error(s), 0 Warning(s). I can not set the breakpoint

RE: Secure DFU Bootloader debugging for nRF51822_xxAA

Vidar Berg — Wed, 13 Dec 2017 13:53:33 GMT

Correct, get the following error when loading the file:

Error: Could not load file 'C:\@@@Boot12_\@@@Boot12_\examples\dfu\bootloader_secure\pca10028\arm5_no_packs\_build\nrf51422_xxac_s130.axf'. Debugger aborted !

Did you try to place the breakpoint at line 108 in main.c?

RE: Secure DFU Bootloader debugging for nRF51822_xxAA

Plutok Oleg — Wed, 13 Dec 2017 13:41:41 GMT

does not work with symbols "@"?

RE: Secure DFU Bootloader debugging for nRF51822_xxAA

Vidar Berg — Wed, 13 Dec 2017 13:40:30 GMT

Did you try to place the breakpoint at line 108 in main.c?

RE: Secure DFU Bootloader debugging for nRF51822_xxAA

Plutok Oleg — Wed, 13 Dec 2017 13:37:39 GMT

I also removed all the characters "@", but there are no changes

RE: Secure DFU Bootloader debugging for nRF51822_xxAA

Vidar Berg — Wed, 13 Dec 2017 13:05:33 GMT

Thanks. I was able to place breakpoints with your project after removing the '@' from the project path.

RE: Secure DFU Bootloader debugging for nRF51822_xxAA

Plutok Oleg — Wed, 13 Dec 2017 12:54:17 GMT

here is my complete project drive.google.com/open

RE: Secure DFU Bootloader debugging for nRF51822_xxAA

Vidar Berg — Wed, 13 Dec 2017 11:17:17 GMT

I'm afraid I'm not aware of any project configuration that can cause that. Suggest that you download a new copy of SDK 12.3.0 and only modify the linker settings, then see if you get the same result. Another alternative is if you can send me your project so I can try it here.

RE: Secure DFU Bootloader debugging for nRF51822_xxAA

Plutok Oleg — Tue, 12 Dec 2017 20:59:16 GMT

In the sources window I can't set breakpoints, but in the disassembly window I can. Debug information enabled.

RE: Secure DFU Bootloader debugging for nRF51822_xxAA

Plutok Oleg — Mon, 11 Dec 2017 20:53:10 GMT

The example from SDK 11 (bootloader) works ok, but the example from SDK 12.3 ((bootloader_secure) doesn't not.

RE: Secure DFU Bootloader debugging for nRF51822_xxAA

Plutok Oleg — Mon, 11 Dec 2017 20:13:51 GMT

I have done the experiment. Set ROM start to 0. Erase chip. Program target. No changes - in source window I cannot set traps and check where the program is at the moment in sources

RE: Secure DFU Bootloader debugging for nRF51822_xxAA

Plutok Oleg — Mon, 11 Dec 2017 16:29:27 GMT

if I step (F11) in the disassembly window, I reach the address 0x00036108, but in source window nothing changes

RE: Secure DFU Bootloader debugging for nRF51822_xxAA

Plutok Oleg — Mon, 11 Dec 2017 15:44:13 GMT

my target settings ROM: start - 0x36000 size - 0x9C00 RAM: start - 0x200025E0 size - 0x1A20

utilites settings command: nrfjprog.exe arguments: --family NRF51--program "#H"

RE: Secure DFU Bootloader debugging for nRF51822_xxAA

Vidar Berg — Mon, 11 Dec 2017 14:19:37 GMT

Hi,

Have you updated the linker configuration to ensure RAM usage is within 16K? The SDK examples are configured for the xxAC part which has 32K of RAM.

Linker configuration for xxAA part:

Also, the nRF51 programming algorithm used by Keil does not support writing the UICR where the bootloader start address is stored (@0x10001014). This may explain way the program never reaches main. Have you tried to load the FW with nrfjprog / nrfgo studio first?

Edit 12.12 Are you able to place breakpoints in the code? I'm wondering if the debug information is included in your executable. Please make sure that this option is enabled as shown in screenshot above.

Attachment:

boot.zip