NRF52840 DK log file

RE: NRF52840 DK log file

Amanda Hsieh — Mon, 19 Apr 2021 09:00:05 GMT

Hi Pan,

Sorry for the delay.

Please try nrfjprog --recover -f nRF52. If it still gets errors, please provide the log with nrfjprog --recover -f nRF52 --log.

-Amanda H.

RE: NRF52840 DK log file

Pan Yinliang — Tue, 23 Mar 2021 03:08:17 GMT

Hi Amanda,

Thanks for your kind reply.

Board version is PCA10056, kindly pls check the attached picture

Thanks and Best Regards

Pan Yinliang

RE: NRF52840 DK log file

Amanda Hsieh — Mon, 22 Mar 2021 12:25:19 GMT

Hi Pan,

Thanks for the log file.

What is the board version on the white sticker?

-Amanda H.

RE: NRF52840 DK log file

Pan Yinliang — Sat, 20 Mar 2021 06:52:44 GMT

Hi Amamder,

Could you pls tell us how to upload the log file? Since it's just a text file, kindly pls check it in attachment.devzone.nordicsemi.com/.../0511.log.log

Pan Yinliang

RE: NRF52840 DK log file

Amanda Hsieh — Thu, 18 Mar 2021 12:35:09 GMT

Hi Pan,

[quote user="Pan Yinliang"] we are using nRF52840 DK, the power supply is around 5V as we connected the board to PC through USB cable.[/quote]

Please modify the power to 3.3v.

