Bootloader app copy dual bank

RE: Bootloader app copy dual bank

bjorn-spockeli — Tue, 26 Sep 2017 09:20:52 GMT

I tried reproducing this by starting the WDT in the bootloader during the prevalidate procedure. The WDT reset the device after 10s, but after reconnecting the DFU procedure resumed and the update was successfull. i.e. no missing pages.

RE: Bootloader app copy dual bank

Cyril — Wed, 20 Sep 2017 15:30:24 GMT

from nrt_dfu_utils.c::nrf_dfu_app_continue(), nothing happens if crc is wrong. Bank 1 is invalidated even when bank 0 is not correct, but I don't think that the best way to handle this case. Something weird also is that nrf_dfu_mbr_compare is called after each page copy from bank 1 to 0, to make sure data is correctly copied and must return an error if data is not the same... but it doesn't. Again, my memory dump showed several pages erased but not written. I have to double check if source pages are correct before copy also... maybe they are erased too.

RE: Bootloader app copy dual bank

Cyril — Wed, 20 Sep 2017 15:19:39 GMT

Yeah, I explicitly enable the watchdog in the bootloader. It uses the bootloader settings correctly but it doesn't seem to resume the copy correctly after the reset though (pages are not written). Finally, no, the copy doesn't restart.

RE: Bootloader app copy dual bank

bjorn-spockeli — Wed, 20 Sep 2017 15:00:56 GMT

Hi Cyril, if you enable the WDT in the application then you must reload it in the bootloader, but after the reset the bootloader should be able to pick up where it left of by examining bootloader settings. Also doesnt the copy procedure start over when the CRC does not match?