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
  • Hakson,

    The error started showing on four pre-production boards suddenly. We doubt this could be caused due to handling. The nrf52832 were assembled by our contract manufacture. Could you provide instructions on how to swap the chips?

    Also, are there any hardware checks we could do by probing any of nrf52832 pins? 

  • Hi,

    NANDHU said:
    The error started showing on four pre-production boards suddenly

    What was done to all the boards prior to when this happened? If all boards stopped working at the same time, there should be a common denominator.

      

    NANDHU said:
    We doubt this could be caused due to handling. The nrf52832 were assembled by our contract manufacture. Could you provide instructions on how to swap the chips?

    Here is a video on how to change a QFN IC: https://www.youtube.com/watch?v=_1PXEp0RQ7s

    If you are unsure on how to do this, I would recommend getting help from a colleague or the contract manufacturer.

     

    NANDHU said:
    Also, are there any hardware checks we could do by probing any of nrf52832 pins? 

    You can check the current consumption, and the voltage to ensure that is OK. You could also check certain GPIOs to see if they behave as defined in the firmware that is currently loaded onto the devices.

     

    Kind regards,

    Håkon

Reply
  • Hi,

    NANDHU said:
    The error started showing on four pre-production boards suddenly

    What was done to all the boards prior to when this happened? If all boards stopped working at the same time, there should be a common denominator.

      

    NANDHU said:
    We doubt this could be caused due to handling. The nrf52832 were assembled by our contract manufacture. Could you provide instructions on how to swap the chips?

    Here is a video on how to change a QFN IC: https://www.youtube.com/watch?v=_1PXEp0RQ7s

    If you are unsure on how to do this, I would recommend getting help from a colleague or the contract manufacturer.

     

    NANDHU said:
    Also, are there any hardware checks we could do by probing any of nrf52832 pins? 

    You can check the current consumption, and the voltage to ensure that is OK. You could also check certain GPIOs to see if they behave as defined in the firmware that is currently loaded onto the devices.

     

    Kind regards,

    Håkon

Children
No Data
Related