Initializing nRF52832 Over the air

RE: Initializing nRF52832 Over the air

pressure_sensor_nonconn_adv — Mon, 07 Nov 2022 12:49:14 GMT

Oh, yes what I meant is that the Bootloader settings and the MBR settings are changing upon a bootloader update. (at 0x7E0000 and 0x7F0000)

This happens even when the BL should be the same.

Ok I will try to debug the Bootloader over RTT.

RE: Initializing nRF52832 Over the air

Edvin — Mon, 07 Nov 2022 11:55:14 GMT

[quote user="pressure_sensor_nonconn_adv"]

should the bootloader settings at 0x7E0000 get changed upon an nRF bootloader update?

[/quote]

Yes.

[quote user="pressure_sensor_nonconn_adv"]does the change of the MBR upon a BL update imply that the BL writes into the wrong location?[/quote]

The MBR should not change. Are you sure that it does? Remember that the MBR is located from 0x00000000 to 0x00001000. Is that changing? Or are you talking about the MBR settings page? Because that will change.

Try to debug your bootloader. Or you can test with the _debug bootloadert (SDK\examples\dfui\secure_bootloader\<whatever_bootloader_you_are_using>_debug

And monitor the RTT log. It should state whats happening.

Best regards,

Edvin

RE: Initializing nRF52832 Over the air

pressure_sensor_nonconn_adv — Mon, 07 Nov 2022 09:37:01 GMT

Thank you for the response, Edvin.

I can update the RIGADO bootloader OTA with an nRF bootloader and softdevice S132 v7.0.1 from SDK16. The problem arises when I try to update the bootloader a second time OTA or over UART. At this point the bootloader settings get changed.

- should the bootloader settings at 0x7E0000 get changed upon an nRF bootloader update?

- does the change of the MBR upon a BL update imply that the BL writes into the wrong location?

RE: Initializing nRF52832 Over the air

Edvin — Mon, 07 Nov 2022 09:04:48 GMT

Hello,

[quote user=""]

Do I need to send a settings.hex file over nRF_DFU and if yes how can I do it?

[/quote]

No,

[quote user=""]Do I need to write into the MBR and if yes how can I do it OTA or by modifying the Bootloader?[/quote]

No,

The settings.hex files are only used if you program the application using a programmer directly, and not over DFU. When you perform a DFU then the bootloader will generate the settings file on it's own.

The MBR never (!) changes. The MBR is part of the softdevice, but even if you update the softdevice, the MBR is constant in all versions, and is not updated when you perform a softdevice update.

If you were using a normal bootloader from our SDK, I would be able to help you more, but I don't know what Rigado has done in their bootloader. I think you need to reach out to them to see if they have done anything custom in their bootloader project. For all I know, they could have forbidden/limited the bootloader to update itself.

Best regards,

Edvin