Upgrade SDK11 to SDK15 - MBR

RE: Upgrade SDK11 to SDK15 - MBR

bart — Thu, 10 Oct 2019 08:07:17 GMT

For archiving reasons: it went wrong because we used to run:

objcopy -Iihex -Obinary s132_nrf52_2.0.0_softdevice.hex softdevice_mainpart.bin

which fills gaps with 00. It should've been:

objcopy --gap-fill 0xFF -Iihex -Obinary s132_nrf52_2.0.0_softdevice.hex softdevice_mainpart.bin

RE: Upgrade SDK11 to SDK15 - MBR

bart — Thu, 10 Oct 2019 07:20:04 GMT

I think something went wrong when i uploaded the SDK11 softdevice, if I use nrfjprog, the end of the page are all FF instead of 00, so then my whole problem is gone.

Thanks for the help!

RE: Upgrade SDK11 to SDK15 - MBR

bart — Wed, 09 Oct 2019 15:02:43 GMT

Seems you're at the right track: m_fs.end_addr = 0, so m_fs.start_addr becomes a very large number.

The reason end_addr is 0, is because BOOTLOADER_ADDRESS = 0

Which is 0, because the old MBR ends with all 00s instead of FFs, so MBR_BOOTLOADER_ADDR = 0

Is that correct?

RE: Upgrade SDK11 to SDK15 - MBR

Hung Bui — Wed, 09 Oct 2019 12:02:17 GMT

Hi Bart,

I assume the hardfault inside fds_init() is with the application, not related to the bootloader code.

I don't think the MBR would affect the fds, however it could be the issue with where the fds/fstorage flash area should be located. The fstorage flash area usually located right under the bootloader as calculated with flash_end_addr().

You may want to step into the code and check what flash_end_addr() return.

Also if the area that the fstorage located has some data from the previous application that doesn't fit with fds it will throw some error, most likely FDS_ERR_NO_PAGES, you may want to double check.