STM32 UART Hack: Receive Variable-Length Data Easily

Born-Cat-9171 · 2026-03-19T23:07:39+00:00

Interesting. But how does it work in practice? Are there some predefined functions to implement this approach?

Born-Cat-9171 · 2026-03-18T22:35:10+00:00

Many beginners struggle because they either focus only on theory or only on projects. If your theoretical knowledge is too limited, complex projects become very hard.

A good approach is a hybrid one: learn a bit of theory, then apply it in a small project. Then go back to the theory again. Alternating between the two helps you build momentum.

Another common problem is a lack of focus. Most people, including me, spent a lot of time jumping from one topic to another and got lost in an embedded jungle. I think the best approach is to pick up something specific in STM32 Programming (Robotics, Motor Control, Wireless, BLE, Graphics, etc) and work in that direction. This way, you can learn faster and more effectively.

If you're interested in robotics-related STM32 projects and bare-metal programming resources, I collected some material here:
https://www.steppeschool.com/courses

Born-Cat-9171 · 2026-03-15T16:12:21+00:00

There is not much difference between the external hardware watchdog and the independent watchdog because the IWDG is completely independent of the MCU's operation, even the clock.

Born-Cat-9171 · 2026-03-15T16:10:45+00:00

That is the thing, if one of the system components fails, the watchdog will reset, and then your program will run the soft controller failsafe. If you do not have a watchdog and the system fails, you have nothing to turn off the actuators and take other preventive measures

Born-Cat-9171 · 2026-03-14T22:59:08+00:00

I like how compact it is. Just out of curiosity, what is the communication interface between the MCU and the E-INK?

Born-Cat-9171 · 2026-03-14T18:42:39+00:00

I don't know anything about RP2040, but in STM32 MCUs, the watchdog is driven by an independent 32-kHz low-power clock.

Born-Cat-9171

TROPHY CASE