Updating Softdevice with custom bootloader

RE: Updating Softdevice with custom bootloader

Einar Thorsrud — Wed, 25 Sep 2024 10:36:09 GMT

[quote user="marklander"]It means good? :) or bad?[/quote]

Sorry, that was I typo (I have fixed it in my previous post). It hsould be "good" 🙂

[quote user="marklander"]so I could keep the same MBR also to update SD, just need to remove the first 0x1000 part of the .hex file. Right?[/quote]

Yes, that is correct.

RE: Updating Softdevice with custom bootloader

marklander — Wed, 25 Sep 2024 10:03:09 GMT

[quote userid="7377" url="~/f/nordic-q-a/114891/updating-softdevice-with-custom-bootloader/503669"] I would say it is a bood idea[/quote]

It means good? :) or bad?

I suppose it was good...so I could keep the same MBR also to update SD, just need to remove the first 0x1000 part of the .hex file. Right?

RE: Updating Softdevice with custom bootloader

Einar Thorsrud — Wed, 25 Sep 2024 07:46:24 GMT

Hi,

Yes, I would say it is a good idea to protect the MBR page with BPROT. It should never be overwritten. This is done in our example bootloader (which also protects itself with BPROT before starting the application).

To be clear, when you do DFU of a new SoftDevice that will should not contain the MBR, so you must strip out the first page of the SoftDevice hex file. This is done by our tools for use with the example bootloader, and you must do the same for your custom bootloader if updating the SoftDevice. The MBR remains in place, and is responsible for copying in place the new bootloader in case of bootloader updates.

RE: Updating Softdevice with custom bootloader

Menon — Mon, 23 Sep 2024 18:22:39 GMT

Hello,
Most of the engineers who work with our old SDK are currently in a workshop and will be available the day after tomorrow. At that time, the ticket will be reassigned to someone with more expertise in the old SDK. We apologize for the inconvenience and appreciate your patience.

Kind Regards,

Abhijith