As far as I can tell, there is no secure bootloader in SDK11, so it is not trivial. It depends on how much time you want to spend on it.
I guess you should look into updating the bootloader (via DFU) to the secure bootloader in SDK 12.3.0). After that, it is not trivial, because you need to change the bootloader start address in UICR. So you need an "in between bootloaders-bootloader" that does this. But it is possible. WARNING: However, if you loose power at the wrong point in time during this, you may brick the device.
I think you need to ask yourself whether this is something you want to spend time on. Is it a product that is out in the field? Or hobby devices in your home?
I gave it a go, but I am not familiar with the bootloader from SDK11 (legacy bootloader). Are you able to update the bootloader itself (to the same bootloader, just change something in the bootloader code, and try to update to this new bootloader)?
Can I use the latest nrfutil 6.1.0 tool to generate the DFU zip file for the dual_bank_bootloader in SDK11 ?
If yes, do I need to keep the --hw-version and --bootloader-version same with the old firmware, which needs to be updated? Because, I lacked its information off, only have .hex file.
Can I use the latest nrfutil 6.1.0 tool to generate the DFU zip file for the dual_bank_bootloader in SDK11 ?
If yes, do I need to keep the --hw-version and --bootloader-version same with the old firmware, which needs to be updated? Because, I lacked its information off, only have .hex file.
Sorry for the late reply. When you mark an answer as the verified answer, the ticket is closed, and it doesn't open even though a new comment/question is posted in this ticket.
Nhuan said:
Can I use the latest nrfutil 6.1.0 tool to generate the DFU zip file for the dual_bank_bootloader in SDK11 ?
I think so, but I have not tested. You need to use the flag --no-backup. Look it up by using the command nrfutil pkg generate --help.
If it doesn't work, it may be that the old bootloaders are deprecated in the later versions of nrfutil. If so, please try to use the version that you used when SDK 11 was the latest SDK (the version that you used when you implemented your bootloader).
--hw version and --bootloader version should be the same as the ones you used before.
Nhuan said:
Because, I lacked its information off, only have .hex file.
Do you know who wrote the applications back in the day? I believe the easiest is to ask the people who used the bootloader in your company.
I notice that nRF Connect for Desktop and nrfutil 6.1.0 can not be used to transfer the DFU image, because the bootloader from SDK11 used a different UUID than the later SDK's bootloaders.
