@____________________________.x

When guests cover every little detail itโ€™s really useful, everyone else just assumes that we already know the 42 mouse clicks they did to get from A to B

@Sid-po5yt

We need a second part for this! Hands down one of the best beginner tutorials out there. Thank you for the effort Robert!

@GreidiAjalik

What a great video! It was pleasure to collaborate with you and thank you so much for having me on your channel!

@stevenbroshar7948

I applaud the questions from Robert. You asked several questions that I was wondering about. The presenter knows this stuff so well that he doesn't know what a novice doesn't know.

@nomadic_rider42

An Interrup can to two things: cause software to execute via an interrupt handler (if the interrupt is enabled) and cause some peripheral to do something (like triggering a timer). An Event doesn't cause the interrupt handler to run, but can cause some peripheral to do something.

@rahuls7039

Robert is like that intelligent kid who knows it all and is just helping the teacher convey every piece of information to all the kids... This is an excellent video for explaining every step...

Thank You @Robert Feranec and @Greidi Ajalik for this beautiful video. ๐Ÿ˜‡

@benhorton1943

As someone starting with STM32 and microcontrollers in general, this was invaluable... makes it feel way less impossible to learn

@nikosant03

What a great tutorial for beginners!!! Thank again for your effort and your time!! Please upload more STM32 firmware-based tutorials explring maybe more peripherals or low-power design techniques (I liked the point mentioning the value of suspend and resume tick) :)

@ediahmadfauziserbhaneka9946

Dude, this is the only video that works. Thanks for posting!

@vrjb100

Compilers will optimize code generated and remove dead code from include files etc. So it's correct to include the string.h file. Only the call to strlen will be included, because that one is really called. Include files define prototype of functions, so the compiler can do type checking and thus detect programming errors at compile time.

@mostafaabdelaziz2316

This is one of the best tutorials I have ever seen, it is really simple and easy for beginners to understand it.

@bahjatmurrad8008

Honestly one of the best videos i've seen on STM32

@elecrain

Perfect content for learning the stm32. Thanks for the detailed explanations, we are waiting for second part !!

@marc_montalvez

I think this is the best tutorial that I have seen in my life

@faisaltariq_artist

Thank you very much.  This was extremely helpful and detailed.   Any beginner with STM32 can get up and running in no time with this tutorial.

@arneweber7875

Thanx a lot, the tip at 40:42 to update ST-Link solved my Problem

@kbgaminghd7504

The amount of respect i have for this guy

@daft4682

This is one of the best tutorials ever. Thank you so much for putting this together. Excellent starting point.

@kaihorstmann2783

You can use the built-in ST-Link for custom boards. The debug pins are available on header pins on the ST-Link of the Nucleo board. Here you need to disconnect the Nucleo MCU from the debugger.
The purpose for the cuts in the Nucleo PCB is actually breaking or cutting off the ST-Link part from the Nucleo, and keep using the ST-Link as stand-alone device.

@desaoaraujo

Just a small correction, you can program another MCU using the ST-Link that's integrated in the Nucleo board, you just need to remove a couple of jumper shunts and you can connect your board via the SWD header.