pico w isn't supported? about debugprobe

[pawsaw]

Hi, what is the status of this? Lost many hours coming to this conclusion: picoprobe doesn't work on pico w.

It would be great, either to support pico w or update the documentation.

[fpaterra]

I was not able to get it to work, I think something changed and there is an incompatibility with PicoProbe on a pico (non-w or w) targeting a pico-w. I moved to using the Pico Debug Probe hardware device and it worked immediately so I would recommend buying one of those (~$25).

[kilograham]

yeah there is no regular LED on the Pico W; it would seem reasonable to allow building without a LED.

It would be a separate task to make a PicoW build that actually uses the onboard LED (which is accessed via the WiFi chip)

[pingufreak]

I'm using a normal pico right now, anyways, it's really slow.

[meltdown03]

It is supported, just use cmake --DPICO_BOARD=pico_w .. in place of cmake ..

[lurch]

@P33M Does the picoprobe.uf2 at https://github.com/raspberrypi/picoprobe/releases/tag/picoprobe-cmsis-v1.0.3 work on the Pico W, or should there be a picow-specific UF2 file there too?

[P33M]

@P33M Does the picoprobe.uf2 at https://github.com/raspberrypi/picoprobe/releases/tag/picoprobe-cmsis-v1.0.3 work on the Pico W, or should there be a picow-specific UF2 file there too?

No, flashing that will result in nonfunctional wireless. It needs a board include file similar to debugprobe.

[meltdown03]

@P33M Does the picoprobe.uf2 at https://github.com/raspberrypi/picoprobe/releases/tag/picoprobe-cmsis-v1.0.3 work on the Pico W, or should there be a picow-specific UF2 file there too?

No, flashing that will result in nonfunctional wireless. It needs a board include file similar to debugprobe.

What ends up without wireless, the debug target board? I only have one Pico W so I cant check how it debugs another Pico W.

[Ziothh]

So erm I compiled picoprobe with cmake -DPICO_BOARD=pico_w .. && make (needs to be one tick instead of two) and when I flash /build/picoprobe.uf2 to my Pico W, the LED still doesn't light up.

Since it doesn't need the WIFI functionality the LED should be able to work. Am I missing something?

[lurch]

On the Pico W, the LED is controlled by a GPIO on the WiFi chip, rather than by a GPIO on the RP2040 chip (which is why there's separate blink example-code for Pico and PicoW). And it sounds like PicoProbe doesn't have code to explicitly support the PicoW's LED?

However the good news is that PicoProbe does have explicit support for the DebugProbe.

[yahyatawil]

Just for confirmation. I've used -DPICO_BOARD=pico_w and uploaded the new .uf2 to Pico W. I was able to run the Openocd. Also sudo dmesg | tail -f command can be helpful to check.

Note: For some reason I can hear a resonance from the wifi module when my ear is close to the board.

[fpaterra]

I'm having this same problem. I've tried different Pico and I'm able to start OpenOCD with picoprope loaded on a non-W pico connected to a non-W pico but when I attempt to start with picoprobe loaded on a non-W pico attached to a pico-w, OpenOCD fails with Error: Failed to connect multidrop rp2040.dap0. If I run with the -d flag the specific failures I get are

Error: 709 539 adi_v5_swd.c:328 swd_connect_multidrop(): Failed to connect multidrop rp2040.dap0
Debug: 710 539 command.c:529 exec_command(): Command 'dap init' failed with error code -4
User : 711 539 command.c:601 command_run_line():
Debug: 712 539 command.c:529 exec_command(): Command 'init' failed with error code -4

Thanks in advance for any help!

[lurch]

@fpaterra AFAIK that should work fine - have you double-checked your wiring?

[fpaterra]

@fpaterra AFAIK that should work fine - have you double-checked your wiring?

Thanks for your reply @lurch. I have doubled checked and had other look over them as well. I also tried switching out the specific pico boards used both the picoprobe host as well as the pico w target. I'm sure I have some thing wrong but I've spent hours on this have not been able to gain any insight. Is there more debugging action I can do to help identify what is wrong?

Thank you again for your help!

[fpaterra]

Interesting. When I connect a Pico Debugger Probe (https://www.raspberrypi.com/documentation/microcontrollers/debug-probe.html) and run the same openocd command:
$ openocd -d -f interface/cmsis-dap.cfg -f target/rp2040.cfg -c "adapter speed 5000"

I get a similar error output, differing only in line numbers. Does this help? Any ideas?

Error: 685 532 adi_v5_swd.c:328 swd_connect_multidrop(): Failed to connect multidrop rp2040.dap0
Debug: 686 532 command.c:529 exec_command(): Command 'dap init' failed with error code -4
User : 687 532 command.c:601 command_run_line():
Debug: 688 532 command.c:529 exec_command(): Command 'init' failed with error code -4
User : 689 532 command.c:601 command_run_line():

I should also note that I get a series of repeating debug messages before these errors (like 10s or more of them) saying this:

Debug: 682 529 cmsis_dap.c:1257 cmsis_dap_swd_switch_seq(): JTAG-to-DORMANT
Debug: 683 530 cmsis_dap.c:1272 cmsis_dap_swd_switch_seq(): DORMANT-to-SWD
Debug: 684 531 cmsis_dap.c:946 cmsis_dap_swd_read_process(): SWD ack not OK @ 0 JUNK

I'm grateful for any help!

[fpaterra]

OK more in the saga. On a whim I attached the USB to power and now things are working using the pico debugger probe. I had tried that with the pico probe software on a non-w pico as well but it did not help. Hopefully I'm up and functional now.

[HyperNiki]

@fpaterra , Hello, I'm encountering the same issue with the Pico Probe. Have you had any success in resolving it? I attempted to address it by installing various versions of openoсd that align with the picoprobe versions (mostly around the same date), but unfortunately, the error persisted. The error message consistently appeared as 'DAP init failed' or 'Failed to connect multidrop rp2040.dap0,' along with the debugging information 'SWD ack not OK @ 0 JUNK' that you previously mentioned. I also made an effort to launch an older version of Ubuntu 18.04, installing both the old versions as well as new versions of openoсd and picoprobe in separate attempts, but I encountered the same error each time.

What's more, there were no such errors two months ago, and the debugger was launching successfully. It's puzzling how everything has changed now.
I would be very grateful for any help

[lurch]

On a whim I attached the USB to power and now things are working using the pico debugger probe.

For the benefit of other people who might run into the same problem, could you explain in more detail what you mean by "I attached the USB to power" please?