• State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 88 subscribers
  • Views 1027 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 279484
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

NRF52840PDK core getting stuck after debugging using NRF Connect SDK1.7 and SES

annamol

We are using NRF52840PDK for development using NRF Connect SDK. We are facing an unusual behavior while using PDK. The development environment is Windows 10 and SES5.60 installed via NRF connect. The PDK works fine for examples using NRFSDK16. Jlink is getting enumerated properly.

While using examples from NRF Connect SDK, we are facing the issue listed below.

  • Code cannot be flashed via Build and run. There is no error message or warning. But code won't execute on target. 
  • Code can be flashed via debug and go 
  • Code can be flashed via Build and debug
  • Once code is downloaded onto the target and resumes execution, and if we are stopping the debug session by pressing the stop button, code will stop execution and will get stuck. Any attempt to reflash without unplugging the board will result in no idcode detected error as shown below. There are times at which multiple powercycle resets doesn't have an impact. 

 

To overcome this we tried running exec setRestartOnClose = 0 via Jlink commander and that helps in preventing code from getting stuck after stopping the debug session.

But NRF52840DK doesn't have this behavior. 

Has anyone ever faced similar issue?

Can that be solved by any other means?

What causes this behavior?

Parents
  • 0

    When we try to program the PDK using west, command prompt doesn't show any error messages, but code won't run.

    The same set of commands works fine with NRF52840DK.

    Do we need to change the board name while using west command for flashing?

  • +1 in reply to annamol

    Hi,

    This is most likely because the PDK is not supported in nRF Connect SDK. The PDK has an engineering SoC that is missing features and erratas that are in the later versions of the SoC. PDKs should only be used for evaluation purposes, and I would recommend getting a DK instead.

    Best regards,

    Marte

Reply
  • +1 in reply to annamol

    Hi,

    This is most likely because the PDK is not supported in nRF Connect SDK. The PDK has an engineering SoC that is missing features and erratas that are in the later versions of the SoC. PDKs should only be used for evaluation purposes, and I would recommend getting a DK instead.

    Best regards,

    Marte

Children
No Data
Related