Mesh DFU Relay Problem

RE: Mesh DFU Relay Problem

Hung Bui — Thu, 02 Apr 2020 12:50:11 GMT

I would suggest testing of building a normal example first. Just follow what in the documentation.

After you call cmake -G Ninja ..................
You need to call "ninja" to actually build the hex file.

You don't need to make the build folder inside the bootloader location.

RE: Mesh DFU Relay Problem

Panda — Thu, 02 Apr 2020 06:58:04 GMT

Hi Hung,

I have read the link content you gave above. When I go on This link STEP 1. It happens some warning as below document :

devzone.nordicsemi.com/.../Cmake-warning-for-bootloader.txt

I have added two lines :cmake_minimum_required(VERSION 3.17)
project (mesh_bootloader) to CMakeLists.txt under path: ...\nrf5_SDK_for_Mesh_v3.2.0_src\mesh\bootloader.

Is the "build "file path is right?How to solve the warning ? Does it need to use ...\nrf5_SDK_for_Mesh_v3.2.0_src\CMake files? Please give me some help ,thanks in advance.

Best Regards,

Panda

RE: Mesh DFU Relay Problem

Hung Bui — Fri, 27 Mar 2020 10:18:33 GMT

You need to install Ninja. Have you followed the documentation for all dependencies here: https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.meshsdk.v4.0.0/md_doc_getting_started_how_to_toolchain.html?cp=7_2_1_1

RE: Mesh DFU Relay Problem

Panda — Fri, 27 Mar 2020 07:20:08 GMT

Hi Hung,

PS E:\Project\Mesh_v3.2.0\nrf5_SDK_for_Mesh_v3.2.0_src\build> cmake -G Ninja -DTOOLCHAIN=gccarmemb -DPLATFORM=nrf52832_xxAA -DBOARD=pca10040 -DSOFTDEVICE=s132_6.1.1 ..
-- Configuring CMake for nRF5 SDK for Bluetooth Mesh 3.2.0
CMake Error: CMake was unable to find a build program corresponding to "Ninja". CMAKE_MAKE_PROGRAM is not set. You probably need to select a different build tool.
-- Configuring incomplete, errors occurred!
See also "E:/Project/Mesh_v3.2.0/nrf5_SDK_for_Mesh_v3.2.0_src/build/CMakeFiles/CMakeOutput.log".

CMake Error happens,how to solve it ? thanks .

RE: Mesh DFU Relay Problem

Hung Bui — Wed, 25 Mar 2020 09:13:37 GMT

Hi Panda,

Have you tried to compile using cmake ? Please follow the instruction on how to build mesh stack and let me know which issue you have.

RE: Mesh DFU Relay Problem

Panda — Wed, 25 Mar 2020 04:05:26 GMT

Hi Hung,

Could you give .emProject and flash_placement.xml for nrf52832 using sdk nRF5_SDK_15.3.0_59ac345 and nrf5_SDK_for_Mesh_v3.2.0_src ?I will try to tansplant since the builded cannot be programed. Thanks.

Best Regards,

Panda

RE: Mesh DFU Relay Problem

Hung Bui — Tue, 24 Mar 2020 17:01:55 GMT

No, there would be no SES project for the bootloader in the SDK.
But we do have an unofficial SES project here:
https://devzone.nordicsemi.com/f/nordic-q-a/51534/stepping-through-nrf-mesh-bootloader-code-in-segger-embedded-studio

RE: Mesh DFU Relay Problem

Panda — Tue, 24 Mar 2020 11:04:40 GMT

Hi Hung,

Do you mean the bootloader can also be builded by SES? just create a booeloader project using SES ,then get the hex ? I will raed he source link you gave above.Thanks

RE: Mesh DFU Relay Problem

Hung Bui — Tue, 24 Mar 2020 10:32:33 GMT

Hi Panda,
Please follow the instruction on how to build the mesh stack with cmake here: https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.meshsdk.v3.2.0/md_doc_getting_started_how_to_build.html?cp=7_6_0_1_2

You need to call the script for Cmake inside a subfolder (for example "build" folder) inside the mesh folder.

RE: Mesh DFU Relay Problem

Panda — Tue, 24 Mar 2020 09:57:25 GMT

Hi Hung,