[quote user="Pan Yinliang"][2021-Mar-17 21:02:18] [debug] [Backend] - ---just_get_num_emus
[2021-Mar-17 21:02:18] [debug] [ nRF0x0] - connect_to_emu_with_snr
[2021-Mar-17 21:02:18] [debug] [nRFU[/quote]

The log is not completed. Please upload the file named log.log under C:\Users\Administrator. Thanks.

-Amanda H.

RE: NRF52840 DK log file

Pan Yinliang — Thu, 18 Mar 2021 12:10:31 GMT

Hi Amanda,

Thank you for your kind reply.

Yes, we are using nRF52840 DK, the power supply is around 5V as we connected the board to PC through USB cable. The new error is as below after tying the command as you suggested, could you pls help check what happened?

[2021-Mar-17 21:02:18] [ info] --------------------------------------------------------------------------------
[2021-Mar-17 21:02:18] [ info] nrfjprog --recover --log
[2021-Mar-17 21:02:18] [ info] nrfjprog version 10.12.1
[2021-Mar-17 21:02:18] [ info] --------------------------------------------------------------------------------
[2021-Mar-17 21:02:18] [debug] [ nRF0x0] - open_dll
[2021-Mar-17 21:02:18] [ info] [ nRF0x0] - Load library at C:\Program Files (x86)\Nordic Semiconductor\nrf-command-line-tools\bin\JLINKARM_UNKNOWN_NRFJPROG.dll.
[2021-Mar-17 21:02:18] [ info] [ nRF0x0] - Library loaded, loading member functions.
[2021-Mar-17 21:02:18] [ info] [ nRF0x0] - Member functions succesfully loaded.
[2021-Mar-17 21:02:18] [ info] [Backend] - Logger callback at 0xe22020 registered in Segger backend logger.
[2021-Mar-17 21:02:18] [ info] [ JLink] - [Info ] [JLink ] Logger callback at 0xe22020 registered in JLink logger.
[2021-Mar-17 21:02:18] [debug] [nRFUnknown] - Just_open_dll_tagged_callback
[2021-Mar-17 21:02:18] [debug] [Backend] - open_dll
[2021-Mar-17 21:02:18] [ info] [Backend] - No J-Link DLL path was provided. Attempting to auto detect.
[2021-Mar-17 21:02:18] [ info] [Backend] - Load library at C:\Program Files (x86)\SEGGER\JLink\JLinkARM.dll.
[2021-Mar-17 21:02:18] [ info] [Backend] - Library loaded, loading member functions.
[2021-Mar-17 21:02:18] [ info] [Backend] - Member functions succesfully loaded.
[2021-Mar-17 21:02:18] [debug] [Backend] - dll_version
[2021-Mar-17 21:02:18] [ info] [Backend] - Segger dll version 6.88.a loaded.
[2021-Mar-17 21:02:18] [debug] [Backend] - set_core_data
[2021-Mar-17 21:02:18] [debug] [ nRF0x0] - enum_emu_snr
[2021-Mar-17 21:02:18] [debug] [nRFUnknown] - Just_enum_emu_snr
[2021-Mar-17 21:02:18] [debug] [Backend] - enum_emu_snr
[2021-Mar-17 21:02:18] [debug] [Backend] - ---just_enum_emu_snr
[2021-Mar-17 21:02:18] [debug] [Backend] - ---just_get_num_emus
[2021-Mar-17 21:02:18] [debug] [ nRF0x0] - connect_to_emu_with_snr
[2021-Mar-17 21:02:18] [debug] [nRFU

Thanks and Best Regards

Pan Yinliang

RE: NRF52840 DK log file

Amanda Hsieh — Thu, 18 Mar 2021 07:02:07 GMT

Hi Pan,

Are you using nRF52840 DK?

Please make sure the power supply is 3.3v. You can check by the J-Link Commander to see the detected VTref.

Please upload the file named log.log under C:\Users\Administrator. Thanks.

-Amanda H.

RE: NRF52840 DK log file

Pan Yinliang — Wed, 17 Mar 2021 13:19:35 GMT

Hi Amanda,

Thank you for your kind prompt reply.

Tried with your suggestion, problem still exist as below:

C:\Users\Administrator>nrfjprog -v
nrfjprog version: 10.12.1
JLinkARM.dll version: 6.88a

C:\Users\Administrator>nrfjprog --recover
ERROR: nrfjprog could not identify the target device. This may be due to an
ERROR: invalid family argument, a problem with your device, or nrfjprog may
ERROR: not yet support your device.
ERROR: Please check the family argument passed, or upgrade nrfjprog to a more
ERROR: recent version.

C:\Users\Administrator>nrfjprog --recover --log
ERROR: nrfjprog could not identify the target device. This may be due to an
ERROR: invalid family argument, a problem with your device, or nrfjprog may
ERROR: not yet support your device.
ERROR: Please check the family argument passed, or upgrade nrfjprog to a more
ERROR: recent version.

Thanks and Best Regards

Pan Yinliang

RE: NRF52840 DK log file

Amanda Hsieh — Wed, 17 Mar 2021 12:38:19 GMT

Hi Pan,

[quote user="Pan Yinliang"]C:\Users\Administrator>nrfjprog --recover
Recovering device. This operation might take 30s.
Erasing user code and UICR flash areas.[/quote]

The lats operation of nrfjprog --recover seems to work.

Can you check the issue is fixed or not? If not, you might need to update the command-line tool to the last version, and do nrfjprog --recover again. If it still fails, please provide log by typing nrfjprog --recover --log.

-Amanda H.

RE: NRF52840 DK log file

Pan Yinliang — Wed, 17 Mar 2021 12:28:53 GMT

Hi Amanda,

Thank you so much for your kind reply.

Yes, we are using nRF52840 DK, nrfjprog version: 10.8.0. After running nrfjprog --recover. it still fails, pls check the error as below for 1 nRF52840DK:

C:\Users\Administrator>nrfjprog -v
nrfjprog version: 10.8.0
JLinkARM.dll version: 6.70d

C:\Users\Administrator>nrfjprog --recover
ERROR: JLinkARM DLL reported an error. Try again. If error condition
ERROR: persists, run the same command again with argument --log, contact Nordic
ERROR: Semiconductor and provide the generated log.log file to them.

And for another board, the error is different which is as below:

C:\Users\Administrator>nrfjprog -v
nrfjprog version: 10.8.0
JLinkARM.dll version: 6.70d

C:\Users\Administrator>nrfjprog --recover
Recovering device. This operation might take 30s.
Erasing user code and UICR flash areas.

Could you pls help us analyze the reason?

Thanks and Best Regards

Pan Yingliang

RE: NRF52840 DK log file

Amanda Hsieh — Wed, 17 Mar 2021 08:17:27 GMT

Hi Pan,

Are you using nRF52840 DK?

What is command-line tool version? You can get it by typing nrfjprog -v.

Please run nrfjprog --recover. If it still fails, please provide the log.

-Amanda H.

RE: NRF52840 DK log file

Pan Yinliang — Wed, 17 Mar 2021 08:05:46 GMT

Hi, thank you so much for your reply, yes we tried this way before, but error still exsits, kindly pls see below:

C:\Users\Administrator\Desktop\PBA 325 010 - 2.06>nrfjprog --family NRF52 --program Je325_Bootloader.ihex
ERROR: JLinkARM DLL reported an error. Try again. If error condition
ERROR: persists, run the same command again with argument --log, contact Nordic
ERROR: Semiconductor and provide the generated log.log file to them.

RE: NRF52840 DK log file

sethu — Wed, 17 Mar 2021 04:07:55 GMT

Hey,

It could have been because you have accidentally erased the firmware for the JLink chip on your DK. It happens when u power cycle with the reset pin pressed. All you need to do is press the reset button and try turning on the DK again, the light on the DK will blink and the DK will be shown as a bootable device on ur PC, if that works out you just have to download the binary of the firmware (link) used by the interface chip and drag and drop it onto the bootable device, after that power cycle the DK (without pressing the reset button) and everything should be back to normal. Please do refer to this answer (link) by @Bjørn Kvaale for reference.

Cheers.