Custom DFU bootloader

RE: Custom DFU bootloader

mosgaard2000 — Thu, 28 May 2020 09:04:58 GMT

devzone.nordicsemi.com/.../DFU_5F00_flash_5F00_placement.xml devzone.nordicsemi.com/.../Program_5F00_flash_5F00_placement.xml

RE: Custom DFU bootloader

jbalboa — Thu, 28 May 2020 08:56:57 GMT

Sorry for being a real pain but, could you share the flash_placement.xml file? I think I have a misconfiguration and I don't know where...

RE: Custom DFU bootloader

mosgaard2000 — Thu, 28 May 2020 06:51:00 GMT

I verified that we have the same linker_section_placement_macros values.

We differ in linker_section_placements_segments:

FLASH RX 0x0 0x100000;RAM RWX 0x20000000 0x40000;uicr_bootloader_start_address RX 0x00000FF8 0x4 ;uicr_mbr_params_page RX 0x00000FFC 0x4;mbr_params_page RX 0x000FE000 0x1000;bootloader_settings_page RX 0x000FF000 0x1000

I Also checked the settings from the DFU_bootloader. Here are my settings:

FLASH RX 0x0 0x100000;RAM RWX 0x20000000 0x40000;uicr_bootloader_start_address RX 0x00000FF8 0x4;bootloader_settings_page RX 0x000FF000 0x1000;uicr_mbr_params_page RX 0x00000FFC 0x4;mbr_params_page RX 0x000FE000 0x1000

FLASH_PH_START=0x0;FLASH_PH_SIZE=0x100000;RAM_PH_START=0x20000000;RAM_PH_SIZE=0x40000;FLASH_START=0xf8000;FLASH_SIZE=0x6000;RAM_START=0x20004000;RAM_SIZE=0x3bad0

RE: Custom DFU bootloader

jbalboa — Wed, 27 May 2020 09:27:48 GMT

I'm using the same softdevice and SDK as you. I changed the settings according with your specs and when I try to debug the application I get a 'Stopped by vector catch' and doesn't start...

The linker configuration I'm using is this:

linker_section_placement_macros="FLASH_PH_START=0x0;FLASH_PH_SIZE=0x100000;RAM_PH_START=0x20000000;RAM_PH_SIZE=0x40000;FLASH_START=0x26000;FLASH_SIZE=0xda000;RAM_START=0x20002b88;RAM_SIZE=0x3d478"
linker_section_placements_segments="FLASH RX 0x0 0x100000;RAM RWX 0x20000000 0x40000;uicr_bootloader_start_address RX 0x00000FF8 0x4;uicr_mbr_params_page RX 0x00000FFC 0x4;mbr_params_page RX 0x0007E000 0x1000;bootloader_settings_page RX 0x0007F000 0x1000"

RE: Custom DFU bootloader

mosgaard2000 — Wed, 27 May 2020 08:18:34 GMT

Hi Javier,

Can you check your linker settings in your project.

I use a nRF52840 with Softdevice 6.1.1 and SDK 15.3 and has the following settings:

FLASH_PH_START=0x0

FLASH_PH_SIZE=0x100000

RAM_PH_START=0x20000000

RAM_PH_SIZE=0x40000

FLASH_START=0x26000

FLASH_SIZE=0xda000

RAM_START=0x20002b88

RAM_SIZE=0x3d478

I believe I had the same problem until I found the correct values.

RE: Custom DFU bootloader

jbalboa — Tue, 26 May 2020 12:58:41 GMT

Hi Morten,

I used your tool (thanks again) to make a .hex file. Now my application reads that file and write it byte by byte.

Now the NRF_DFU_EVT_DFU_STARTED switch case gets fired but right after, the nrf_dfu_req_handler complaints about the firmware size:

Creating the object with size 0x00001000 would overflow firmware size. Offset is 0x00000000 and firmware size is 0x00000844

I'm not sure if I set a wrong value for the firmware size or if there is any other problem.

The full log is this:

<info> app: Application version 0
<info> app: Writting
<info> app: NRF_DFU_EVT_DFU_STARTED
<error> nrf_dfu_req_handler: Creating the object with size 0x00001000 would overflow firmware size. Offset is 0x00000000 and firmware size is 0x00000844.
<warning> nrf_dfu_serial: DFU request completed with result: 0x8
<info> app: NRF_DFU_EVT_DFU_FAILED
<error> nrf_dfu_req_handler: Write request too long
<warning> nrf_dfu_serial: DFU request completed with result: 0x3
<info> app: NRF_DFU_EVT_DFU_FAILED
<error> nrf_dfu_req_handler: Write request too long
<warning> nrf_dfu_serial: DFU request completed with result: 0x3
<info> app: NRF_DFU_EVT_DFU_FAILED
<error> nrf_dfu_serial_uart: Failed to allocate buffer
<error> nrf_dfu_req_handler: Write request too long
<warning> nrf_dfu_serial: DFU request completed with result: 0x3
<info> app: NRF_DFU_EVT_DFU_FAILED
<error> nrf_dfu_serial_uart: Failed to allocate buffer
<error> nrf_dfu_req_handler: Write request too long
<warning> nrf_dfu_serial: DFU request completed with result: 0x3
<info> app: NRF_DFU_EVT_DFU_FAILED

Am I missing something?

Javier Balboa

RE: Custom DFU bootloader

