Unable to dfu bootloader nrf52

[JosPasAl]

In order to perform dfu to softdevice S132 v3 sdk12 (secure bootloader) from sdk11 softdevice S132 v2 (legacy bootloader).I've change the legacy bootloader as it it says here: devzone.nordicsemi.com/.../

The "fix_legacy_bootloader" works fine if I flash it with a programer but if I try to update with dfu OTA it doesn't work. The dfu process in nRF Toolboox Android app finish succesfully but the dfu services are not advertising. I need it because I have devices that can't be flash again.

I tried creating different zips (only bootloader / SD+bootloader) but I didn't have different results. Also, I tried to dfu the "unfix" legacy bootloader with the same Android App and it works properly, so It can't be the way of creating the image .zip or the app.

The only change I apply are the explained in the previous link:

• use the dfu_dual_bank_fix.c.
• Change the BOOTLOADER_REGION_START to 0x78000
• Change in the target options the IROM1 start adress to 0x78000 in fix legacy bootloader keil project

Do I have to change also the followings defines or not ?

#define BOOTLOADER_SETTINGS_ADDRESS         0x0007F000
#define BOOTLOADER_MBR_PARAMS_PAGE_ADDRESS 0x007E000

What I'm missing?

Thanks.

UPDATE 07/12/2016 Include flash read file in petition of Bjørn Spockeli

nrf52_hexdump.txt

[bjorn-spockeli]

Could you read out the flash after the failed DFU using the following command

nrfjprog -f nrf52 --memread 0x00000000 --n 524288 >> nrf52_hexdump.txt

and attach the nrf52_hexdump.txt file to the question?

Could you also post the command you used to create the S132 v3.0.0+Secure Bootloader firmware image?

[JosPasAl]

By failed DFU you mean after dfu the "fix_legacy_bootloader.zip" or after flash the .hex with the programmer?

Update I create the S132 v3.0.0+Secure Bootloader firmware image, it was like that:

nrfutil dfu genpkg out.zip --softdevice XXX.hex --bootloader YYY.hex --application-version 0xFFFFFFFF --dev-revision 0xFFFF --dev-type 0xFFFF --sd-req 0xFFFE

[bjorn-spockeli]

Are you trying to update from an "unfixed" Legacy bootloader that starts at 0x7A000 to a "fixed" bootloader that starts at 0x78000?

[JosPasAl]

Yes, just like that to after could update to S132 v3.0.0 and Secure Bootloader

[bjorn-spockeli]

That is not possible with the nRF51. It is only possible to update from the legacy bootloader to the secure bootloader if the legacy bootloader was flashed to the nRF51 device with a start address at 0x78000 using a programmer. This is because the bootloader start address is written to the UICR register and they cannot be altered without erasing the entire chip and then reprogramming it.