3 ms·

>I'd say a lot of UARTs are running debug consoles You are already assuming RTOS/Linux with this. UART is easy to initialise on about all platforms. On an AVR

>I'd say a lot of UARTs are running debug consoles You are already assuming RTOS/Linux with this. UART is easy to initialise on about all platforms. On an AVR you you don't even have to think about configs or clock trees. UART is one of the best ways to debug and vastly superior to just blinking a led.

monocasa 6y ago
> You are already assuming RTOS/Linux with this. > UART is easy to initialise on about all platforms. On an AVR you you don't even have to think about configs or clock trees. I'm assuming fairly standard microcontrollers, but yes, from my experience as a lead for a proprietary RTOS that I ported to dozens of boards. I'd say that AVR is the outlier here. Nearly every more complicated core has clock configuration that's finicky and needs to happen to bring the UART up. Blinking an LED just needs a couple writes to PINCONFIG and GPIO blocks and a busy wait loop that isn't optimized out. > UART is one of the best ways to debug and vastly superior to just blinking a led. It is once you've validated that code execution is actually occurring.
IndrekR 6y ago
> UART is one of the best ways to debug and vastly superior to just blinking a led. A proper debugger, and if the platform allows, a tracer are the best ways to debug/profile code on an MCU.