I am reasonably experienced in embedded systems and can say that fighting tool chains is a massive waste of time. These videos are first class, well done!
Yes please! Plus-n for the part-2. You deserve more subs than you've got. I'm new to C and wouldn't have chosen to go with it were it not for your tutorials. Thank you.
Thank you for this clear tutorial! A Part 2 would be helpful, especially for those of us who are trying to wean ourselves from the Arduino IDE, but are accustomed to being able to plug the Pico into USB and download the code to it. I think that is only possible using PicoProbe and SWD, but taking it slow and showing each step of the process and some examples for how the debugging capability of PicoProbe and openocd can be used by beginner level programmers hoping to move into a more professional environment would be great.
Having problems. I've used Zadig enough to know the UF2 has to be flashed first, but under "Show All Devices" there is no Interface 2, only Interface 0 and 1. Windows assigns CDC-ACM UART to Interface 1 and it shows up as a COM port. Windows assigns CMSIS-DAP v2 to Interface 0 and when I run OpenOCD (your prebuilt version) it cannot find a Picoprobe. I've tried using Zadig to replace the driver with libusb but the same result occurs. The UF2 file was downloaded today from the R-Pi Pico site. Any suggestions appreciated!
I had to copy the picoprobe.uf2 to the pico before zadig would let me install the correct usb driver. That's not the order in the video. Just thought I'd point it out in case anyone has the same problem. Thanks for the videos. A guide to pico debugging would be really helpful.
As of the end of 2023, make the jump to Platform IO and the pico debug probe, and it's pretty much a one click solution. You don't have to set any of this up manually.
Thanks for the tutorial! One issue, when I use breakpoints in the C source file, the code stops at the assembly code and not the C code, any idea how to fix this?
Nice video to demonstrate a blinking Led, Ok, thanks, is the second Pico support multidrop SWD ? If yes, It should be cool to see how to debug with 2 cores ?
I am receiving this error can someone help? Open On-Chip Debugger 0.10.0+dev-geb22ace-dirty I pasted the debug on pico uf2, then installed the lib usb driver. Ran the command for open ocd and I received the error above.
Picoprobe sounds a lot like the Black Magic Probe that I use on STM32. I wonder if I can use my Black Magic Probe on the Pico.... it's a bit easier because it has GDB built in and doesn't need OpenOCD or any of that.
Love this video! However, with the "arm-none-eabi-gdb hello_serial.elf" directions, I get "Reading symbols from hello_serial.elf..." but then "(No debugging symbols found in hello_serial.elf)"... Not sure how this happened? ... Do I need to recompile the examples in some way to have the "debugging symbols" with all the examples? ... Thank you in advance! ... I have a second question, namely, IS THERE a VIS STUDIO CODE youTUBE vid showing this same thing on a Rasp Pi 4 running VIS STUDIO CODE?... Would love to see it!
Does the new Pi Pico Debug probe program the same way (hold the button, plug in usb, and copying the picoprobe uf2 file to it)? Regarding the VS Code extensions (Cortex-Debug, CMake Tools, Cpp tools), in order to debug non-Pi devices (ex. stm32), would you just need to change the launch json file to point to the target's svd and cfg files? I understand openocd uses the universal arm protocol 'CMSIS-DAP', but is it necessary to modify or rebuild openocd/msys2 tool whenever you debug a different Arm device (cortex m0m3m7)? BTW, George Hotz has a great 2016 video where he shows a different way to debug.. he made a qemu-based tool (qira) that allows for 'timeless' debugging!
The pico probe UF2 does not appear to exist. On the page linked the only thing about Pico probe is an ad to buy a cover. On page 60 of the getting started documentation it gives the same link and claims the UF2 appears under "utilities". There are no "utilities" on the page
Interesting, I can still see it on the following link www.raspberrypi.org/documentation/rp2040/getting-started/#board-specifications under the "About Raspberry Pi PIco" Tab
If only you could upload a zip file comprising of, OPENOCD, PICOTOOL and win32lib USB Driver, I shall get unstuck. But the software will have to work on 32bit windows 10 PC.
This is so stupid. All microcontrollers should be plug and play. Zero setup time. Straight to implementation. Looks like developers are masochistic enough, and enjoying the endless toolchain setup adventures, also to prove themselves important and useful.
couldnt agree more lol ive been trying to get the pico debug standalone tool working for hours. spent hours trying to set up pico to code in C, now this lol
An absolutely great and clear tutorial on OpenOCD and Pi Pico. Thank you for your effort and your additional information on your website. It saved me a lot of time and trying. Thank you very much. Please make a 2nd part of the tutorial - it is very interesting. Many greetings from Germany!
Great video and very helpful. I did however need to use commands from the updated "Getting started with Pico" document as the old command (as stated in the video) does not work any more src/openocd -f interface/cmsis-dap.cfg -c "adapter speed 5000" -f target/rp2040.cfg -s tcl instead of: src/openocd -f interface/picoprobe.cfg -f target/rp2040.cfg -s tcl Would love to see a part two tot his video!
It is simply not working for me. I have spent hours at it. What you show in this video does not necessarily follow, what I get in real life downloads, even, if I follow your instructions step by step. I have windows10 on a 32bit desktop PC. Do I need to get a new 64 bit PC with windows 10 ?. Your (zip file) picotool and openocd, did not work on my 32 bit windows 10. MinGW is not working on 32 bit windows 10 PC. The question is, if I have to get a new PC, should I no get a PI4, or, PI400 which can simplify, considerably, the set up for me to run VSCODE for debugging pico. Please advise. Perhaps it is time for some one to bring out a proper IDE like STM32 IDE with CUBEMX.
What I would love to see is a very through set of tutorials in C for the Pico. The examples are great in the sdk but would love additional ones including how to use a TFT display, etc.
Well spoken Mr. Thomas. I am sure MR. Shawn Hymel is up for the task. That is after he has helped me, and the other 99 followers, to get over sticky points. For now, I am stuck.
I followed your advice in this video to the letter. Running the hello_serial.elf worked just fine with the pico-probe and Putty displayed the output as in your video. I then continued and installed Cortex-Dubug etc, still all following your advice. But, when I attempted to debug with Cortex I get a warning dialog that reads: "Failed to launch OpenOCD GDB Server. Timeout." I have tried installing an older version of Cortex-Debug, but I still get the same warning dialog. What can you suggest please? BTW your videos are very good.
I got it to work. Disconnected the micro-usb cable from the pico-probe, re-connected and then launched VS Code. Attempted to debug via Cortex again and it worked. I have now installed Cortext-Debug v3.12 again.
Why does Zadig 2.5 (and Zadig 2.8) only show 3 devices and none of them are the Pico probe? Have you missed a step in this video? Is one of the Picos supposed to be connected?
Thanks for this video! Using this picoprobe as a pseudo "Jtag" interface is almost as painful as debugging a kernel driver on a Windows VM! I was able to replicate the processes which is the 1st for me with this project. However, I am using Visual Studio Code with PlatformIO and I need to edit the platformio.ini instead of the json cfg files as they are auto-generated from PlatformIO extension. Can you point me into how to modify the ini file to match the operations as defined in the cfg file?
Could you please confirm if this method can be used to prob any serial devices? I am not sure if you already had, please make a indepth tutorial for decoding the debug info. Surely checking you channel... Sorry if already done ...and yes a part 2...I don't know it matters or not after a year. Thanks for the video. Atleast a stepping stone for beginners.
I am reasonably experienced in embedded systems and can say that fighting tool chains is a massive waste of time. These videos are first class, well done!
I totally agree. "fighting tool chains" is pointless.
Some one should put the debugger in the second core and use interrupts to switch over.
That can't always be done, some use the second core for running code
@@danieljimenez1989 One needs to WALK before one can RUN.
I can not not even get the Debug to work.
@@danieljimenez1989 Ladyada talks about it. But then, talk is cheap.
some of the steps are presented out of sequence. The picoprobe UF2 file has to be installed on a Pico before zadig installer shows the driver
I got as far as PICOPROBE UF2 File. Then I am stuck. Can not get openocd to work on my 32bit windows 10 desktop.
A part two on this video would be great.
This is super helpful.
Thank you for a terrific video and yes, a part 2 would be very much appreciated.
Thank you for watching, glad you found it helpful! Will get on the part 2!
Yes please! Plus-n for the part-2. You deserve more subs than you've got. I'm new to C and wouldn't have chosen to go with it were it not for your tutorials. Thank you.
Thank you for this clear tutorial! A Part 2 would be helpful, especially for those of us who are trying to wean ourselves from the Arduino IDE, but are accustomed to being able to plug the Pico into USB and download the code to it. I think that is only possible using PicoProbe and SWD, but taking it slow and showing each step of the process and some examples for how the debugging capability of PicoProbe and openocd can be used by beginner level programmers hoping to move into a more professional environment would be great.
Having problems. I've used Zadig enough to know the UF2 has to be flashed first, but under "Show All Devices" there is no Interface 2, only Interface 0 and 1. Windows assigns CDC-ACM UART to Interface 1 and it shows up as a COM port. Windows assigns CMSIS-DAP v2 to Interface 0 and when I run OpenOCD (your prebuilt version) it cannot find a Picoprobe. I've tried using Zadig to replace the driver with libusb but the same result occurs. The UF2 file was downloaded today from the R-Pi Pico site. Any suggestions appreciated!
I have the same issue, did you figure it out in the meantime?
I wish every tutorial was as good as this one
I had to copy the picoprobe.uf2 to the pico before zadig would let me install the correct usb driver. That's not the order in the video. Just thought I'd point it out in case anyone has the same problem. Thanks for the videos. A guide to pico debugging would be really helpful.
Thanks Adam, save me a pile of frustration
Yes, please add the more in-depth debugging video. Cheers.
You are amazing. Thank you so much! Your video has made debugging rust much easier for me.
2:07 “… of the razpi pico, getting sKuhDAHted guide”
I have no idea what you’re trying to say but it sounds amazing
I would have saved so much time. If only I watched your video before the getting started documentation,...
Great video! I look forward to part 2.
Glad you found it useful, Part 2 coming soon!
Great explanation video. I assume your web docs are as clear as this! Thanks.
Glad it was helpful! Thank you
Much Awaited
Can you help me ? I am getting stuck.
Great video, thanks a lot. Thumbs up for part 2!
As of the end of 2023, make the jump to Platform IO and the pico debug probe, and it's pretty much a one click solution. You don't have to set any of this up manually.
This is incredibly helpful! Thank you!
You're welcome! Thank you for watching
What do you do if it failed to open OR find the device
Nice. Helped a bunch.
VSCode is complaining about "Identifier true is not defined" but yet the LED is blinking in debug mode...
...thanks
Thanks ! Waiting for a part 2 :)
Thanks for the tutorial! One issue, when I use breakpoints in the C source file, the code stops at the assembly code and not the C code, any idea how to fix this?
Nice video to demonstrate a blinking Led, Ok, thanks, is the second Pico support multidrop SWD ? If yes, It should be cool to see how to debug with 2 cores ?
Thanks a lot, if it took me a while to make it run because eff VS Code and its useless error messages. So frustrating.
Great tutorial!
Thank you!
I am receiving this error can someone help?
Open On-Chip Debugger 0.10.0+dev-geb22ace-dirty
I pasted the debug on pico uf2, then installed the lib usb driver. Ran the command for open ocd and I received the error above.
Very helpful video. I shall try this.
Picoprobe sounds a lot like the Black Magic Probe that I use on STM32.
I wonder if I can use my Black Magic Probe on the Pico.... it's a bit easier because it has GDB built in and doesn't need OpenOCD or any of that.
How do you make headers fit the debug pins?
How do you get the double breadboard pictured?
Can you please cover how to debug multi file project?
for C programming on windows, one day !
4:20 or as monitor for micropython serial output, might be interesting
Where did you get that double-width half-size breadboard?
Love this video! However, with the "arm-none-eabi-gdb hello_serial.elf" directions, I get "Reading symbols from hello_serial.elf..." but then "(No debugging symbols found in hello_serial.elf)"... Not sure how this happened? ... Do I need to recompile the examples in some way to have the "debugging symbols" with all the examples? ... Thank you in advance! ... I have a second question, namely, IS THERE a VIS STUDIO CODE youTUBE vid showing this same thing on a Rasp Pi 4 running VIS STUDIO CODE?... Would love to see it!
Is it possible to use picoprobe for another microcontrollers, such as Microchip Cortex-M4?
Does the new Pi Pico Debug probe program the same way (hold the button, plug in usb, and copying the picoprobe uf2 file to it)?
Regarding the VS Code extensions (Cortex-Debug, CMake Tools, Cpp tools),
in order to debug non-Pi devices (ex. stm32), would you just need to change the launch json file to point to the target's svd and cfg files? I understand openocd uses the universal arm protocol 'CMSIS-DAP', but is it necessary to modify or rebuild openocd/msys2 tool whenever you debug a different Arm device (cortex m0m3m7)?
BTW, George Hotz has a great 2016 video where he shows a different way to debug.. he made a qemu-based tool (qira) that allows for 'timeless' debugging!
This would be tedious/painful to figure all out on one own - thank you.
Glad I could help!
Excellent video
if i want to program another mcu, like atmega, stm32 or sam21, will it work?
Great Video. Thank you.
The pico probe UF2 does not appear to exist.
On the page linked the only thing about Pico probe is an ad to buy a cover.
On page 60 of the getting started documentation it gives the same link and claims the UF2 appears under "utilities". There are no "utilities" on the page
Interesting, I can still see it on the following link www.raspberrypi.org/documentation/rp2040/getting-started/#board-specifications under the "About Raspberry Pi PIco" Tab
Found it. Thanks for the quick response
If only you could upload a zip file comprising of, OPENOCD, PICOTOOL and win32lib USB Driver, I shall get unstuck. But the software will have to work on 32bit windows 10 PC.
From where did you get your Knowledge?
Oh no! I was so pumped until i saw you’re coding in C :’(
This is so stupid. All microcontrollers should be plug and play. Zero setup time. Straight to implementation. Looks like developers are masochistic enough, and enjoying the endless toolchain setup adventures, also to prove themselves important and useful.
couldnt agree more lol ive been trying to get the pico debug standalone tool working for hours. spent hours trying to set up pico to code in C, now this lol
Peeco?
Yes please ... part two would be really useful.
Planning it now! :)
An absolutely great and clear tutorial on OpenOCD and Pi Pico. Thank you for your effort and your additional information on your website. It saved me a lot of time and trying. Thank you very much. Please make a 2nd part of the tutorial - it is very interesting. Many greetings from Germany!
Glad you found it helpful! Thank you for watching and I will get part 2 out soon!
Great video and very helpful. I did however need to use commands from the updated "Getting started with Pico" document as the old command (as stated in the video) does not work any more
src/openocd -f interface/cmsis-dap.cfg -c "adapter speed 5000" -f target/rp2040.cfg -s tcl
instead of:
src/openocd -f interface/picoprobe.cfg -f target/rp2040.cfg -s tcl
Would love to see a part two tot his video!
Thank you for letting me know the command changes. I will look into updating the video & going into more detail debugging. Thanks!
It is simply not working for me. I have spent hours at it. What you show in this video does not necessarily follow, what I get in real life downloads, even, if I follow your instructions step by step. I have windows10 on a 32bit desktop PC. Do I need to get a new 64 bit PC with windows 10 ?.
Your (zip file) picotool and openocd, did not work on my 32 bit windows 10.
MinGW is not working on 32 bit windows 10 PC.
The question is, if I have to get a new PC, should I no get a PI4, or, PI400 which can simplify, considerably, the set up for me to run VSCODE for debugging pico.
Please advise.
Perhaps it is time for some one to bring out a proper IDE like STM32 IDE with CUBEMX.
64 bit binaries will not work on a 32 bit computer... You can buy a raspberry pi or a new PC, that's up to you :)
What I would love to see is a very through set of tutorials in C for the Pico. The examples are great in the sdk but would love additional ones including how to use a TFT display, etc.
The benefit of using a PICO is to get the applications, up and running quickly.
Well spoken Mr. Thomas. I am sure MR. Shawn Hymel is up for the task. That is after he has helped me, and the other 99 followers, to get over sticky points. For now, I am stuck.
@@gautombose4172 What are you stuck on?
This is brilliant, thank you very much!
Glad it was helpful!
I realize I am quite randomly asking but does anyone know of a good place to watch newly released tv shows online?
@Samson Beckett Try FlixZone. Just search on google for it =)
@Richard Caspian Yup, I've been watching on FlixZone for since april myself :D
@Richard Caspian thank you, I signed up and it seems to work :) I really appreciate it !!
I followed your advice in this video to the letter. Running the hello_serial.elf worked just fine with the pico-probe and Putty displayed the output as in your video.
I then continued and installed Cortex-Dubug etc, still all following your advice. But, when I attempted to debug with Cortex I get a warning dialog that reads:
"Failed to launch OpenOCD GDB Server. Timeout."
I have tried installing an older version of Cortex-Debug, but I still get the same warning dialog. What can you suggest please?
BTW your videos are very good.
I got it to work. Disconnected the micro-usb cable from the pico-probe, re-connected and then launched VS Code. Attempted to debug via Cortex again and it worked. I have now installed Cortext-Debug v3.12 again.
Can you help me. I am getting stuck.
Why does Zadig 2.5 (and Zadig 2.8) only show 3 devices and none of them are the Pico probe? Have you missed a step in this video? Is one of the Picos supposed to be connected?
Can this same setup be used on Raspberry Pi Zero 2 W?
Great video! love to see a part2
I need this one pi pico running strange and not loading at all .
Marvelous
Thanks for this video! Using this picoprobe as a pseudo "Jtag" interface is almost as painful as debugging a kernel driver on a Windows VM! I was able to replicate the processes which is the 1st for me with this project. However, I am using Visual Studio Code with PlatformIO and I need to edit the platformio.ini instead of the json cfg files as they are auto-generated from PlatformIO extension. Can you point me into how to modify the ini file to match the operations as defined in the cfg file?
Helpful Video.
Your breadboard looks different from what is commonly available. Please can you please share the make/brand/or store link to get it.
Man, this is amazing. Thank you for sharing the knowledge and resources.
Is this still the current best way to set up the tool chain?
Thanks for making this!
Could you please confirm if this method can be used to prob any serial devices?
I am not sure if you already had, please make a indepth tutorial for decoding the debug info. Surely checking you channel... Sorry if already done ...and yes a part 2...I don't know it matters or not after a year. Thanks for the video. Atleast a stepping stone for beginners.
And +1♥️