nRF52 Mesh DFU questions

RE: nRF52 Mesh DFU questions

davidesteban13 — Tue, 27 Nov 2018 14:38:14 GMT

Hello Helen, i have the same problem, you fixed it?

RE: nRF52 Mesh DFU questions

Martin — Wed, 14 Nov 2018 09:57:59 GMT

Hi,

you should verify that bank_addr is actually put in the start of your available memory, i.e. 0x46FFD.

Martin

RE: nRF52 Mesh DFU questions

helen — Mon, 12 Nov 2018 07:03:12 GMT

HI Martin,

It is my application's memory:

The spare area is from 0x46ffc to 0x6e000, which is 156KB. And my dfu zip file is only 134KB, if it is too large, what is the the most large size? How to calculate? Thanks!

Harden

RE: nRF52 Mesh DFU questions

Martin — Fri, 09 Nov 2018 07:34:05 GMT

Hi,

The error you get 0xD is NRF_MESH_DFU_END_ERROR__LAST, which states: /**< The given bank address results in bootloader invalidation. */. This usually suggests your file is to large to fit on the free designated area for DFU. I suggest you look into where the Bootloader, SoftDevice and Mesh puts files in the flash. You can use the nRF Connect Programmer found HERE to help you adjust flash placements.

RE: nRF52 Mesh DFU questions

helen — Tue, 06 Nov 2018 02:04:53 GMT

devzone.nordicsemi.com/.../dfu_5F00_test.zip devzone.nordicsemi.com/.../light_5F00_server_5F00_110501.zip

HI Martin,

Tnanks! I have add RAM_SIZE in the dfu example in the mesh sdk 2.2.

FLASH_PH_START=0x0

FLASH_PH_SIZE=0x78000

RAM_PH_START=0x20000000

RAM_PH_SIZE=0xf000

FLASH_START=0x26000

RAM_START=0x200032c8

RAM_SIZE=0xbd38

And modify the RAM_PH_SIZE to RAM_SIZE in flash_placement.xml.

But when I try to dfu with the light_server_110501.zip(134KB)，it always report like this and stop output the log.

<t: 10298>, main.c, 244, Enabling serial interface...

<t: 10310>, main.c, 248, DFU example started!

<t: 215611>, nrf_mesh_dfu.c, 390, New firmware!

<t: 215614>, nrf_mesh_dfu.c, 528, RADIO TX! SLOT 0, count 255, interval: periodic, handle: FFFD

<t: 215618>, nrf_mesh_dfu.c, 534, Killing a TX slot prematurely (repeats done: 1).

<t: 215622>, nrf_mesh_dfu.c, 561, SERIAL TX!

<t: 281806>, nrf_mesh_dfu.c, 528, RADIO TX! SLOT 0, count 255, interval: periodic, handle: FFFD

<t: 281810>, nrf_mesh_dfu.c, 534, Killing a TX slot prematurely (repeats done: 0).

<t: 281814>, nrf_mesh_dfu.c, 561, SERIAL TX!

<t: 347660>, nrf_mesh_dfu.c, 383, Abort event. Reason: 0xD

<t: 347664>, nrf_mesh_dfu.c, 528, RADIO TX! SLOT 0, count 255, interval: periodic, handle: FFFE

<t: 347668>, nrf_mesh_dfu.c, 534, Killing a TX slot prematurely (repeats done: 20).

<t: 347672>, nrf_mesh_dfu.c, 561, SERIAL TX!

When I dfu with the dfu_test.zip(4KB), it always succeed. I have no idea about that. Could you give me some advice? Thanks!

Helen

RE: nRF52 Mesh DFU questions

Martin — Mon, 05 Nov 2018 09:53:58 GMT

Hi Helen,

The difference between RAM_PH_SIZE and RAM_SIZE is that one is your physical ram, whilst the other is ram allocated for your application.

It seems like you maybe got these mixed up somewhere, as it looks like you do not have enough RAM.Your flash_placement.xml line 32 should look like this:

 <MemorySegment name="RAM" start="$(RAM_PH_START)" size="$(RAM_SIZE)">

If this does not solve your issue, you should look into how much ram you have currently allocated. In that case, this post should point you in the right direction.

Martin

RE: nRF52 Mesh DFU questions

helen — Mon, 05 Nov 2018 09:16:50 GMT

Hi Martin,

In 6) ,what does 'On line 32 change RAM_PH_SIZE to RAM_SIZE' mean? What is RAM_SIZE equal to? When I do this, and rebuild my project, I meet some error:

