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

Devices stuck in high current debug mode.

modles

Hi. I have an urgent issue where after using the JLINK disk programming function on the NRF52-DK, my device is stuck in high current (3ma) debug mode until power is cycled. I have several devices out in the field that are stuck in this mode due to non cycling of the power. I can perform and OTA firmware update to these devices, so is there any sdk command or register change that I can make to kick these devices out of debug mode and back into normal mode!? Thanks
Ben

Parents
  • 0

    A bit late of a response. My team encountered this issue a couple months ago. We found it to be a bug in the driver for the JLINK Debugger we were using to program. Ultimately it was fixed by updating past v10.9.0 of the nRF Command Line Tools which updated the JLINK drivers.

    This was our experience of how the issue manifests:

    If the reset after programming flag is enabled and the programming pins are removed before the reset is completed at just the right time a JLINK error is generated and the JLINK will be glitched. Any subsequent programming would then cause target devices to remain in high current (3mA) debug mode. Only a full power cycle of the JLINK debugger returned the debugger to a safe state.

    We were able to reproduce this consistently after realizing what glitches the JLINK.

    The change notes for nrf-command-line-tools v10.9.0 states it has been fixed. 

    I would add a check for any errors returned by nrfjprog and power cycle your JLINK if anything arises.

    I would also power cycle your target device right after programming and before casing up as a precaution.

Reply
  • 0

    A bit late of a response. My team encountered this issue a couple months ago. We found it to be a bug in the driver for the JLINK Debugger we were using to program. Ultimately it was fixed by updating past v10.9.0 of the nRF Command Line Tools which updated the JLINK drivers.

    This was our experience of how the issue manifests:

    If the reset after programming flag is enabled and the programming pins are removed before the reset is completed at just the right time a JLINK error is generated and the JLINK will be glitched. Any subsequent programming would then cause target devices to remain in high current (3mA) debug mode. Only a full power cycle of the JLINK debugger returned the debugger to a safe state.

    We were able to reproduce this consistently after realizing what glitches the JLINK.

    The change notes for nrf-command-line-tools v10.9.0 states it has been fixed. 

    I would add a check for any errors returned by nrfjprog and power cycle your JLINK if anything arises.

    I would also power cycle your target device right after programming and before casing up as a precaution.

Children
No Data
Related
Terms of service