This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

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

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.

Parents
  • Then i want inform you these.

    We have 4 four custom boards facing these issue.

    Among those four  i can able to recover one board by using batch file method you suggested .

    With the help of nrf_connect app i erased the firmware inside it.

    Then after sometimes i tried to connect the same device without firmware using nrf_connect app but the same issues where showing without firmware too. I can't read the device or erase device .

    If the issue is with firmware then how the same issue showing  after erasing the firmware?    

Reply
  • Then i want inform you these.

    We have 4 four custom boards facing these issue.

    Among those four  i can able to recover one board by using batch file method you suggested .

    With the help of nrf_connect app i erased the firmware inside it.

    Then after sometimes i tried to connect the same device without firmware using nrf_connect app but the same issues where showing without firmware too. I can't read the device or erase device .

    If the issue is with firmware then how the same issue showing  after erasing the firmware?    

Children
No Data
Related