Not able to flash nRF5340 PDK anymore

[sethu]

Hey guys, 

All of a sudden, I'm not able to flash my nRF board anymore. I get the following message when I try to connect to the board using segger IDE.

And when I try west flash, I get the following:

As per that message, when I try "west flash --log", I get unknow command error.

Any help would be appreciated. 

Other info:

I'm pretty sure that it isn't a problem with the code I'm trying to flash or even anything on the PC because I have another one of the same board which works without any problem.

[sethu]

I tried both the solutions mentioned but still no luck, both gave me error as shown below:

Nrfjprog and the nrf connect had been updated prior to executing the commands.

[Amanda Hsieh]

Please try the latest version of the nRF-Command-Line-Tools. If it still cannot fix the issue, run the following commands, and provide the logs. 

 

nrfjprog.exe --coprocessor CP_NETWORK --recover --log NETWORK.log
nrfjprog.exe --coprocessor CP_APPLICATION --recover --log APPLICATION.log

-Amanda H.

[sethu]

Hey,

[2020-Nov-17 09:16:34] [ info] --------------------------------------------------------------------------------
[2020-Nov-17 09:16:34] [ info] C:\Program Files (x86)\Nordic Semiconductor\nrf-command-line-tools\bin\nrfjprog.exe --coprocessor CP_APPLICATION --recover -f RF53 --log application.log 
[2020-Nov-17 09:16:34] [ info] nrfjprog version 10.11.1 
[2020-Nov-17 09:16:34] [ info] --------------------------------------------------------------------------------

Now that I run the command, this is the only output from the log file for both cases. 

Also, the command gives an error saying the following:

ERROR: Argument provided has a wrong value. Memory access not aligned, value
ERROR: outside of range or similar.

thanks

[Amanda Hsieh]

Sorry for the mistake, it is "-f NRF53". I have modified the previous commands. Please try again. 

-Amanda H.

[sethu]

Hey, 

No worries. I have done it again and both commands give almost the same output which has been attached below:

Fullscreen 6840.application.log Download

