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

RST Pin for SWD interface is necessary?

Lakerno

image description

I am using the Segger interface for designing an nRF52 based device. I am planning to use SWDIO SWCLK VTref and GND pins on my device. Is it necessary to connect the nRESET pin to the Reset pin of the NRF52 chip? If I dont connect this, will there be any issue with programming/flashing the device? what are the advantages/disadvantages? Can anyone kindly elaborate on this?

thank you!

Parents
  • 0

    I'm using a nRF51 device with a Keil ulink2 - I just have four wires to the nRF for Ground, Power, SWCLK and SWDIO which works for me (programming soft device, programming application code and debugging). My software isn't using any microcontroller sleep modes which have caused me issues on other processors (STM32).

    So the nRESET is not necessary.

    The nRF51 SWDIO is actually labelled SWDIO/nRESET so I expect that it is possible to reset the debug interface but I haven't had to do that.

    I expect that using a Segger interface won't make any difference as the wires are an ARM interface that doesn't care about the brand of debugger being attached.

Reply
  • 0

    I'm using a nRF51 device with a Keil ulink2 - I just have four wires to the nRF for Ground, Power, SWCLK and SWDIO which works for me (programming soft device, programming application code and debugging). My software isn't using any microcontroller sleep modes which have caused me issues on other processors (STM32).

    So the nRESET is not necessary.

    The nRF51 SWDIO is actually labelled SWDIO/nRESET so I expect that it is possible to reset the debug interface but I haven't had to do that.

    I expect that using a Segger interface won't make any difference as the wires are an ARM interface that doesn't care about the brand of debugger being attached.

Children
No Data
Related

core_v2_widget.Hide()