debugprobe not resonsive shortly after starting debug

[MNS26]

debugprobe not resonsive shortly after starting debug

[MNS26]

i remade my PlatformIO setup and now it is working (i quite dont know why but it works)

I will close the issue now

[lurch]

Does it work any more reliably if you set a slower adapter speed?

[MNS26]

tried setting the adapter speed to 500KHz and still the same issue

the moment i try and get the memory location of the buffer it broke (hovering mouse over it)

[lurch]

Ahh I see from your logfile that you're using Open On-Chip Debugger 0.11.0-g8e3c38f78-dirty so perhaps that's too old? https://github.com/raspberrypi/openocd is using rp2040-v0.12.0.

[MNS26]

managed to trigger it again but this time it threw a error message as well
that memory area is 255 bytes and where the I2C buffer lives
(i had to manually re-add it to the memory tab since the code changed)

[MNS26]

Ahh I see from your logfile that you're using Open On-Chip Debugger 0.11.0-g8e3c38f78-dirty so perhaps that's too old? https://github.com/raspberrypi/openocd is using rp2040-v0.12.0.

hmm odd... i never manually installed any openocd version. i will try that later (irl stuff -_-)
afaik PlatformIO handles the install of openocd

[MNS26]

hmm just had a look and i dont see a easy way to update the one from PlatformIO, the latest one they have is 10 months old PlatformIO openocd

[MNS26]

nope. . . using their latest version manually specified

and the output of the debug console

[MNS26]

oh interesting... even though i have VSCode closed it still has PlatformIO open.
I wonder if this might be a PlatformIO issue instead (i honestly dont know)

the project from the picture RP2040-HOTAS