sorry to reply later.I have seen the patch .I am not familiar with cmake.Could you tell me how to build bootloader with camke in detail?

I install camke using the source https://cmake.org/download .Then I input "cmake''in dos command line ,it works.Next I input" cmake -G Ninja .. -DSDK_ROOT=[E:/Project/Mesh_v3.2.0/nrf5_SDK_for_Mesh_v3.2.0_src/mesh/bootloader] -DCMAKE_BUILD_TYPE=MinSizeRel -DBUILD_BOOTLOADER=ON" with your patch files replace .Error shows "The source directory "C:/Users" does not appear to contain CMakeLists.txt."

the another method is use CMake 3.17.0 gui, I have tried but also failed.

I notice under the mesh sdk file ,there is a CMake file.Maybe it could be used?

Waitting for your help .on the same time,i will learn something about cmake.Thank you.

Best Regards,

Panda

RE: Mesh DFU Relay Problem

Hung Bui — Wed, 05 Feb 2020 12:40:26 GMT

Hi Marques,
If you still have trouble with the nRF52840, please use the patch I provided here. It's for SDK v4.0. The command to generate bootloader file for the nRF52840 is:

cmake -G Ninja .. -DSDK_ROOT=[path to your nRF5 SDK] -DCMAKE_BUILD_TYPE=MinSizeRel -DBUILD_BOOTLOADER=ON -DPLATFORM=nrf52840_xxAA -DSOFTDEVICE=s140_7.0.1

Please make sure you recompile the nrfutil using the patch as well.

devzone.nordicsemi.com/.../patchnRF52840.zip

RE: Mesh DFU Relay Problem

Hung Bui — Mon, 03 Feb 2020 08:35:28 GMT

Hi,

Please implement the .patch file for the bootloader and re-compile it.
To build the bootloader from command line do this:

cmake -G Ninja .. -DSDK_ROOT=[path to your SDK] -DCMAKE_BUILD_TYPE=MinSizeRel -DBUILD_BOOTLOADER=ON

RE: Mesh DFU Relay Problem

rmarques — Fri, 31 Jan 2020 17:46:56 GMT

Hello, our team had this problem some odd months ago with nrf52840 - post.

Can you guys compile a bootloader for this chip with the same fix please? We implemented our own recovery routines on the app side but we feel it's clunky and it fails sometimes.

RE: Mesh DFU Relay Problem

Hung Bui — Wed, 29 Jan 2020 16:09:33 GMT

Hi Panda,

Good news, we have a workaround prototype that you can test. We are still continue testing but it seems to work.

As explained earlier it was an issue that the serial node doesn't re-transmit the missing segment. The fix here involved modification on nrfutil, bootloader and the serial dfu app.
Please make sure you rebuild nrfutil after the patch.

Attached is the .patch file and the patched file that I was using in the test. Please let me know the result on your side.

devzone.nordicsemi.com/.../patch.zip

RE: Mesh DFU Relay Problem

Hung Bui — Wed, 22 Jan 2020 13:42:25 GMT

Hi Panda,

