nrf5340PDK/DK interface MCU FW

[Smile Jiang]

Hi ,Support Team

       My customer is using our nrf5340PDK, their wrong operation caused the DK board become unrecognizable. I use the newest nRF-Command-Line-Tools_10_11_1 to recover it, but it still not work just the same phenomenon like this case:https://devzone.nordicsemi.com/f/nordic-q-a/65640/error-could-not-fetch-memory-size-of-target-devkit-error-error-occured-when-get-library-info-errorcode-couldnotopendevice-0x4-lowlevel-error-jlinkarm_dll_error-ffffff9a,  the ticket still waiting for final conclusion.

      I try to use nrfjprog,but it still not not recognized:

     So I suppose update the interface MCU is a method,but I cannot find the FW from our website,  did we release the interface MCU FW for nrf5340PDK/DK??

     If not, what's the possible solution to the customer's issue?

BR 

Smile

[Håkon Alseth]

Hi,

 

My customer is using our nrf5340PDK, their wrong operation caused the DK board become unrecognizable. I use the newest nRF-Command-Line-Tools_10_11_1 to recover it, but it still not work just the same phenomenon like this case:https://devzone.nordicsemi.com/f/nordic-q-a/65640/error-could-not-fetch-memory-size-of-target-devkit-error-error-occured-when-get-library-info-errorcode-couldnotopendevice-0x4-lowlevel-error-jlinkarm_dll_error-ffffff9a,  the ticket still waiting for final conclusion.

      I try to use nrfjprog,but it still not not recognized:

This is different than your use-case. You can access all libraries etc for Segger JLink, its that you cannot connect to the nRF.

To erase the network core, run this:

nrfjprog --recover --coprocessor CP_NETWORK -f nrf53

To erase the app core, run this.

nrfjprog --recover --coprocessor CP_APPLICATION -f nrf53

 

You can also add a "--log" to create a logfile to upload here.

 

 So I suppose update the interface MCU is a method,but I cannot find the FW from our website,  did we release the interface MCU FW for nrf5340PDK/DK??

     If not, what's the possible solution to the customer's issue?

 This doesn't have anything to do with the interface MCU, more towards why nRF5340 is locked down.

Which JLink version are you running? This should be posted when calling "nrfjprog --version".

 

You should be running a fairly new JLink (v6.80 or newer).

Could you try opening up J-Link Commander and connecting via this tool? Please paste a screenshot with the error code if it still fails.

 

Kind regards,

Håkon

[Smile Jiang]

Hi Hakon,

      The jlink version is v6.86f, I try to recover the DK with the command you provide, namely:

          nrfjprog --recover --coprocessor CP_NETWORK -f nrf53

          nrfjprog --recover --coprocessor CP_APPLICATION -f nrf53

     but the JLinkARM DLL reported an error with the log file: 

Fullscreen log1119.log Download

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

     I also try to open it with J-Link Commander, it can recognize ,like this:

    

   so I use 'erase' cmd(because I already tested on my nrf52840DK, it was worked), but on this nrf53DK, it failed:

   

I'm not sure what wrong operations had done on this DK previously, but now it's still unprogrammable

BR

Smile

[Håkon Alseth]

Hi Smile,

 

Thanks for the detailed logs.

It seems that it isn't able to communicate with the nRF at all. No contact over DP, so I suspect that there might be a hardware issue here.

Are any of the "nRF current measurement" solder bridges cut? Is the kit in any way modified?

 

Kind regards,

Håkon

[Smile Jiang]

Hi Hakon

      I checked that it suffered two wrong operations:

       1. Wrongly program the nrf52840' FW to the board by SES;

       2. Then found the board cannot program normally, so wrongly update the nrf52840DK's interface MCU hex to the 5340DK, but it still cannot work.

      There isn't any solder bridges cut.

      So seems like a HW issue?

BR

Smile

[Håkon Alseth]

Hi,

 

Smile Jiang said:

       2. Then found the board cannot program normally, so wrongly update the nrf52840DK's interface MCU hex to the 5340DK, but it still cannot work.

If you suspect that the SEGGER IC is not working as it should, you can try to connect an external debugger (note: must support Cortex M33! Older debuggers doesn't)  to the P18 debug in connector:

https://infocenter.nordicsemi.com/topic/ug_nrf5340_pdk/UG/nrf5340_PDK/hw_debug_in_trace.html?cp=3_0_4_4_8

 

If that still doesnt work, then its not likely its the debugger part that is the problem.

 

Smile Jiang said:

      So seems like a HW issue?

I'm not ruling that out, but the problem can be local to the DK as well, not only the nRF IC. 

 

Kind regards,

Håkon