• State Verified Answer
  • Replies 1 reply
  • Subscribers 73 subscribers
  • Views 972 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 218802
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Mesh update in NRFUTIL 4.0.0

Tomi

Hi!

Does latest NRFUTIL 4.0.0 include mesh update option?

I saw in branch dfu_mesh on pc-nrfutil github that this branch was last updated on 16.12.2016 (nrfutil 0.3) and that newer updates do not include proper files for Mesh update.

If I want to translate Python NRFUTIL files for Java and I am wondering if 0.3 version is still OK and dfu_mesh branch is still working on nRF52840 DK boards?

Thank you in advance!

Parents
  • +1

    Hi,

    Yes, this is the correct version to use for Mesh DFU. Please have a look at the Configuring DFU section of nRF5 SDK for Mesh documentation:

    To perform DFU transfers over mesh, use a customized version of the nrfutil tool. This tool sends the DFU packets to one device over serial interface. This device then stores these packets, and also forwards them to the other devices withing the radio range.

    The required steps are listed below, followed by a more detailed explanation for each step.

    Before you start, note the following information:

    • This guide assumes that you have at least 2 development kits or devices, where one is to be interfaced over the serial port, while the other receives the DFU from the first device over the mesh. To specify which device to use in which context, add the -s <serial-number> option for each call to the nrfjprog command, where <serial-number> is the Segger ID of your device. This will make nrfjprog execute its operations on the specified device only.
    • The nrfutil tool that is required to transfer the firmware image is available at https://github.com/NordicSemiconductor/pc-nrfutil/tree/mesh_dfu. The tool is open source.
    Note
    The master branch of the pc-nrfutil repository does not contain the additional code that is needed to handle a mesh DFU. To use the tool with mesh DFU, use the mesh_dfu branch as mentioned above. See the tool's documentation for more information about installation and prerequisites.

    Best regards,
    Jørgen

Reply
  • +1

    Hi,

    Yes, this is the correct version to use for Mesh DFU. Please have a look at the Configuring DFU section of nRF5 SDK for Mesh documentation:

    To perform DFU transfers over mesh, use a customized version of the nrfutil tool. This tool sends the DFU packets to one device over serial interface. This device then stores these packets, and also forwards them to the other devices withing the radio range.

    The required steps are listed below, followed by a more detailed explanation for each step.

    Before you start, note the following information:

    • This guide assumes that you have at least 2 development kits or devices, where one is to be interfaced over the serial port, while the other receives the DFU from the first device over the mesh. To specify which device to use in which context, add the -s <serial-number> option for each call to the nrfjprog command, where <serial-number> is the Segger ID of your device. This will make nrfjprog execute its operations on the specified device only.
    • The nrfutil tool that is required to transfer the firmware image is available at https://github.com/NordicSemiconductor/pc-nrfutil/tree/mesh_dfu. The tool is open source.
    Note
    The master branch of the pc-nrfutil repository does not contain the additional code that is needed to handle a mesh DFU. To use the tool with mesh DFU, use the mesh_dfu branch as mentioned above. See the tool's documentation for more information about installation and prerequisites.

    Best regards,
    Jørgen

Children
No Data
Related
Terms of service