From: Rob M. <Rob...@u-...> - 2024-04-23 17:51:04
|
Interesting: attached find the [non-debug I'm afraid] log output from a success case using OpenOCD with the Zephyr west tool, plus the openocd.cfg file it employs. In the openocd.cfg file it does indeed say: # Reset configuration # use hardware reset, connect under reset # connect_assert_srst needed if low power mode application running (WFI...) reset_config srst_only srst_nogate connect_assert_srst However, if I power the board down entirely and modify the reset_config line in my own stm32u5.cfg file to be the same as this I still, unfortunately, get the problem. There's something I'm missing here... Rob -----Original Message----- From: Paul Fertser <fer...@gm...> Sent: Tuesday, April 23, 2024 6:45 PM To: Rob Meades <Rob...@u-...> Cc: Tommy Murphy <tom...@ho...>; ope...@li... Subject: Re: [OpenOCD-user] Anyone using STM32U5 with OpenOCD? **** This is an EXTERNAL email. It was sent from outside of u-blox. **** On Tue, Apr 23, 2024 at 08:37:50PM +0300, Paul Fertser wrote: > On Tue, Apr 23, 2024 at 04:00:34PM +0000, Rob Meades wrote: > > Thanks for the swift response: verbose OpenOCD output attached. The > > odd thing is that this worked fine when OpenOCD was driven only by > > Zephyr's west tool, > > Is it possible it was using "reset_config srst_only > connect_assert_srst"? Indeed it was ... -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fer...@gm... |