jbalboa — Tue, 26 May 2020 09:13:00 GMT

OMG thank you so much!!! I'll give it a try and post the results!!!

Javier Balboa

RE: Custom DFU bootloader

mosgaard2000 — Tue, 26 May 2020 09:07:19 GMT

Hi Javier,

I think you are right that you are missing the file conversion.

I have made a git-hub repository and put a small program to do the DFU conversion if you need that.

https://github.com/mosgaard2000/Software_XE7

I also uploaded a main.cpp file so you can see the code I use for converesion.

RE: Custom DFU bootloader

jbalboa — Mon, 25 May 2020 09:47:38 GMT

Hi mosgaard2000, thanks a lot for your code, it helped me to understand the dfu process in uart mode.

I managed to integrate your code on my application, however, when I start the DFU process, the observer only reaches the NRF_DFU_EVT_TRANSPORT_ACTIVATED switch case and not the NRF_DFU_EVT_DFU_STARTED.

I copied the MAIN_SM_BOOTLOADER part, and I send the upgraded image stored in the sd card byte by byte, but it doesn't do the upgrade process.

Do you know which could be the error?

You mentioned that you had to make a file converter to insert the DFU package info in the .zip file. Could it be the part I'm missing?

Thanks in advance

Javier Balboa

RE: Custom DFU bootloader

mosgaard2000 — Fri, 17 Jan 2020 08:40:58 GMT

Hi Erik,

1. I use nRF52840 with SDK 15.3 (I believe the background DFU requires 15.3 as a minimum).

2. There is a lot of log info that is not needed. In the Main function I start with a lot of if...else statements to decide if we start the bootloader - I only uses this to check if my program needs to go to other states (not related to the bootloader). This is not necessary - you can go directly to MAIN_SM_BOOTLOADER state which is were everything regarding the bootloader is handled.

Regards,

Morten

RE: Custom DFU bootloader

EGawtry — Thu, 16 Jan 2020 02:14:19 GMT

Thanks! I like how you tied it into the serial_dfu code. Two questions,

1. DFU_TRANSPORT_REGISTER doesn't seem to exist. What rev of nRF are you using? I have 15.2.

2. I notice that you go into a complicated bootloader setup in main. Is all that necessary for the DFU to work?

Thanks again,

-Erik

RE: Custom DFU bootloader

mosgaard2000 — Tue, 07 Jan 2020 12:32:08 GMT

I have attached my main.c file and the nrf_dfu_serial_uart that I uses.

I have removed most of the code from my main file, but you can see the state where I do the bootloader.

devzone.nordicsemi.com/.../nrf_5F00_dfu_5F00_serial_5F00_uart.zip

RE: Custom DFU bootloader

EGawtry — Mon, 06 Jan 2020 14:10:27 GMT

Marten,

Oh! Please! Anything that helps. I don't understand why I am having so much trouble with this when I had little problem with everything else (except for a library bug which I fixed), so anything that gives me a light bulb over my head is great.

Thanks,

-Erik

RE: Custom DFU bootloader

mosgaard2000 — Mon, 06 Jan 2020 09:04:48 GMT

Hi,

I did get it to work, but doing some reverse engineering.

I made use of the Background DFU - that are running inside my application. So I have access to all my peripherals - including my SPI interface to my external sd-card running with FatFS.

In my program I check the sd-card for a specific bootloader file, and if that exists I go to a state where I read the file 1 byte at a time.

I added the UART bootloader to my code and commented out the interrupt routines and added my own function to call. Then I can pass the byte I read from the file to the UART bootloader.

In order to get it to work I had to make a file-converter that actually reads the .zip package, that are normally used by the bootloader, and convert it to a new file that also contains the DFU package info (because this is normally handled by the interface program on the PC).

Hope this helps a little - if you like I will be happy to share my code for the bootloader and the file-converter with you.

-Morten

RE: Custom DFU bootloader

EGawtry — Sun, 05 Jan 2020 21:29:05 GMT

Hello, did you ever get it to work?

I have a similar problem for my pca10040/S132 (Laird BL652), and am getting really confused by the cryptic barely documented DFU interface. I noticed that one example uses pstorage, is that the way to bypass all that? I suddenly have clients breathing down my neck wanting a firmware update to allow SD-card firmware updates before end customer distribution. ;-)

Thank you,

-Erik

RE: Custom DFU bootloader

bjorn-spockeli — Tue, 30 Jul 2019 12:02:45 GMT

Hi Morten,

the Secure Bootloader in our nRF5 SDK is designed to be transport agnostic. so it should be able to create a custom transport layer, e.g. SPI, that interfaces with the bootloader.

I would recommend taking a look at the UART transport layer implementation in the nRF5_SDK_15.3.0_59ac345\examples\dfu\secure_bootloader\pca10056_uart example. Specifically, nrf_dfu_serial_uart.c and nrf_dfu_serial.c in the nRF5_SDK_15.3.0_59ac345\components\libraries\bootloader\serial_dfu folder.

They show how the DFU_TRANSPORT_REGISTER macro to register the init and close functions used further up in the bootloader

DFU_TRANSPORT_REGISTER(nrf_dfu_transport_t const uart_dfu_transport) =
{
    .init_func  = uart_dfu_transport_init,
    .close_func = uart_dfu_transport_close,
};

Best regards

Bjørn