• State Verified Answer
  • Replies 33 replies
  • Subscribers 74 subscribers
  • Views 5405 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 237863
Options
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"

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.

Parents
  • 0
    Håkon Alseth said:
    If the center-pad (or other connections) isn't properly soldered, you will see instabilities like these.

     Hakon, We don't think that the issue is due to solder problem ,because if this issue was due to solder problem it will  show up from the initial stage of  testing .Actually we  started to face this issue only after a couple of weeks of testing, till then we were able to successfully read and write to the device.Also all the boards are showing up the issue simultaneously. 

    Note:- The hardware we are using is manufactured and  passed the QA test from an authorized company.   

Reply
  • 0
    Håkon Alseth said:
    If the center-pad (or other connections) isn't properly soldered, you will see instabilities like these.

     Hakon, We don't think that the issue is due to solder problem ,because if this issue was due to solder problem it will  show up from the initial stage of  testing .Actually we  started to face this issue only after a couple of weeks of testing, till then we were able to successfully read and write to the device.Also all the boards are showing up the issue simultaneously. 

    Note:- The hardware we are using is manufactured and  passed the QA test from an authorized company.   

Children
No Data
Related
Terms of service