STM32 + SWD + ST-Link + CubeIDE | Debugging on Custom Hardware Tutorial - Phil's Lab #4

Guide on how to connect, check, program, and debug your custom STM32-based hardware via SWD and the ST-Link debugger utilising STM32CubeIDE.

If you have any questions or suggestions for future videos, please let me know in the comments!

[Timestamps]
00:00 Introduction
00:28 ST-Link
01:08 Hardware Connections

02:11 ST-Link Utility (Checking that we can connect to STM32 MCU)
03:37 STM32CubeIDE (Programming and debugging software package)

05:22 Enabling SWD
06:04 Setting up an external high-speed crystal (HSE)
07:10 Additional peripheral selection

08:50 LED blinking test code
09:44 Building code and checking for compiler errors
10:02 Debug configuration, debugging, and flashing via ST-Link
11:26 Running, pausing, and setting breakpoints

12:20 Hardware running code

[Hardware]

[Software]

ID: QIBvbJtYjWuHiTG0uCoK

[slazy]

You really are an inspiration bro! Found you through your KiCad course, your videos really help me alot. I want to dive deeper into STM32 boards. Wish you the best for 2023

[disposedtrolley]

Thanks Phil! I'm just getting into STM32 and custom board design and your videos have been really helpful.

[satchell]

The Eclipse IDE has come a long way. Thanks Phil, awesome stuff!

[devised]

Thanks Phil! I didn’t realize I needed swo pin to print. Saved me a lot of struggle!

[deeperblues]

Spot on information for a newbie to the STM32 tools. Many thanks Phil!

[jackiewang]

Thanks a lot! 5:42 is very important. I originally thought my debugger is broken.

[adaminsanoff]

I enjoy watching your videos after a long working day.

[jonathanfulcher]

This is exactly what I needed. Thanks!

[lucianopavarotti]

Great video, clear explanation with simple software and hardware example! Thank you for sharing the knowledge!

[johnadriani]

Realy cool.. realy clearly good voice .. is not to fast yor trutoreal everything is good to understand.. you are a very good teacher

[kenwallace]

Yes indeed, very clear and useful. The debugger is complex with a steep learning curve. This helps.

[edwinvp]

Thank you for this very nice video! Your video provided the hints I was looking for. I've got a working "hello blinky LED" program now.
One note in case of my board, I had to press the RESET button on the board before ST link application would recognize the target.

[younesthabet]

@5:45 why you choose Serial Wire instead of JTAG4/5 !? and what is the difference between them!?

[nickbolton]

1:31: This caused me a couple of hours frustration; that you can't power MCUs from pin 1 on a [real] ST-LINK/V2. The part where you said "It's just a reference voltage" was something I wish had been made clearer in the docs. I then realised I had to use pin 19 (non-ISOL device only) to power my board at 3.3 V. The confusing part is that pin 1 needs to also be connected, as well as pin 19.

[Rtech]

Quick question, do you need that device in order to program an STM32? I'm using an STM32 along with a Bluetooth module to make my Bluetooth headphones, but I was planning on using UART and not SWD.

[Electromechaniac]

Hello! Could You describe the model/producer (maybe part number) of white connectors? Thanks a lot!

[ronaldogrande]

very clear explanation like ever.
I just dont understand why you have to set 168mhz. But sounds like is something to have in mind

[theoneandonlymattp]

Hi Phil, is it possible to connect to a board using the STM32 debugger and pull the software off or atleast see the software on the chip? as i have been sent a board by a customer who has had an issue with there and it's suspected the chip has lost its data but is unsure.

[saadtiwana]

You make some of the best videos!
You have yourself another subscriber!

[hUgO]

Can you help me out with something? When I use ST-Link I can connect to my board however when I try to debug with STM32CubeIDE I get an error ST-Link not found.