• State Verified Answer
  • Replies 11 replies
  • Subscribers 88 subscribers
  • Views 3078 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 268236
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

NRF52840-DK Jlink detection failed

KLui

Hi, I used my NRF52840-DK for few times but suddenly the jlink connection was not detectable. Before the Jlink failed, the main controller on board did not bring up the board properly after switching on/off the power switch. USB connection was running after a reset on the main controller. I think the board needs reloading the firmware. Please provide me the procedures how to do it without a programmer. Thanks.

Parents Reply
  • 0 in reply to Einar Thorsrud

    The board does not get recognized at all. When I open the J-Link Configurator it tell me there is no compatible board detected. 

    And if it helps, this has happend to me with two boards. One was brand new and the other one was used for a while.

    Maybe some of the software that was on the board had an impact on the BOOTLOADER size? Is there a way to clear the board without using a programmer?

    I will not be able to test anything out until monday bec I am off work, then I will give it a try again.

Children
  • 0 in reply to Elias Bruggmann

    Hi,

    Elias Bruggmann said:
    And if it helps, this has happend to me with two boards. One was brand new and the other one was used for a while.

    That is interesting. Do you remember if something specific happened before this happened with the boards?

    Elias Bruggmann said:
    Maybe some of the software that was on the board had an impact on the BOOTLOADER size? Is there a way to clear the board without using a programmer?

    That should not be the case. The firmware on the nRF IC does not affect this, as this should be isolated to the onboard debugger (the big IC with the white sticker).

    I do not have any particular reason for suggesting this, but as I am not able to explain what happened: Can you check with another computer to see if you experience the same on that (available size is 100 instead of 108)? Also, can you list all files you see on the BOOTLOADER drive, including hidden files and the size of all of them?

  • 0 in reply to Einar Thorsrud
    Einar Thorsrud said:
    That is interesting. Do you remember if something specific happened before this happened with the boards?

    So I have just been assigned to this project a few days ago. I was told that the board that was used already stopped working right and that I should try to reinstal the J-Link firmware. Before it was programmed using nrfConnect.

    The new Board was programmed using nrfConnect and for our application I needed to deactivate the massstorage device using the J-Link Commander, but that did not work because it was not detected. After that error I decided to also try and reinstal the J-Link firware using the BOOTLOADER but on both boards got the problem that we are talking about here.

    Einar Thorsrud said:
    I do not have any particular reason for suggesting this, but as I am not able to explain what happened: Can you check with another computer to see if you experience the same on that (available size is 100 instead of 108)? Also, can you list all files you see on the BOOTLOADER drive, including hidden files and the size of all of them?

    I will do that as soon as Im back at work, on monday.

  • 0 in reply to Einar Thorsrud

    Alright the problem is solved. I tried it last week on another PC that did not help but this week I tried another one and the size was 108kB so enough for the file.

    Thank you for your help!

  • 0 in reply to Elias Bruggmann

    This is a bit of a mystery to me, but good to here it was resolved. Thanks for letting us know!

Related
Terms of service