Bare metal embedded lecture-6: Downloading and debugging executable 

If you are familiar with with BlueTooth, Please give a lecture about it as to how a microcontroller can process realtime sound data and send through bluetooth.

I am not able to find any board config file for stm32f446re board. Can I not do debugging using using openOCD??

Thank you for sharing such a great content. Note: 1:30 AFAIK you don't need the ST-LINK adapter, since the discovery boards come with an embedded ST-LINK/V2.

I am using a Linux operating system. I used the command "openocd -f /usr/share/openocd/scripts/board/st_nucleo_f4.cfg -f /usr/share/openocd/scripts/interface/stlink.cfg" to load my microcontroller

Anyone using bluepill board can use openocd.exe -f \interface\stlink.cfg -f target\stm32f1x.cfg

Another Great Video. You explain everything in a very easy way. One question, I have Stm32f103 blue pill board(it doesn't have on board stlink circuit) and I dont have stlink debugger, is there any way I can program blue pill board through on board Usb or the Usb to serial adapter using OpenOCD?

Hi, thanks for this video. I have a question about OpenOCD becasue I want to understand this correctly. From my perspective OpenOCD is kind of a bridge from software perspective to connect PC/Laptop with a board with hardware bridge (st link)?, Do I unnderstand this ok?, please correct me :)

Confused: There is no remote programming/debugging done in this example then why client/server model is used?

great videos {1 through 7} and lot of insights specific to linker file and script ... I could reproduce the demo on my STM32F407G-DISC1 board ... One point to be noted though , OpenOCD needs ST-Link interface {stlink-v2-1.cfg} *not* {stlink-v2.cfg}. So one may update the board cfg file appropriately and then use the updated board cfg file with the linker command .

This is pure gold . Can you please do a series on arm v8 architecture. Thanks

What is telnet why we are using it

You're awesome, I finally got my code working. One problem I had that wasn't covered in the video was needing to download STlink drivers, before that i was getting a USB error in openOCD.

Good work. A few doubts. First why open ocd requires board specific details as the architecture and debug interfaces are common in many microcontrollers? Second. I think we can use the gdb itself to put break points and watch points if we provide the elf file as input before opening gdb. This is more easier as we don’t require to analyse the function address to put the break point. We can use function name as is.

thankyou very much for making this free on youtube

You are a good teacher, it was very useful. Keep it up.

I liked the video first then started watch.. confident of liking it even before watching.

Thanks for such awesome content

Very well explained

Great Explanation sir!

Awesome 👍 sir

OpenOCD only supports USB2.0. I only have USB3.0 ports on my computer. Is there any bypass to this?