Just an update, we found that it's an issue when doing the test with just one relay node (device A , connected to PC) and one mesh node (device B) ,when there is any missing segment on device B, the device A won't resend the missing segment (as it's only doing relay) and this will result in error 3.

It's not the case when device A also receive image, or when you have multiple nodes that receive the image as the destination not relay. In that case the other node(s) can resend the missing segment when requested by B.

We are working on a fix for this.

You can test this theory by having 2 or 3 nodes as devices B, they should be able to serve each other if one node misses a packet.

RE: Mesh DFU Relay Problem

Panda — Fri, 17 Jan 2020 02:16:56 GMT

Hi Hung,

The hex files i used is Here. devzone.nordicsemi.com/.../s132.6.1.1.rar.

RE: Mesh DFU Relay Problem

Hung Bui — Thu, 16 Jan 2020 12:32:33 GMT

Hi Panda,

Just a quick update, we have reproduced the issue here. With error 0x03. I will let you know when we have any finding.

RE: Mesh DFU Relay Problem

Hung Bui — Thu, 16 Jan 2020 12:11:29 GMT

Hi Panda,

I know that you need to use the dimming feature, but we want to try the default example to see if it was any issue integrating the DFU code into the dimming example causing the issue or not.

Which bootloader did you use ? Was it the precompiled one ? Could you state the .hex file you used ?

RE: Mesh DFU Relay Problem

Panda — Thu, 16 Jan 2020 07:50:49 GMT

Hi Hung,

I Have relied your similar question above .I use SES 4.16a.I just now test your given blinky110k.hex.The same issue happens after device A process 20% in dos command window.When I use blinky160k.hex.The device B's whole log just as follow without reaction:

0> <t: 723195>, nrf_mesh_dfu.c, 390, New firmware!
0> <t: 723198>, main.c, 154, Requesting DFU transfer with bank at 0x0004C000
0> <t: 723202>, nrf_mesh_dfu.c, 528, RADIO TX! SLOT 0, count 255, interval: periodic, handle: FFFD
0> <t: 723205>, nrf_mesh_dfu.c, 534, Killing a TX slot prematurely (repeats done: 3).
0> <t: 723209>, nrf_mesh_dfu.c, 561, SERIAL TX!
0> <t: 788600>, nrf_mesh_dfu.c, 528, RADIO TX! SLOT 0, count 255, interval: periodic, handle: FFFD
0> <t: 788603>, nrf_mesh_dfu.c, 534, Killing a TX slot prematurely (repeats done: 0).
0> <t: 788607>, nrf_mesh_dfu.c, 561, SERIAL TX!
0> <t: 855246>, nrf_mesh_dfu.c, 383, Abort event. Reason: 0xD
0> <t: 855249>, main.c, 175, Mesh DFU End !
0> <t: 855252>, nrf_mesh_dfu.c, 528, RADIO TX! SLOT 0, count 255, interval: periodic, handle: FFFE
0> <t: 855256>, nrf_mesh_dfu.c, 534, Killing a TX slot prematurely (repeats done: 20).
0> <t: 855259>, nrf_mesh_dfu.c, 561, SERIAL TX!

----------- log end up without reaction ----------

Device A and B's base hex is devzone.nordicsemi.com/.../light_5F00_switch_5F00_dimming_5F00_client_5F00_DFU_5F00_nrf52832_5F00_xxAA_5F00_s132_5F00_6.1.1.hex . I need use this application to mesh dfu ,not just do example. So there is need to find out reason and repair this issue.

Do SDK mesh v4.0.0 fix this issue?

Best Regards,

Panda

RE: Mesh DFU Relay Problem

Hung Bui — Wed, 15 Jan 2020 15:37:59 GMT

How long did it take to get the device B to stop DFU ? Do you have the issue at the same place, all the times, or it happen at different point ? Can you provide the log file ?
I provided here some .hex file with different file size that you can use to test.

devzone.nordicsemi.com/.../blinky.zip

RE: Mesh DFU Relay Problem

Hung Bui — Wed, 15 Jan 2020 14:04:46 GMT

Hi Panda,

I'm sorry for the late reply but could you update the DFU .zip file you used for DFU, not the .zip file of your project. Please provide the .hex file of the application you use in the .zip file as well. Please generate the .zip without any key so we can test using our bootloader.

Have you tried to test using our dfu example with no modification ?

RE: Mesh DFU Relay Problem

Panda — Tue, 14 Jan 2020 05:59:31 GMT

The file is devzone.nordicsemi.com/.../0160.dimming_5F00_client_5F00_DFU.rar . you can name different devices (A/B/Target relay)by changing GAP_DEVICE_NAME define to distinguish and justify .If there are any requirements,please tell me konw .

Best Regards,

Panda

RE: Mesh DFU Relay Problem

Hung Bui — Mon, 13 Jan 2020 13:22:25 GMT

Hi Panda,

Seems that the DFU relaying was working but something caused the packet to drop.
Could you provide us a .zip file that we can test here and check if we can reproduce the issue ? Could you make the .zip with no key so it's easier to test here.

RE: Mesh DFU Relay Problem

Panda — Sat, 11 Jan 2020 03:48:10 GMT

Hi Hung,

DFU with smaller image for Device B test is OK.

RE: Mesh DFU Relay Problem

Hung Bui — Fri, 10 Jan 2020 09:23:32 GMT

Hi Panda,

Do you have any update of doing DFU with smaller image ?