Attachments (0)
Nordic Case Info
  • Case ID: 114646
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Creating a zip file for DFU master. Is nrf.exe replaced by nrfutil.exe?

mosi

I can't find nrf.exe in C:\Program Files (x86)\Nordic Semiconductor\Master Control Panel\3.10.0.14\nrf

I only find nrfutil.exe in that folder.

Shall I use nrfutil.exe?

Parents
  • 0

    Hi,

    Yes, you use nrfutil.exe. See Creating an image file on infocenter for details.

    Regards, Terje

  • 0 in reply to tesc

    Hi,

    --dev-revision and --dev-type are checked with the UICR registers, which both are set to 0xFFFF by default. By changing these registers you can mark different revisions of your device with different numbers, and make separate firmware updates for each device revision. This is unlike --application-version which is not checked by the DFU firmware.

    We do not have a list of --sd-req magic numbers. To find the value for a given SoftDevice version you can program that version to a board and find the code using nRFgo studio. It will appear under "Region 1 (SoftDevice)", under "Firmware:", in my case (a particular version of s132) it is "(Id: 0x006d)". Another approach is to look up SD_FWID_OFFSET in the nrf_sdm.h SoftDevice header file. It is the memory address offset where you will find the ID in the softdevice hex itself.

    Regards, Terje

Reply
  • 0 in reply to tesc

    Hi,

    --dev-revision and --dev-type are checked with the UICR registers, which both are set to 0xFFFF by default. By changing these registers you can mark different revisions of your device with different numbers, and make separate firmware updates for each device revision. This is unlike --application-version which is not checked by the DFU firmware.

    We do not have a list of --sd-req magic numbers. To find the value for a given SoftDevice version you can program that version to a board and find the code using nRFgo studio. It will appear under "Region 1 (SoftDevice)", under "Firmware:", in my case (a particular version of s132) it is "(Id: 0x006d)". Another approach is to look up SD_FWID_OFFSET in the nrf_sdm.h SoftDevice header file. It is the memory address offset where you will find the ID in the softdevice hex itself.

    Regards, Terje

Children
No Data
Terms of service