ISSUES DUE TO "UNABLE TO FIND OR OPEN THE JlinkARM.dll"

[NANDHU]

HI,

•  We are mainly using "nRFgo Studio" and "nRF Connect" application for erasing and flashing codes to our custom board and its taking place successfully for a long time.
• The hardware tools we are using for flashing the code is "J-LINK BASE " version 10.1.
• But now  we can't able to flash or erase the code to our custom board either with "nRFgo Studio" or nRF  Connect.I don,t known why its happening?

When i tried to erase the code in our custom board using "nRFgo Studio"

When i tried to read our custom board using "nRF_Connect" its not reading look the below screen shot

DOUBTS

• What is the reason behind these issues?
• Is it a problem with our custom board or with jlink tool?
• What are the solution for these problems?

Please reply as soon as you can possible . Its a major issue with us.

[Håkon Alseth]

Could you share a picture of your physical setup (debugger + device)?

Have you tried this on another PC? The error messages shown now looks to be related to your debugger, not the actual connection to the nRF, as shown in your attached picture:

  

Kind regards,

Håkon

[NANDHU]

Hakson,

Leave that error part in log terminal. Its came when i try to remove the connection between jlink and nrf device after waited for long time .

The only thing showing on the log terminal is "using nrfjprog to communicate with target" .

I told you already  that without firmware the same issue is showing . Is there any solution for that?

[NANDHU]

Håkon Alseth said:

Have you tried this on another PC?

 yes in all pc the same issues are showing.

Look these screen shot all your doubts will clear

[NANDHU]

[1.Can you verify that you can program one of our nRF52832 Dev Kits using the software on your PC?  This will use the on board SWD programmer which might help isolate the issue.] 

The above question is asked by an engineer from nordic to us .

 yes , we can able to flash the codes on to nRF52832 Dev Kits using the software on our pc . Also we were able to flash the codes to the older boards(older version of boards). So we think our flashing hardware(j-link) is working fine. 

 

[Håkon Alseth]

Hi Nandhu,

 

After recovering the device, did you flash the same .hex file to it again?

If there is a assertion occurring in the very beginning, it will be hard to recover again.

For debugging purposes, try adding a nrf_delay_ms(100); in the top of your main, or add preprocessor define "DEBUG" to your project to enable blocking assertions.

 

I also see that there are several mechanical links between the debugger and the nRF, are all these connections tested to be working?

PS: You should not use normal tape on electronics, as tape will generate a high ESD spike when applied, moved, or removed, and this can damage electronics. You should use ESD-safe tape.

Kind regards,

Håkon