Issue merging Sofdevice + Application + DFU secure bootloader

RE: Issue merging Sofdevice + Application + DFU secure bootloader

jzumaeta — Thu, 21 Mar 2024 17:11:54 GMT

I resolved my issue. It was because I was writing configuration values to a flash memory address overlapping with the app region, causing corruption within my own app.

RE: Issue merging Sofdevice + Application + DFU secure bootloader

Sigurd — Mon, 18 Mar 2024 09:22:07 GMT

[quote user="jzumaeta"]What secure boot loader configurations do I need to worry about compared to a peripheral-only application?[/quote]

From the bootloader point of view, that should not matter much. As long as you are able to trigger DFU mode, either with button or buttonless.

RE: Issue merging Sofdevice + Application + DFU secure bootloader

jzumaeta — Tue, 12 Mar 2024 06:36:50 GMT

Hi Sigurd

Thanks for your reply.

I have some logs, but it depends on the process running on my code. So I do not think it makes sense to share them. There is also no error message from the softdevice or ble event so far.

On the other hand, suppose I have an application that works as both central and peripheral at the same time (e.g. ble_app_multirole_lesc). What secure boot loader configurations do I need to worry about compared to a peripheral-only application?

RE: Issue merging Sofdevice + Application + DFU secure bootloader

Sigurd — Mon, 11 Mar 2024 14:39:48 GMT

Hi!

Difficult to say what's going on here without more information.

Do you have any nrf_logs from the application?(either from UART or Segger RTT backend)