OTA DFU bootloader

RE: OTA DFU bootloader

Amanda Hsieh — Mon, 21 Sep 2020 05:53:20 GMT

Could you try again or other browsers? I can open them on my side.

RE: OTA DFU bootloader

Cy — Fri, 18 Sep 2020 14:14:52 GMT

that link is dead or something, at least today.

RE: OTA DFU bootloader

Amanda Hsieh — Fri, 18 Sep 2020 07:17:18 GMT

Hi Cy,

Because the size of each SoftDevice is different (See Adjustment of RAM and Flash memory), the flash and ram values are different in each SD. However, it is still good feedback to consider that.

[quote user="drollinger"]Is there a detailed and comprehensive explanation of the bootloader design?[/quote]

Please see the Bootloader and DFU modules documentation.

-Amanda H.

RE: OTA DFU bootloader

Cy — Thu, 17 Sep 2020 14:59:58 GMT

So, from my point of view, worth about $0.02, it would seem if I can make a zip based on a working hex within the nrfutil and the option - - softdevice 0x00 than it should have made the flash and ram values correct.

RE: OTA DFU bootloader

Cy — Thu, 17 Sep 2020 14:42:36 GMT

Thank you, I develop with visual code and command line tools, I apologize for not including it in my original post. I use the makefile inside the armgcc folder of the projects. When following a recipe on how to do things, as in Hung Bui's, there is no information on the design or development of the project itself and is quite abstract. It ok to be abstract when everything just works but when it does not, fine detail on the design and development is needed.

Is there a detailed and comprehensive explanation of the bootloader design?

RE: OTA DFU bootloader

Amanda Hsieh — Thu, 17 Sep 2020 08:42:14 GMT

Hi Cy,

Sorry for misunderstanding your situation.

--sd-req should be the same version as the softdevice on the chip because the bootloader will check the version number. But it doesn't care the app will use it late or not.

[quote user="drollinger"]I have a situation where the application useful to me does not require a soft device. Well, I guess it is prudent to dig into the bootloader program and the linker script to figure out where, what, and how. [/quote]

Yeah, I agree with Jörg Fischer's suggestion. You can have an application that doesn't use the SoftDevice. You only need to change the FLASH and RAM start address and size. You can test and modify nRF5_SDK_17.0\examples\peripheral\blinky\pca10040\mbr with the FLASH and RAM start address and size in nRF5_SDK_17.0\examples\peripheral\blinky\pca10040\s132.

Right-click on the project -> Common -> Linker -> Section Placement Macros

-Amanda H.

RE: OTA DFU bootloader

Cy — Mon, 14 Sep 2020 14:35:09 GMT

Hmm, I have no use for hrs_application_s132.hex, and that is a soft device application. I have a situation where the application useful to me does not require a soft device. Well, I guess it is prudent to dig into the bootloader program and the linker script to figure out where, what, and how.

RE: OTA DFU bootloader

Amanda Hsieh — Mon, 14 Sep 2020 11:44:19 GMT

Hi,

[quote user="drollinger"]nrfutil pkg generate --hw-version 52 --application-version 1 --application _build/nrf52832_xxaa.hex --sd-req 0xCB --key-file private.key app_dfu_package.zip[/quote]

If you already programmed the s132_nrf52_7.0.1_softdevice.hex and only want to only update the app, your commend is correct. You can test with the hrs_application_s132.hex nRF5_SDK_17.0.0\examples\dfu\secure_dfu_test_images\ble\nrf52832

-Amanda H.

RE: OTA DFU bootloader

Cy — Sat, 12 Sep 2020 22:50:41 GMT

Well, utilizing the nrfutil and the 0x00 on the sd option will zip and data transfers but will not run the application.

RE: OTA DFU bootloader

Cy — Sat, 12 Sep 2020 22:41:58 GMT

The tutorial utilizes the

nrfutil pkg generate --hw-version 52 --application-version 1 --application _build/nrf52832_xxaa.hex --sd-req 0xCB --key-file private.key app_dfu_package.zip

to zip the application. Can this same utility be used to zip the app in the correct way? The option of the --sd with the version 7.0.1 is being used but I dont think it will run properly without the option, but will run with the option being 0x00.

RE: OTA DFU bootloader

Turbo J — Sat, 12 Sep 2020 21:56:16 GMT

You need to modify the linker script/settings for the application.

Reason: The SD has to stay in place - otherwise the OTA DFU bootloader won't work. Thus the application has to occupy the flash area after the SD. You also need to reserve a small amount of RAM (8 bytes IIRC) for the Softdevice - even when it is disabled - in order to use interrupt forwarding.

An unmodified app would occupy the space for the SD in flash - this should be rejected in the bootloader logic. And no, cannot run a statically linked app from a flash address other than it was linked to.