DFU Bootloader with S340 Softdevice

RE: DFU Bootloader with S340 Softdevice

dragilla — Tue, 30 Nov 2021 14:22:19 GMT

I didn't. To be honest I'm more interested in the mobile app DFU. I was only testing on my computer, because it seemed a faster / easier method (no need to transfer the zip to the phone).

So thank you for your help so much. I think we can close this topic.

RE: DFU Bootloader with S340 Softdevice

Einar Thorsrud — Tue, 30 Nov 2021 13:30:18 GMT

I see. Did you look more into the debugger issue where you did not see the type field? Make sure you test with optimization disabled if you have not done so allready, as that will make debugging easier. The type should have been 2. Can you also check the handle and op fields, so that we can see if that makes sense?

RE: DFU Bootloader with S340 Softdevice

dragilla — Tue, 30 Nov 2021 13:05:20 GMT

No. I don't use bonding.

RE: DFU Bootloader with S340 Softdevice

Einar Thorsrud — Tue, 30 Nov 2021 12:51:22 GMT

Do you use DFU with bonding by any chance, and if so, could it be that you bond when you test on the phone but not when you test with nRF Connect for desktop?

RE: DFU Bootloader with S340 Softdevice

dragilla — Mon, 29 Nov 2021 16:25:31 GMT

Ok. I don't know why, but it doesn't work from "BLE" app (NRF Connect suit), but it does when I use the nRF Tools on my mobile. New firmware is installed and boots up.

Should I do something extra on the BLE app?

RE: DFU Bootloader with S340 Softdevice

dragilla — Mon, 29 Nov 2021 14:40:24 GMT

When I click on "Start DFU", the app goes to ble_dfu_buttonless_on_ble_evt, then to on_rw_authorize_req

and there it does not reach the code in the "iffs". p_auth_req->type is empty... hm

This is how it looks:

RE: DFU Bootloader with S340 Softdevice

Einar Thorsrud — Mon, 29 Nov 2021 13:08:40 GMT

Hi,

Good, then the bootloader is there and RTT logging is present in the bootloader and you should see it again after reset.

Probably that does not occur, then. With that, I suggest going back to debugging you reapplication (enable RTT in the app for this to make it easier, and disable RTT logging in the bootloader). Is an error handler reached? Or what else happens when it is supposed to enter DFU mode? You should be able to see this from debugging, hopefully you should get much just from observing the log with a debug build.

RE: DFU Bootloader with S340 Softdevice

dragilla — Mon, 29 Nov 2021 12:09:20 GMT

Ok. It's like I said. When I turn off logging in my app, I can see logs from the bootloader, but they only show when I start app. Then I try to "start the DFU" it goes "initializing" and restarts... but I'm no loonger sure it does, because the log is silent from the moment the app started the first time.

The log from the first boot below:

00> <info> app: Inside main
00> 
00> <debug> app: In nrf_bootloader_init
00> 
00> <debug> nrf_dfu_settings: Calling nrf_dfu_settings_init()...
00> 
00> <debug> nrf_dfu_flash: Initializing nrf_fstorage_nvmc backend.
00> 
00> <debug> nrf_dfu_settings: Using settings page.
00> 
00> <debug> nrf_dfu_settings: Copying forbidden parts from backup page.
00> 
00> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
00> 
00> <info> nrf_dfu_settings: Backing up settings page to address 0xFE000.
00> 
00> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
00> 
00> <debug> app: Enter nrf_bootloader_fw_activate
00> 
00> <info> app: No firmware to activate.
00> 
00> <debug> nrf_dfu_validation: CRC check of app failed. Return 1
00> 
00> <debug> app: App is valid
00> 
00> <info> nrf_dfu_settings: Backing up settings page to address 0xFE000.
00> 
00> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
00> 
00> <debug> app: Running nrf_bootloader_app_start with address: 0x00001000
00> 
00> <debug> app: Disabling interrupts. NVIC->ICER[0]: 0x0
00>

RE: DFU Bootloader with S340 Softdevice

dragilla — Mon, 29 Nov 2021 11:58:33 GMT

Ok. But it does not get to the bootloader... I think. I mean it does the first time, when there is no app. Then I can connect to it and upload a zip with my app. Next when I connect to my app and try the DFU it reboots back to my app. I will check what you wrote though. Thanks

RE: DFU Bootloader with S340 Softdevice

Einar Thorsrud — Mon, 29 Nov 2021 11:50:02 GMT

Your application or the bootloader? You need to build the _debug version of the bootloader, which has RTT logging. I also suggest you disable RTT logging in the application (if you use it) while testing this, as if not you can get problems with the RTT viewer (it searches for a n RTT buffer in memory, and if it finds the RTT buffer from the application before the bootloader that will be used, even though the bootloader may have it's RTT buffer located at a different place in RAM).

RE: DFU Bootloader with S340 Softdevice

dragilla — Mon, 29 Nov 2021 10:30:59 GMT

I have it compiled with debug and I use RTT. There's nothing there :(

RE: DFU Bootloader with S340 Softdevice

Einar Thorsrud — Mon, 29 Nov 2021 10:29:14 GMT

Hi,

I did not see any questions related to buttonless other than the statement that you want to use it.

[quote user="dragilla"]What I can say in addition is that the app does not go into the ble_dfu_evt_handler. It just resets.[/quote]

If it "just resets" then something is resetting. An error handler perhaps? Have you attempted to make a debug build (with DEBUG defined) and logging enabled? If so, you should easily see that. Generally, the buttonless DFU mechamism is very simple, by just writing a magic work to GPREGREG and performing a soft reset. Then the bootloader checks GPREGRET for the magic word - and if it is present, it enters DFU mode.

RE: DFU Bootloader with S340 Softdevice

dragilla — Mon, 29 Nov 2021 10:26:28 GMT

Hi, Thanks for your answer. This part of my question is clear. Can you please address the other part (buttonless dfu app does not work).

What I can say in addition is that the app does not go into the ble_dfu_evt_handler. It just resets.

PS: I also implemented parts of the power management example app into my app, which I think might be in conflict.

RE: DFU Bootloader with S340 Softdevice

Einar Thorsrud — Mon, 29 Nov 2021 09:17:59 GMT

Hi,

[quote user=""]what should be changed? Are there major differences between 140 and 340?[/quote]

Assuming the S340 SoftDevice you are using is the same major version as the S140 version and you only use a BLE bootloader in both cases, the API etc. is the same (so not just the nrf_sdm.h file). This should be enough, though there could be something I do not think about which you should see when you test.

Regarding memory, the bootloader is located at the end of the flash, so flash start address will not be a problem even if the SoftDevice increases. If the version is the same and you only use BLE still, the RAM configuration should also be good. Alternatively you could increase the bootloader RAM start address and decrees the size a bit just to be on the safe side (you will get a runtime error when configuring the SoftDevice if this is a problem, though).

RE: DFU Bootloader with S340 Softdevice

dragilla — Mon, 29 Nov 2021 08:48:36 GMT

Ok. I think the bootloader itself is ok, because I can upload a new zip containing my app. However, my app, which I tried to extend with the DFU functionality does not function properly. The DFU service is visible, but when i click on the "Start DFU" button in the BLE app (in the nrf connect suit), after connecting and upploading the zip, my app restarts, but does not go into the bootloader. What am I missing? Where to look for a mistake?

RE: DFU Bootloader with S340 Softdevice

dragilla — Sun, 28 Nov 2021 11:27:17 GMT

OK. I've changed the nrf_sdm.h file to the one provided with the S340 softdevice and it compiled and runs. Please let me know if this should be enough or maybe there is something more I should do. Thanks