Unable to dfu bootloader nrf52

RE: Unable to dfu bootloader nrf52

bjorn-spockeli — Wed, 07 Dec 2016 10:11:45 GMT

Great! Im happy to help :) I would appreciate if you could mark the answer as correct by clicking the checkmark in the circle to the left of the answer.

RE: Unable to dfu bootloader nrf52

JosPasAl — Wed, 07 Dec 2016 10:08:28 GMT

the problem it's solved. I create a new image with the sofdecive S132V2.0.0 and the fixed legacy bootloader. I update the device with it and then dfu the S132V3.0.0+secure bootloader. Now I can update the sdk12.1 application developed.

Thanks a lot for your time Bjørn Spockeli!

RE: Unable to dfu bootloader nrf52

bjorn-spockeli — Wed, 07 Dec 2016 09:14:05 GMT

Ok, are you sure that the DFU transfer is completed, i.e. reaches 100%? Looking at the hex_dump I can see that the image in the swap area is only about 14-15kB and if the DFU was successful then it should be 24kb+112kB = 136kB.

RE: Unable to dfu bootloader nrf52

JosPasAl — Wed, 07 Dec 2016 08:29:50 GMT

I've already attached it

RE: Unable to dfu bootloader nrf52

bjorn-spockeli — Wed, 07 Dec 2016 07:39:14 GMT

Ok, could you read out the flash i.e.

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

after the DFU of the Secure Bootloader and the S132 v3.0.0 SoftDevice? (Please attach it to your question)

RE: Unable to dfu bootloader nrf52

JosPasAl — Tue, 06 Dec 2016 15:56:14 GMT

I tried with the new dfu_dual_bank.c in an fresh example of the legacy bootloader and after dfu it I can see the device. But now, when I tried to dfu the secure bootloader and SD132 v3.0.0. It happens the same as before when tried to update the fix legacy bootloader. The dfu process finishs properly but then I cannot see the device anymore.

The secure bootloader and SD132 v3.0.0. image is generated as follows:

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

RE: Unable to dfu bootloader nrf52

bjorn-spockeli — Tue, 06 Dec 2016 14:59:43 GMT

Please see this post. It explains the necessary changes that must be done to the lagacy bootloader in order to update to the new Secure bootloader on the nRF52.

Best regards Bjørn

RE: Unable to dfu bootloader nrf52

JosPasAl — Tue, 06 Dec 2016 13:34:31 GMT

Yes, that's correct!

RE: Unable to dfu bootloader nrf52

bjorn-spockeli — Tue, 06 Dec 2016 13:29:06 GMT

I apologize for the confusion, for some reason I thought you were using the nRF51. Ok, so if you flash the fixed legacy bootloader(start address 0x78000) with a programmer then you're able to update from the Legacy to the Secure bootloader? If you try to update the unfixed legacy bootloader(start address 0x7A000) to the fixed legacy bootloader(start address 0x78000) then the fixed legacy bootloader will not start after the DFU? Is this correct?

RE: Unable to dfu bootloader nrf52

JosPasAl — Tue, 06 Dec 2016 13:04:15 GMT

But I'm using the nrf52 as it says in the question title. I thing I dind't explained well.

The problem lays out when I tried to update with dfu from legacy bootloader with start address at 0x7A000 to fix legacy bootloader with start address at 0x78000. If I flash directly the fixed legacy bootloader with start address at 0x78000 with a programmer, I'm able to afterwards update to the secure bootloader adn SD132 v3.0.0.

However that's not possible If I tried to update thought dfu the fixed legacy bootloader. After the update if finished (it doesn't give any error) I'm not able to see the device in the dfu menu in the nRF toolbox app.

RE: Unable to dfu bootloader nrf52

bjorn-spockeli — Tue, 06 Dec 2016 12:54:52 GMT

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.

RE: Unable to dfu bootloader nrf52

JosPasAl — Tue, 06 Dec 2016 12:45:49 GMT

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

RE: Unable to dfu bootloader nrf52

bjorn-spockeli — Tue, 06 Dec 2016 12:43:59 GMT

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

RE: Unable to dfu bootloader nrf52

JosPasAl — Tue, 06 Dec 2016 12:18:52 GMT

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

RE: Unable to dfu bootloader nrf52

bjorn-spockeli — Tue, 06 Dec 2016 11:56:04 GMT

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?