This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Relay in mesh DFU

Hi,

I have an nRF52840 DevKit and dongle and am using SDK for mesh v.5 with SDK 17.0.2.

I want to update the firmware in a mesh network and am working on the mesh DFU example using DevKit connected to pc and dongle which will receive the file through the mesh.

I run the example successfully and it worked. 

Now I want to send the firmware to a specific node in the mesh network. So I used different application IDs for DevKit (1) and dongle (2) in the generation of the device page and zip file.

I tried to send the zip file to the dongle but that did not work. 

Here is the log:

3>, main.c, 227, ----- Bluetooth Mesh DFU Example -----
00> <t: 8884>, nrf_mesh_dfu.c, 753, Version info: BL(ver, id): 0x01 0x01 SD: 0x0100
00> <t: 8888>, nrf_mesh_dfu.c, 755, Version info: APP company: 0x00000059 id: 0x0001 version: 0x00000001
00> <t: 8901>, serial_handler_prov.c, 267, Generating encryption keypair...
00> <t: 13799>, main.c, 233, Initialization complete!
00> <t: 18558>, main.c, 254, Enabling serial interface...
00> <t: 18561>, mesh_app_utils.c, 66, Device UUID (raw): 137FF47B11294702B381A62F60654E45
00> <t: 18564>, mesh_app_utils.c, 67, Device UUID : 137FF47B-1129-4702-B381-A62F60654E45
00> <t: 18575>, nrf_mesh_dfu.c, 554, RADIO TX! SLOT 0, count 15, interval: periodic, handle: FFFE
00> <t: 18580>, nrf_mesh_dfu.c, 593, SERIAL TX (type: 65534)
00> <t: 18588>, main.c, 262, DFU example started!
00> <t: 2229779>, nrf_mesh_dfu.c, 418, New firmware!
00> <t: 2229782>, main.c, 79, DFU type Application
00> <t: 2229784>, main.c, 148, Starting relay
00> <t: 2229786>, nrf_mesh_dfu.c, 554, RADIO TX! SLOT 0, count 3, interval: periodic, handle: FFFD
00> <t: 2229791>, nrf_mesh_dfu.c, 593, SERIAL TX (type: 65533)
00> <t: 2295967>, nrf_mesh_dfu.c, 554, RADIO TX! SLOT 0, count 3, interval: periodic, handle: FFFD
00> <t: 2295971>, nrf_mesh_dfu.c, 593, SERIAL TX (type: 65533)
00> <t: 2362028>, nrf_mesh_dfu.c, 458, DFU start
00> <t: 2362031>, nrf_mesh_dfu.c, 554, RADIO TX! SLOT 1, count 6, interval: exponential, handle: FFFC
00> <t: 5245615>, nrf_mesh_dfu.c, 325, ABORT Timeout fired @1184083466
00> <t: 5245618>, nrf_mesh_dfu.c, 554, RADIO TX! SLOT 0, count 15, interval: periodic, handle: FFFE
00> <t: 5245623>, nrf_mesh_dfu.c, 593, SERIAL TX (type: 65534)
00> <t: 5245629>, nrf_mesh_dfu.c, 554, RADIO TX! SLOT 0, count 15, interval: periodic, handle: FFFE
00> <t: 5245634>, nrf_mesh_dfu.c, 565, Killing a TX slot prematurely (repeats done: 0).
00> <t: 5245637>, nrf_mesh_dfu.c, 593, SERIAL TX (type: 65534)

I have searched the devzone and found this ticket like my case. 

In this case, it was suggested to use a patch file which is for SDK v4.0.

Should I use an updated patch file for SDK v5?

Could you please advise me to solve the problem?

Br, 

Sama

Parents
  • Hi,

    From your logs it seems like the DFU was successful. But the firmware on the dongle was not update? Am I understanding this correctly? The LED is not toggling? 

  • Hi, 

    What specifically did you flash on the device connected to PC? and can you reproduce the issue using our example?

  • Hi,

    I am sorry for my late reply.

    What I did is:


    1. I produced the private key and public key and then the device page different for DevKit and dongle.


    2. I flashed the DevKit by:
        a. SoftDevice.
        b. dfu_nrf52840_xxAA_s140_7_2_0 from example folder.
        c. Device page.
        d. mesh_bootloader_serial_gccarmemb_nrf52840_xxAA.

    3. and flashed the dongle by:
        a. SoftDevice.
        b. dfu_no_serial_nrf52840_xxAA_s140_7_2_0 from example folder.
        c. Device page.
        d. mesh_bootloader_gccarmemb_nrf52840_xxAA.

    4. I produced the test_file.zip by using the bliny example for the dongle and tried to send that. I considered that the zip.file should be produced so that it matches with the device page of the dongle. However, the firmware of the dongle was not updated.

    Br,

    Sama

Reply
  • Hi,

    I am sorry for my late reply.

    What I did is:


    1. I produced the private key and public key and then the device page different for DevKit and dongle.


    2. I flashed the DevKit by:
        a. SoftDevice.
        b. dfu_nrf52840_xxAA_s140_7_2_0 from example folder.
        c. Device page.
        d. mesh_bootloader_serial_gccarmemb_nrf52840_xxAA.

    3. and flashed the dongle by:
        a. SoftDevice.
        b. dfu_no_serial_nrf52840_xxAA_s140_7_2_0 from example folder.
        c. Device page.
        d. mesh_bootloader_gccarmemb_nrf52840_xxAA.

    4. I produced the test_file.zip by using the bliny example for the dongle and tried to send that. I considered that the zip.file should be produced so that it matches with the device page of the dongle. However, the firmware of the dongle was not updated.

    Br,

    Sama

Children
No Data
Related