Re: [OpenOCD-user] Openocd does not appear to reset the target properly.

[Paul F. <fer...@gm...>]

On Sat, Jun 21, 2025 at 04:28:33PM -0700, Thomas D. Dean wrote:
> On 6/21/25 15:49, Paul Fertser wrote:
> > On Sat, Jun 21, 2025 at 03:31:56PM -0700, Thomas D. Dean wrote:
> > > If I
> > > 1. connect the RPi debug probe to USB and pico_w.
> > > 2. power on the pico_w.
> > > 3. sudo openocd -f interface/cmsis-dap.cfg -f target/rp2040.cfg \
> > >       -c "adapter speed 5000" -c "program $1 verify reset exit"
> > 
> > This looks correct, I have nothing to suggest here.
> > 
> > > Openocd seems to finish without error.
> > > 
> > > Attempting to connect with firefox never does, just sets there
> > > spining.
> > 
> > And here I would suggest to connect with GDB to see what it is doing
> > and why it is stuck where.
> > 
> > > I noticed that cmake says the build type for my project is release, the
> > > *.elf file has debug symbols. and openocd output has debug and breakpoint.
> > 
> > Debug symbols are used by GDB, OpenOCD doesn't parse any of it from
> > ELF. And BTW, adding full debug information doesn't increase the
> > amount of flash used, it's all in special ELF sections which are not
> > copied to the target at all.
> > 
> 
> I looked with gdb. The code is in a while loop, waiting for the html, as it
> should be.
> 
> The only concern is the need to cycle power after writing flash.

I hope looking with GDB before power cycling should provide the
clues about what specifically is different with power-on-reset
vs. SYSRESETREQ.

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fer...@gm...