1> C:/Program Files/SEGGER/SEGGER Embedded Studio 3.30/gcc/arm-none-eabi/bin/ld: error: .reserved_ram is too large to fit in RAM memory segment
1> C:/Program Files/SEGGER/SEGGER Embedded Studio 3.30/gcc/arm-none-eabi/bin/ld: error: .data_run is too large to fit in RAM memory segment
1> C:/Program Files/SEGGER/SEGGER Embedded Studio 3.30/gcc/arm-none-eabi/bin/ld: error: .bss is too large to fit in RAM memory segment
1> C:/Program Files/SEGGER/SEGGER Embedded Studio 3.30/gcc/arm-none-eabi/bin/ld: error: .heap is too large to fit in RAM memory segment
1> C:/Program Files/SEGGER/SEGGER Embedded Studio 3.30/gcc/arm-none-eabi/bin/ld: error: section .heap overlaps absolute placed section .stack
1> C:/Program Files/SEGGER/SEGGER Embedded Studio 3.30/gcc/arm-none-eabi/bin/ld: error: .reserved_ram is too large to fit in RAM memory segment
1> C:/Program Files/SEGGER/SEGGER Embedded Studio 3.30/gcc/arm-none-eabi/bin/ld: error: .data_run is too large to fit in RAM memory segment
1> C:/Program Files/SEGGER/SEGGER Embedded Studio 3.30/gcc/arm-none-eabi/bin/ld: error: .bss is too large to fit in RAM memory segment
1> C:/Program Files/SEGGER/SEGGER Embedded Studio 3.30/gcc/arm-none-eabi/bin/ld: error: .heap is too large to fit in RAM memory segment
1> C:/Program Files/SEGGER/SEGGER Embedded Studio 3.30/gcc/arm-none-eabi/bin/ld: error: section .heap overlaps absolute placed section .stack
Build failed

Helen

RE: nRF52 Mesh DFU questions

Martin — Fri, 29 Jun 2018 08:51:46 GMT

My pleasure!

RE: nRF52 Mesh DFU questions

Carlos — Fri, 29 Jun 2018 01:13:14 GMT

Thank you for the suggestions, now I have DFU working with the light switch examples.

RE: nRF52 Mesh DFU questions

Martin — Thu, 28 Jun 2018 06:24:30 GMT

Time to get to bed now then ;)

The DFU-example is not prepared to be provisioned, but it does not need to be. You can instead program one of your servers or clients with NRF_MESH_SERIAL_ENABLE 1 and flash it with the serial bootloader. Then this device will be able to send DFU to the rest of the devices.

I have seen the same errors, and they are related to the error in flash_placement.xml I think.

My original answer is also updated, as I saw that you are using the armcc bootloader, whilst I was using the gccarmemb bootloader.

Good luck!

BR,

Martin

RE: nRF52 Mesh DFU questions

Carlos — Thu, 28 Jun 2018 06:19:30 GMT

Hello Martin,

Thank you for the suggestions, I will follow them tomorrow as soon as I get in to the office (almost midnight over here).

One more thing, do I need to do something special to provision the devkit with the DFU example? As my output shows I can see the UUID being broadcast but it does not start the provisioning process.

Have you seen the same errors when sending the zip file to the DFU devkit?

Regards,

Carlos

RE: nRF52 Mesh DFU questions

Martin — Thu, 28 Jun 2018 06:04:35 GMT

Hello Carlos, I have just done something similar to what you are trying to do.

I will try to answer atleast some of your questions.

1) Yes, you need a separate zip ,and a separate application ID for each type of application that you run. Server/client etc. these also need rising application_versions for everytime you do a new DFU.

For the bootloader_config_default.json you will only need to modify the application_id the first time you flash the development board.

2) Here you can find a list of the Softdevices and their versions: https://devzone.nordicsemi.com/f/nordic-q-a/1171/how-do-i-access-softdevice-version-string

3) The serial bootloader only needs to be flashed onto the card which is recieving the DFU via cable. All other cards should have the other bootloader as mentioned in your question 4. For my project I used the bin/bootloader/gccarmemb/mesh_bootloader_gccarmemb_nrf52832_xxAA.hex and /bin/bootloader/gccarmemb/mesh_bootloader_serial_gccarmemb_nrf52832_xxAA.hex . I know these will work, so unless there is a reason not to use these i would reccomend them

4) See 3.

5) The dfu hex file will be found in that location only after you have built the project with segger/cmake or your preffered IDE.

Something important for step 5 is: If you want to do DFU on servers and clients, these both need relevant code from the DFU project. Remember to put NRF_MESH_SERIAL_ENABLE 0 on devices that are not programmed via cable. After you have implemented the DFU project code, rebuild your project and replace build/examples/dfu/dfu_nrf52832_xxAA_s132_5.0.0.hex with i.e [ /examples/light_switch/server/build/\light_switch_server_nrf52832_xxAA_s132_6.0.0_Debug/light_switch_server_nrf52832_xxAA_s132_6.0.0.hex ] <<-- This needs to point at your hex files for the different units. Check time modified on the file, so that it is when you rebuilt the project.

tl:dr All different units need an initial flash of their project code, with necessary DFU code included..

6) You should modify all your projects flash_placement.xml files. On line 32 change RAM_PH_SIZE to RAM_SIZE this will give you enough space to transfer the data on your development boards. Remember to save and rebuild after doing this.

Also, I recommend testing DFU using the step-by-step guide in the quick-start guide. The dfu_no_serial_<target>_<SoftDevice>.hex and dfu_serial_<target>_<SoftDevice>.hex files can be created simply by building the DFU project with NRF_MESH_SERIAL_ENABLE set to 1 and 0. You will find the most recent .hex in the project folder/build/"build type"/

Hope this helps you on the way!

Regards,

Martin

RE: nRF52 Mesh DFU questions

Carlos — Thu, 28 Jun 2018 01:18:25 GMT

By the way I also include the relevant code from the DFU example into the light switch server, in case that was needed but no difference so far. Maybe I am missing some simple but important piece of the puzzle.