SDK 16 S332 Bootloader

[brian]

Hi

After getting  SDK16 , we have tried to load a combined hex file with  bootloader + S132 V7 + application with dfu + bootloader setting page to PCA10040. And It work well, dfu is ok. 

And then We update bootloader and application form S132 to S332. It seems working well, while only programming bootloader and S332. but If we load a combined hex file with bootloader,softdevice,applcation,and bootloader setting page, It can't work, application isn't advertising. But If we debug the application( with S332 and bootloader), then it work well. Is there any setting we miss? We also use nfjprog --readregs to get register value while program stuck. The PC is 0x0003AB02 and check with map file, It is stuck at

_do debug_operation

0x000000000003aae8 __do_debug_operation
0x000000000003ab18 __text_end__ = (__text_start__ + SIZEOF (.text))
0x000000000000a744 __text_size__ = SIZEOF (.text)
0x000000000003ab18 __text_load_end__ = __text_end__

Brian

[smackenzie]

If you open the individual hex files, can you see any sections that are outside of the flash region?

I remember having a similar issue where the bootloader had a section defined in the UICR region. Removing that part from the hex file allowed it to be used in updates.

[brian]

Hi smackenzie

Thanks for your reply.

It seems no section overlay with UICR in bootloader hex file. I have attached both bootlaoder  and application  hex file.

Brian

ble_ant_app_hrm_pca10040_s332.hexsecure_bootloader_ble_s332_pca10040_debug.hex

[smackenzie]

I think the bottom of the bootloaders hex file is outside of flash. Specifically

:04DB080008D9070031
:020000020000FC
:020000041000EA
:0410140000200700B1
:0410180000E00700ED
:0400000370002379ED
:00000001FF

[Einar Thorsrud]

Hi Brian,

I have some questions since I am not entirely sure how to interpret what you do.

• You write that "If we load a combined hex file with bootloader,softdevice,applcation,and bootloader setting page, It can't work, the application isn't advertising". Does this mean that you merge everything together, and then upload via a debugger and try to run it, and hen it fails?
  • So there is no DFU in the loop here?
  • And then by just attaching a debugger and starting a debug session it works, with the exact same content in flash?

By the way, the bootloader .hex file you uploaded seems reasonable to me. Also, any content in the bootloader .hex for the UICR (typically bootloader start address), will be stripped away by nrfutil when it generates the DFU zip package, so it should not cause problems.

Einar

[brian]

Hi smackenize

So I need to modify section placement of bootloader?

Brian