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

Unable to flash target board using nrf52840 DK

gauthamranganathan

Hello, 

I am unable to flash target board using my nrf52840 Dev board. I have two dev boards and I am able to flash the target with the other dev board.

The target board is based on mdbtv50. 

I have not made any hardware changes to the Dev board. However, I am able to run any of the examples on the DK and it works fine. 

I have attached the J-link commander and nrf connect log files. Please assist me with this, 

2019-04-16T07:07:45.038Z INFO Application data folder: C:\Users\gauth\AppData\Roaming\nrfconnect\pc-nrfconnect-programmer
2019-04-16T07:07:45.231Z DEBUG App pc-nrfconnect-programmer v1.0.2 official
2019-04-16T07:07:45.231Z DEBUG App path: C:\Users\gauth\.nrfconnect-apps\node_modules\pc-nrfconnect-programmer
2019-04-16T07:07:45.231Z DEBUG nRFConnect 2.6.1 is supported by the app (^2.6.0)
2019-04-16T07:07:45.231Z DEBUG nRFConnect path: C:\Users\gauth\AppData\Local\Programs\nrfconnect\resources\app.asar
2019-04-16T07:07:45.231Z DEBUG HomeDir: C:\Users\gauth
2019-04-16T07:07:45.231Z DEBUG TmpDir: C:\Users\gauth\AppData\Local\Temp
2019-04-16T07:07:45.392Z INFO Using nrfjprog library 9.8.0, pc-nrfjprog-js 1.4.1
2019-04-16T07:07:50.367Z INFO Using nrfjprog to communicate with target
2019-04-16T07:07:51.843Z INFO Using J-Link Software version 6.40
2019-04-16T07:07:52.945Z INFO Segger serial: 683578621
2019-04-16T07:07:52.945Z INFO Segger speed: 2000 kHz
2019-04-16T07:07:52.945Z INFO Segger version: J-Link OB-SAM3U128-V2-NordicSemi compiled Jan 7 2019 14:07:15
2019-04-16T07:07:52.946Z INFO Probed: 683578621.
2019-04-16T07:07:52.946Z INFO Model: NRF52840_xxAA_REV1.
2019-04-16T07:07:52.946Z INFO RAM: 256KiB.
2019-04-16T07:07:52.946Z INFO Flash: 1024KiB in pages of 4KiB.
2019-04-16T07:07:54.232Z INFO Reading device non-volatile memory. This may take a few seconds.
2019-04-16T07:08:11.533Z INFO Using nrfjprog to communicate with target
2019-04-16T07:08:12.694Z INFO Using J-Link Software version 6.40
2019-04-16T07:08:13.533Z INFO Segger serial: 683578621
2019-04-16T07:08:13.533Z INFO Segger speed: 2000 kHz
2019-04-16T07:08:13.533Z INFO Segger version: J-Link OB-SAM3U128-V2-NordicSemi compiled Jan 7 2019 14:07:15
2019-04-16T07:08:13.533Z INFO Probed: 683578621.
2019-04-16T07:08:13.533Z INFO Model: NRF52840_xxAA_REV1.
2019-04-16T07:08:13.534Z INFO RAM: 256KiB.
2019-04-16T07:08:13.534Z INFO Flash: 1024KiB in pages of 4KiB.
2019-04-16T07:08:14.653Z INFO Reading device non-volatile memory. This may take a few seconds.
2019-04-16T07:08:29.462Z INFO Non-volatile memory has been read. 1 non-empty memory blocks identified.

Thank you, 

Parents
  • 0

    Hi

    Andreas is travelling, so I will be taking your case. If you can't provide a picture, I'll take your word for it as far as hardware connections go. Are there no differences in the two DKs other than one not being able to flash the target device? Are you able to flash any other chips if you have any available? Are the debugger versions the same as well?

    I.E.
    1.0.0
    2018.17
    123456xxx (or something)

    What exactly happens when you try flashing the target device? Do you get any error codes?

    Best regards,

    Simon

  • 0 in reply to Simonr

    When i connect the faulty DK to the custom board and hook up the DK to my computer, I do not see the target device on nRFgo studio. when I try to program an application/softdevice it gets programmed on the DK instead of the custom board. 

    The faulty one has the following version numbers

    1.0.0

    2018.33

    683578621

    the one which is working well has the following version numbers

    1.0.0

    2018.49

    683886294

Reply Children
No Data
Related