[2020-Nov-18 09:07:48] [ info] --------------------------------------------------------------------------------
[2020-Nov-18 09:07:48] [ info] C:\Program Files (x86)\Nordic Semiconductor\nrf-command-line-tools\bin\nrfjprog.exe --coprocessor CP_APPLICATION --recover -f NRF53 --log application.log 
[2020-Nov-18 09:07:48] [ info] nrfjprog version 10.11.1 
[2020-Nov-18 09:07:48] [ info] --------------------------------------------------------------------------------
[2020-Nov-18 09:07:48] [debug] [ nRF0x0] - open_dll
[2020-Nov-18 09:07:48] [ info] [ nRF0x0] - Load library at C:\Program Files (x86)\Nordic Semiconductor\nrf-command-line-tools\bin\JLINKARM_NRF53_NRFJPROG.dll.
[2020-Nov-18 09:07:48] [ info] [ nRF0x0] - Library loaded, loading member functions.
[2020-Nov-18 09:07:48] [ info] [ nRF0x0] - Member functions succesfully loaded.
[2020-Nov-18 09:07:48] [ info] [Backend] - Logger callback at 0xaf1610 registered in Segger backend logger.
[2020-Nov-18 09:07:48] [ info] [  JLink] - [Debug   ] [JLink     ] Logger callback at 0xaf1610 registered in JLink logger.
[2020-Nov-18 09:07:48] [debug] [nRF530x0] - open
[2020-Nov-18 09:07:48] [debug] [Backend] - open_dll
[2020-Nov-18 09:07:48] [ info] [Backend] - No J-Link DLL path was provided. Attempting to auto detect.
[2020-Nov-18 09:07:48] [ info] [Backend] - Load library at C:\Program Files (x86)\SEGGER\JLink\JLinkARM.dll.
[2020-Nov-18 09:07:48] [ info] [Backend] - Library loaded, loading member functions.
[2020-Nov-18 09:07:48] [ info] [Backend] - Member functions succesfully loaded.
[2020-Nov-18 09:07:48] [debug] [Backend] - dll_version
[2020-Nov-18 09:07:48] [ info] [Backend] - Segger dll version 6.86.f loaded.
[2020-Nov-18 09:07:48] [debug] [ nRF0x0] - enum_emu_snr
[2020-Nov-18 09:07:48] [debug] [nRF530x0] - enum_emu_snr
[2020-Nov-18 09:07:48] [debug] [Backend] - is_connected_to_emu
[2020-Nov-18 09:07:48] [debug] [Backend] - enum_emu_snr
[2020-Nov-18 09:07:48] [debug] [Backend] - ---just_enum_emu_snr
[2020-Nov-18 09:07:48] [debug] [Backend] - ---just_get_num_emus
[2020-Nov-18 09:07:48] [debug] [Backend] - is_connected_to_emu
[2020-Nov-18 09:07:48] [debug] [ nRF0x0] - connect_to_emu_with_snr
[2020-Nov-18 09:07:48] [debug] [nRF530x0] - connect_to_emu_with_snr
[2020-Nov-18 09:07:48] [debug] [Backend] - is_connected_to_emu
[2020-Nov-18 09:07:48] [debug] [Backend] - connect_to_emu_with_snr
[2020-Nov-18 09:07:48] [debug] [Backend] - is_connected_to_emu
[2020-Nov-18 09:07:48] [debug] [Backend] - ---just_enum_emu_snr
[2020-Nov-18 09:07:48] [debug] [Backend] - ---just_get_num_emus
[2020-Nov-18 09:07:48] [debug] [Backend] - ---just_connect_to_emu_with_snr
[2020-Nov-18 09:07:48] [debug] [Backend] - ---just_connect_to_emu_without_snr
[2020-Nov-18 09:07:48] [ info] [Backend] - Segger logging enabled.
[2020-Nov-18 09:07:48] [debug] [Backend] - ---just_load_core_data
[2020-Nov-18 09:07:48] [ info] [  JLink] - [Debug   ] [JLink     ] Device "CORTEX-M33" selected.
[2020-Nov-18 09:07:48] [debug] [Backend] - read_debug_port_idr
[2020-Nov-18 09:07:48] [debug] [Backend] - read_debug_port_register
[2020-Nov-18 09:07:48] [debug] [Backend] - ---just_read_debug_port_register
[2020-Nov-18 09:07:48] [debug] [Backend] - coresight_configure
[2020-Nov-18 09:07:48] [debug] [Backend] - ---just_select_debug_port_register
[2020-Nov-18 09:07:48] [debug] [Backend] - Select AP 255, DP Bank 0, AP Bank 255
[2020-Nov-18 09:07:48] [error] [  JLink] - [Debug   ] [JLink     ] Not supported by current CPU + target interface combination.
[2020-Nov-18 09:07:48] [ info] [Backend] - JLinkARM.dll reported "-2", an unknown error.
[2020-Nov-18 09:07:48] [debug] [Backend] - ---just_abort_debug_action
[2020-Nov-18 09:07:48] [ info] [Backend] - Attempting to clear any configuration errors in debug port before closing connection. 
[2020-Nov-18 09:07:48] [debug] [ nRF0x0] - close_dll
[2020-Nov-18 09:07:48] [debug] [nRF530x0] - close
[2020-Nov-18 09:07:48] [debug] [Backend] - is_connected_to_emu
[2020-Nov-18 09:07:48] [debug] [Backend] - close
[2020-Nov-18 09:07:48] [debug] [Backend] - disconnect_from_emu
[2020-Nov-18 09:07:48] [debug] [Backend] - ---just_disconnect_from_emu
[2020-Nov-18 09:07:48] [debug] [Backend] - is_connected_to_device
[2020-Nov-18 09:07:48] [debug] [Backend] - ---just_is_debug_region_powered
[2020-Nov-18 09:07:48] [debug] [Backend] - ---just_read_debug_port_register
[2020-Nov-18 09:07:48] [debug] [Backend] - ---just_select_debug_port_register
[2020-Nov-18 09:07:48] [debug] [Backend] - Select AP 255, DP Bank 0, AP Bank 255
[2020-Nov-18 09:07:48] [error] [  JLink] - [Debug   ] [JLink     ] Not supported by current CPU + target interface combination.
[2020-Nov-18 09:07:48] [ info] [Backend] - JLinkARM.dll reported "-2", an unknown error.
[2020-Nov-18 09:07:48] [debug] [Backend] - ---just_abort_debug_action
[2020-Nov-18 09:07:48] [ info] [Backend] - Attempting to clear any configuration errors in debug port before closing connection. 
[2020-Nov-18 09:07:48] [debug] [Backend] - Segger Backend closed.
[2020-Nov-18 09:07:48] [debug] [nRF530x0] - nRF family DLL closed

It is pretty similar to the output when the family parameter was not passed

[Amanda Hsieh]

Hi Sethu, 

Could you try the latest version of nrfjprog v10.12.1? 

https://www.nordicsemi.com/Software-and-tools/Development-Tools/nRF-Command-Line-Tools/Download

Please let me know it can help or not. Thanks. 

-Amanda 

[StefanHri]

I have the same issue. However, updating nrfjprog to version v10.12.1 did not help. I am using Ubuntu 20.04.

[Amanda Hsieh]

Hi, 

Please create a new support case with the recovery logs for the app and net core.

-Amanda H. 

[sethu]

Hey, 

It could have been because you have accidentally erased the JLink chip on your DK, it happened to me on a different board recently as well, 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 and everything should be back to normal. Please do refer to this answer (link)  by @Bjørn Kvaale for reference.

Cheers

(I don't have nrf5340 accessible anymore so couldn't check again with the same device)