SDK 2.1.0 and Debug probe

[eshea3]

After installing the new SDK 2.1.0 , the Pico does not reset and hangs after loading new elf file with openocd. Tried downloading the source for debugprobe and recompiling and that results in an "failed to connect to multidrop rp2040".

[lurch]

Have you tried the recently-released firmware update? https://github.com/raspberrypi/debugprobe/releases/tag/debugprobe-v2.1.0

[eshea3]

Downloaded one this morning, but that looks newer. Will try that now. Thanks

…

On Wed, Nov 27, 2024 at 1:10 PM Andrew Scheller ***@***.***> wrote: Have you tried the recently-released firmware update? https://github.com/raspberrypi/debugprobe/releases/tag/debugprobe-v2.1.0 — Reply to this email directly, view it on GitHub <#155 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABAXWVFMAHFUDONV4MKW3CD2CYDKDAVCNFSM6AAAAABSTNLPCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBUGUZDGMRXHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- *Ed Shea* ***@***.*** ***@***.***>* *410-852-0856*

[eshea3]

Tried that and still doesn't reset command is sudo openocd -f interface/cmsis-dap.cfg -f target/rp2040.cfg -c "adapter speed 5000" -c "program soil.elf verify reset exit" If I run the command sudo openocd -f interface/cmsis-dap.cfg -f target/rp2040.cfg -c "adapter speed 5000" -c "init; reset; exit" the Pico resets. I have tried this on multiple Picos and multiple projects. Only a dingle debug probe though

…

On Wed, Nov 27, 2024 at 1:12 PM Edward Shea ***@***.***> wrote: Downloaded one this morning, but that looks newer. Will try that now. Thanks On Wed, Nov 27, 2024 at 1:10 PM Andrew Scheller ***@***.***> wrote: > Have you tried the recently-released firmware update? > https://github.com/raspberrypi/debugprobe/releases/tag/debugprobe-v2.1.0 > > — > Reply to this email directly, view it on GitHub > <#155 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABAXWVFMAHFUDONV4MKW3CD2CYDKDAVCNFSM6AAAAABSTNLPCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBUGUZDGMRXHA> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> > -- *Ed Shea* ***@***.*** ***@***.***>* *410-852-0856*

-- *Ed Shea* ***@***.*** ***@***.***>* *410-852-0856*

[eshea3]

And I did delete the build directory and rebuild each project after updating the debugprobe firmware

…

On Wed, Nov 27, 2024 at 1:30 PM Edward Shea ***@***.***> wrote: Tried that and still doesn't reset command is sudo openocd -f interface/cmsis-dap.cfg -f target/rp2040.cfg -c "adapter speed 5000" -c "program soil.elf verify reset exit" If I run the command sudo openocd -f interface/cmsis-dap.cfg -f target/rp2040.cfg -c "adapter speed 5000" -c "init; reset; exit" the Pico resets. I have tried this on multiple Picos and multiple projects. Only a dingle debug probe though On Wed, Nov 27, 2024 at 1:12 PM Edward Shea ***@***.***> wrote: > Downloaded one this morning, but that looks newer. Will try that now. > Thanks > > On Wed, Nov 27, 2024 at 1:10 PM Andrew Scheller ***@***.***> > wrote: > >> Have you tried the recently-released firmware update? >> https://github.com/raspberrypi/debugprobe/releases/tag/debugprobe-v2.1.0 >> >> — >> Reply to this email directly, view it on GitHub >> <#155 (comment)>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/ABAXWVFMAHFUDONV4MKW3CD2CYDKDAVCNFSM6AAAAABSTNLPCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBUGUZDGMRXHA> >> . >> You are receiving this because you authored the thread.Message ID: >> ***@***.***> >> > > > -- > *Ed Shea* > ***@***.*** ***@***.***>* > *410-852-0856* > -- *Ed Shea* ***@***.*** ***@***.***>* *410-852-0856*

-- *Ed Shea* ***@***.*** ***@***.***>* *410-852-0856*

[lurch]

Pinging @will-v-pi as IIRC he looked at openocd recently?

[eshea3]

Update The Pico is actually rebooting. The projects I tested on had in common the following startup code stdio_init_all(); sleep_ms(2000); Removing the second line resolved the issue. I have no idea why that common throws things into a tizzy. Thanks for your help.

…

On Wed, Nov 27, 2024 at 1:54 PM Andrew Scheller ***@***.***> wrote: Pinging @will-v-pi <https://github.com/will-v-pi> as IIRC he looked at openocd recently? — Reply to this email directly, view it on GitHub <#155 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABAXWVGBBQ45GYSMPNGTOGD2CYIPZAVCNFSM6AAAAABSTNLPCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBUGU4DSMRWGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- *Ed Shea* ***@***.*** ***@***.***>* *410-852-0856*

[will-v-pi]

That’s a known issue with the 0.12.0 release of OpenOCD not working with sleeps (raspberrypi/pico-feedback#428) - it’s since been fixed, so this is probably unrelated to the 2.1.0 release and you’re likely using the wrong OpenOCD

[eshea3]

Thanks will look into it. But been using the same setup w/o problem until I installed 2.1.0.

…

On Wed, Nov 27, 2024, 3:44 PM will-v-pi ***@***.***> wrote: That’s a known issue with the 0.12.0 release of OpenOCD not working with sleeps (raspberrypi/pico-feedback#428 <raspberrypi/pico-feedback#428>) - it’s since been fixed, so this is probably unrelated to the 2.1.0 release and you’re likely using the wrong OpenOCD — Reply to this email directly, view it on GitHub <#155 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABAXWVET2OSX52XHRGSEWRD2CYVKNAVCNFSM6AAAAABSTNLPCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBUG42DCMBXGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Gerhard-Vienna]

Look here: raspberrypi/pico-sdk#2132
This is definitely a problem with the current 2.1.0 release.
As a temporary solution, switch the sdk to the development branch.

[eshea3]

Thanks I saw that earlier this week and already adjusted my call to openOCD

…

On Sun, Jan 12, 2025, 1:24 PM Gerhard Schiller ***@***.***> wrote: Look here: raspberrypi/pico-sdk#2132 <raspberrypi/pico-sdk#2132> This is definitely a problem with the current 2.1.0 release. As a temporary solution, switch the sdk to the development branch. — Reply to this email directly, view it on GitHub <#155 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABAXWVCUVAQB6PI2EWVL5NT2KKXPPAVCNFSM6AAAAABSTNLPCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBVHA2TSNJVGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[eshea3]

Adding -c "set USE_CORE 0" to the openocd invocation worked for me - no need to downgrade the SDK

…

On Sun, Jan 12, 2025 at 2:08 PM Edward Shea ***@***.***> wrote: Thanks I saw that earlier this week and already adjusted my call to openOCD On Sun, Jan 12, 2025, 1:24 PM Gerhard Schiller ***@***.***> wrote: > Look here: raspberrypi/pico-sdk#2132 > <raspberrypi/pico-sdk#2132> > This is definitely a problem with the current 2.1.0 release. > As a temporary solution, switch the sdk to the development branch. > > — > Reply to this email directly, view it on GitHub > <#155 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABAXWVCUVAQB6PI2EWVL5NT2KKXPPAVCNFSM6AAAAABSTNLPCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBVHA2TSNJVGY> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

-- *Ed Shea* ***@***.*** ***@***.***>* *410-852-0856*