Attachments (1) Download All
Nordic Case Info
  • Case ID: 306174
Options

Unable to flash hex file on nRF52840 USB Dongle using nRF Programmer tool

beparas

Hello Team,

I have started studying OpenThread. To test an OpenThread application, I bought an nRF52840 USB dongle.

I have built the FTD example using the following steps:


Fullscreen
1
2
3
4
5
$ cd ~/src/ot-nrf528xx
$ rm -rf build
$ script/build nrf52840 USB_trans -DOT_JOINER=ON -DOT_COMMISSIONER=ON
$ cd ~/src/ot-nrf528xx/build/bin
$ arm-none-eabi-objcopy -O ihex ot-cli-ftd ot-cli-ftd.hex
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Reference: https://openthread.io/codelabs/openthread-hardware#4

To flash the ot-cli-ftd.hex bin, I am planning to use nRF Programmer.

1] I connected the nRF52840 USB dongle to the PC.
2] Put nRF52840 USB dongle in DFU mode, indicated by the RGB LED pulsing RED.
3] Now I launched the Programmer application from nRF Connect for Desktop and selected the nRF52840 USB dongle.
4] I added the ot-cli-ftd.hex file by clicking the "Add file" button.
5] but the "Write" button is still disabled on the Programmer.





The programmer debug log is attached.

Fullscreen 2023-04-13T07_02_15.541Z-log.txt Download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
2023-04-13T07:02:15.635Z DEBUG Application data folder: /home/paras/.config/nrfconnect/pc-nrfconnect-programmer
2023-04-13T07:02:15.686Z DEBUG App pc-nrfconnect-programmer v3.0.8 local
2023-04-13T07:02:15.686Z DEBUG App path: /home/paras/.nrfconnect-apps/node_modules/pc-nrfconnect-programmer
2023-04-13T07:02:15.686Z DEBUG nRFConnect 4.0.1, required by the app is (>=4.0.0)
2023-04-13T07:02:15.686Z DEBUG nRFConnect path: /tmp/.mount_nrfcon4uTiLQ/resources/app.asar
2023-04-13T07:02:15.686Z DEBUG HomeDir: /home/paras
2023-04-13T07:02:15.686Z DEBUG TmpDir: /tmp
2023-04-13T07:02:15.698Z INFO Using nrf-device-lib-js version: 0.6.5
2023-04-13T07:02:15.698Z INFO Using nrf-device-lib version: 0.14.7
2023-04-13T07:02:15.698Z INFO Using nrfjprog DLL version: 10.19.1
2023-04-13T07:02:15.698Z INFO Using JLink version: JLink_V7.86e
2023-04-13T07:02:15.698Z DEBUG [nrfdl][debug](12:32:15.638) [jlink] [NRFJPROG][Client][] open
2023-04-13T07:02:15.698Z DEBUG [nrfdl][debug](12:32:15.638) [jlink] [NRFJPROG][Client][] start
2023-04-13T07:02:15.698Z DEBUG [nrfdl][debug](12:32:15.646) [jlink] [NRFJPROG][SeggerBackend][] Logger sink registered in Segger backend logger
2023-04-13T07:02:15.698Z DEBUG [nrfdl][debug](12:32:15.646) [jlink] [NRFJPROG][JLink][] Logger sink registered in JLink logger
2023-04-13T07:02:15.699Z DEBUG [nrfdl][debug](12:32:15.646) [jlink] [NRFJPROG][nRFXX][] open
2023-04-13T07:02:15.699Z DEBUG [nrfdl][debug](12:32:15.646) [jlink] [NRFJPROG][nRFXX][] just_check_family
2023-04-13T07:02:15.699Z DEBUG [nrfdl][debug](12:32:15.646) [jlink] [NRFJPROG][SeggerBackend][] open_dll
2023-04-13T07:02:15.699Z DEBUG [nrfdl][debug](12:32:15.646) [jlink] [NRFJPROG][SeggerBackend][] No J-Link DLL path was provided. Attempting to auto detect.
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Could you please help me to resolve this issue?

Test setup


1] On the PC Ubuntu, 20.04.6 LTS is running. 
2] The nRF Connect for Desktop (v4.0.1) is running on Ubuntu.
3] nRF Programmer v3.0.8
4] nRF52840 USB Dongle information

  • Board number (PCA10059)
  • Hardware revision: 2.1.1
  • Production year and week (2023.2)

Terms of service