Hi Paul, Thanks for your answer and hints, when adding connect_assert_srst I obtain the following:
> Warn : 213 455 adi_v5_swd.c:117 swd_connect(): 'srst_nogate' reset_config > option is required > Debug: 214 459 cmsis_dap_usb.c:927 cmsis_dap_swd_switch_seq(): JTAG-to-SWD > Debug: 215 465 cmsis_dap_usb.c:730 cmsis_dap_swd_read_process(): SWD ack > not OK @ 0 JUNK > While on the board, the line for reset is connected to the SWD connector. I'm going to dig into the procedure to contact the target as you suggested and verify the reset line. Le lun. 6 juil. 2020 à 16:29, Paul Fertser <[email protected]> a écrit : > Hello, > > On Mon, Jul 06, 2020 at 04:14:46PM +0200, Benjamin Gutton wrote: > > reset_config srst_only > > Have you tried adding connect_assert_srst there? > > > Debug: 214 506 cmsis_dap_usb.c:730 cmsis_dap_swd_read_process(): SWD ack > not OK > > @ 0 JUNK > > So it looks like the target just doesn't respond. What is the > procedure to contact your target when it disables SWD or enters some > sleep mode? > > -- > Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! > mailto:[email protected] >
_______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
