This Is 100% How You Should Be Debugging | How to Use OpenOCD to Debug Embedded Software with GDB 

Thanks so much, you would not believe how few, straight forward explanations of how to do this there are out there.

This is great, I’ve always wanted to get into embedded systems programming and it seems as your channel is where I’ll start 😁🙏🏽

I think I learned more in the last 7 and a half minute than I had expected. Wow! Well done!

When you talk about debuggers please don't forget The Black Magic probe.... so cheap, so easy, so cheap! I debug my Blue Pill with... well.... another Blue Pill!!!

Really informative video. Thanks a lot. For me personally you hit the nail on the head with this video. It was exactly what I was looking for.

Thank you so much, it is really hard to find simple, relevant information regarding debugging on embedded

Thank you so much! It's really hard to find working up-to-date examples like this. So many old examples don't work anymore. I was able to get SWO working. And I also got debugging of the nRF using the st-link working.

I wasn't aware you could toggle the display format while inside gdb... I normally just run with --tui when I start. Will have to give that a go next time!

Perfect! I've done something similar with two rpi picos. Now I know also what openOCD actually does! Thanks.

great video! never debugged a microcontroller, but it doesn't seems too difficult.

Wow, this is really cool! I didn't know gdb could do that

Great tutorial, thank you.

that's why I love my little Arduino Zero, since it has an EDBG included. (I also have a jlink for my other boards)

Thank you sooo much for this tutorial!

Almost every embedded system I have worked with, one of the engineers has dedicated a UART for a serial debugging console.

awesome tutorial, thanks!

Another fantastic video, thanks.

You are great man. That's all.

Jesus Christ, I've wasted a week being stuck with debugging because I forgot to add the "target extended-remote" step to my damn notes! Thanks for the video though, the instructions hold up for other boards too.

FYI, in Fedora, the st-link package is stlink, not st-link. Also, there is no gdb-multiarch on Fedora. Use regular gdb but set arch once you start it. Great video.

I think it might be easier to just code correct the first time 😁🤓😂 ..just kidding, really nice, did not know this could be done command line like this! Good content! 💪👌👍🤓

Oscilloscope helps with debugging very much. Sometimes I can make all the job using only one or two pins to out either logical states through them or use them as a clock/data pair to see bytes on the oscilloscope directly.

Hold up could I use one of these little chips instead of a PLC for some basic robotics? Like I would have to use different relays but that may be worth the sacrifice if I don’t have to use ladder programming

Hello, LLL, may i humbly request a dive into GD32VF103 MCU. It's a 32-bit RISC-V chip. It is rather basic at the moment, but something tells me that as time goes on this architecture will become more and more mainstream. And a lot of folks would like to watch series on RISC-V assembly as well as corresponding GCC stack. Cheers.

My only experience with embedded is from messing around with Arduino using PlatformIO in vscode. Is this better than PIO? Or maybe they can compliment each other?

ty

Not to be that guy but is there a GUI for it? I’ve used the STM32CubeIDE and it has a debug mode that has all the functionality of this and probably more, like having a live view of global variables as the program runs and being able to see the disassembly, and it seems it would be easier just to scroll through your code whilst it running and just click to create a breakpoint wherever you want it, the interface in the IDE seems a lot easier to use with more functionality than this, so is there a non STM GUI version of this for other chips?

You are love my dear. I want to give you a hug!!

Thank you. Atleast I could see the ST-link V2 leds blink after so long. After target extended-remote localhost:3333 command, OpenOCD gives an error: "undefined debug reason 7 - target needs reset" and GDB gives: "0x00000000 in ?? ()" What does these two error mean and how to resolve it ?

Do you have any course/video playlist/certificate where i can learn to program stm32 based systems using this method?

I have 250pcs STM32 bluepill witch is same variant with this video (black jumper and wrong device ID). and having issue USB not recognized. Need help....

Just spent 2 days banging my head against the desk trying to get I2C working on the blue-pill using the libopencm3 library. By the way, you have to gpio_set(I2CPORT, SDA|SCL) to get it to work (at least in master-mode). Question: I found some 'optimized out' variables while debugging INSIDE libopencm3 code. I don't know if the debugger symbols were optimized out or if the variables were, any thoughts? I changed the -O level in the library's makefile, and re-compiled. Thanks so much for these videos, man. I tried cubeIDE and hated it; register level programming is fun and all, but I want to actually get stuff done. You introduced me to this library that fits my style.

I brought this in for show and tell at work... They adopted it for a piece of legacy firmware.

whats the different to hit debug in eclipse ide with openocd or stlink, jlink Interface?

Why would I do this instead of just using SWD's SWO pin via STM32Cube IDE?

What's the difference between PyOCD and OpenOCD? I haven't used them directly, but I have used software that relies on PyOCD

Is there a command-line-parameter to scan the JTAG chain for devices? Any thoughts on using a GUI for debugging.. VSCode , Eclipse, or VisualGDB? For example VisualGDB supports OpenOCD, yet it doesn't support popular debuggers that use OpenOCD, like the Black Magic Pro. (Perhaps the BMP debugger is a little different as it doesn't seem to require any server software running on your computer (OpenOCD /STLink/urjtag/etc).. Instead, I think the Black Pill just appears as a remote (serial) GDB debugger.. with all the JTAG/SWD-TRACESWO support handled on the BMP itself?) Speaking of debuggers, I'm a little confused as to the difference between JTAG and SWO/SWD, and "ETM Traces". Segger has tons of different J-Link/J-Trace models.. and there's also plenty of cheap clones (EDU Mini, RealView U-Link2, etc). I have an AT ATMEL-ICE debugger, which supports CMSIS-DAP/SW/JTAG but no SWO. Perhaps this explains why ITM_SendChar doesn't work when I tried it with Keil (limited version 32KB). Does OpenOCD support the advanced streaming/tracing capability?

Maybe you could make a video on why unix/linux developers give their products just goofy names.

This is a good demonstration for a basic understanding of the embedded system debug process. BUT IMHO it's a fucking nightmare to debug an actual project like that. Any ide GUI is much more convinient. And for the remote target, it's easier to log in to the PC with a debugger by RDP and use GUI.

I could only find the jlink for like 500 Euros. Are they really that expensive?

First time heard thoughts it was about someone is keep washing his hand

I can't seem to run OpenOCD, why is it so hard to use this?

where do I get the configuration file for my controller : stm32f401ccu6

Really, really good video! Thanks!

Hello,just found ur channel,i want to ask if arduino is a good entry to low level programming

The package st-link doesn't seem to exist on Ubuntu 24.04. Any suggestions?

I take it it's possible to do this with rust code as well?

Do you have an stm32 openocd tutorial on the raspberry pi? f4 preferably

When you say "bare metal" is that AtmelStudio or are you digging into the .h files to use lowest command possible. I just saw AtmelStudio is 1 GB in size (ugh) and Arduino is in Linux's Synaptic Package Manager and only 20 MB (yeay). Thank you.

Nah just print everything to serial console and hope for the best. Why is all this stuff so damn complicated? I couldn't even understand what all of these do before watching this.

First!!