• State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 93 subscribers
  • Views 572 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 292269
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

52840 10056 DK problem

fmar

Hello Nordic Team,

I have an issue on one of my 10056 DK.  The DK is connected to a development PC, appears in device manager as a Jlink CDC UART port, and as a mass storage drive.

When debugging from Segger Embedded Studio, the jlink seems to work (fw downloaded to flash), but the debugging session does not stops neither at the beginning of my main(), neither at breakpoints. CPU registers do not show up any values, as if there is no connection to the target. This happens for any project I'v tried.

Note that:

1. if I simply switch to a second 10056 DK, anything goes fine

2. I've completed the checklist in   My nRF52/nRF51 DK kit doesn't work. except for step 7 (not sure if it apllies)

Any idea?

thanks

Parents Reply Children
  • 0 in reply to Jared

    Hi Jared,

    it seems I solved (90%) the issue. All the (example) projects I was using do use a softdevice, which was not loaded (anymore) on the DK. Manually loading the softdevice on the DK apparently solved the issue. 

    However (last 10%) I could not still figure out why this has happened, and why in the build/deploy/debug chain of events not even a warning came out.

    Regards,

    Francesco

  • 0 in reply to fmar

    Hi,

    Yes, I suspected that this was the root cause. Softdevice examples needs the Softdevice to be flashed for it to start. Usually, our examples are pre-configured so that it flash the Softdevice automatically when you flash with the SES IDE. Check if the Softdevice is listed as additonal load file in the project settings in SES. Note that you have to change the configuration in the upper left corner from release to common: 

    regards

    Jared

  • 0 in reply to fmar

    Hi Jared,

    I can confirm the Softdevice is (and was) listed as additional load file in the project settings. Also, the project file itself is under version control, so there's no chance for me to inadvertently modify this setting.

    Now (after manually loading the softdevice once) everything works fine, so I guess we can close the ticket up until I find a way to reproduce the situation.

    Thanks.

    Francesco

Related
Terms of service