RE: dfu_activate_app fail to swap bank 1 to bank 0

Hung Bui — Mon, 08 Jun 2015 10:56:13 GMT

@knightmare: please correct me if I am wrong, you have modified the dfu_init, so that it set settings.bank_0 = BANK_ERASED; at the begining, regardless if the image is actually tranmistted or not ? Could you explain the purpose for doing that? You won't be able to fallback to original application if there is smth wrong when updating.

It's pretty strange that adding a delay fixed the issue. Please be noted that in our code we will wait (for BOOTLOADER_COMPLETE) until the pstorage has finished with storing the bootloader setting has finished before it trigger a reset, as in pstorage_callback_handler. And bootloader setting is only stored after we have finished with storing code with pstorage_raw_store().

So if you can have a breakpoint at m_update_status = BOOTLOADER_COMPLETE; in pstorage_callback_handler() you can check if bank0 is copied with correct image.

Could you send us your bootloader, hex file before and after application update ?

Do you have the same issue with the stock bootloader example ?

RE: dfu_activate_app fail to swap bank 1 to bank 0

knightmare — Wed, 03 Jun 2015 04:23:45 GMT

Our device have left no j-link interface to customer, so the failure just sentences the device to death. We have stopped manufacturing and it will not be restarted until the problem is targeted and solved.