Community spotlight: MyEmbeddedStuff
One of the things we love most about the Arduino community is the way knowledge flows freely – makers, engineers, and hobbyists sharing what they’ve learned so others can build on it. Case in point, the in-depth technical analyses coming from MyEmbeddedStuff, a blog dedicated to embedded systems written by an engineer with over seven years of professional experience and a genuine passion for understanding how things work at a low level.
Since the launch of the Arduino UNO Q in October, MyEmbeddedStuff has started publishing detailed posts exploring the board’s architecture, communication protocols, and real-world performance. We reached out to learn more about the person behind the blog and what drew them to explore the Arduino® UNO™ Q so thoroughly. Their story will resonate with many in the Arduino community: curiosity, persistence, and a belief that sharing knowledge makes everyone stronger.
From blink to… a career in tech
Like many embedded engineers, the author of MyEmbeddedStuff started young. “From a very young age, I’ve always been passionate about computers and technology,” they explain. “At one point I even considered studying something more focused on computer science, but I felt I was missing interaction with the real world. That’s when I started leaning more towards electronics, and especially robotics: seeing how small systems could actually do things was the real turning point for me.”
That curiosity led to the classic electronics “hello world” – blinking an LED – and from there, a deep dive into microcontrollers, programming, and everything that makes embedded systems tick. After completing both a Bachelor’s and Master’s degree in Electronic Systems, they’ve spent their career working on everything from ultra-low-power IoT devices to complex multicore systems running embedded Linux.
And Arduino? “Arduino was also a key learning tool for me when I was starting out,” they say. It’s a refrain we hear often, and it never gets old – Arduino as the gateway that makes embedded systems accessible to anyone curious enough to try.
Why UNO Q?
Over the past few years, MyEmbeddedStuff has noticed a clear trend in professional embedded development: increasingly complex systems combining real-time microcontrollers with Linux-based processors. That’s exactly why the UNO Q immediately stood out.
“The release of the UNO Q immediately caught my attention, as it brings together both worlds: a Linux-based system on one side, and an STM32 handling time-critical tasks on the other,” they explain. “I believe that a board like the UNO Q, at a relatively accessible cost, can be a very powerful learning platform for people who are getting into embedded systems today.”
But beyond its educational potential, the UNO Q addressed a practical problem they’ve encountered professionally: communication between microcontrollers or between microcontrollers and host systems. “In several of my professional projects, communication between microcontrollers or between microcontrollers and a host system has been one of the most complex and time-consuming parts. That’s precisely why the approach taken by the UNO Q caught my interest.”
Beyond the documentation
What sets MyEmbeddedStuff’s analysis apart is the depth of investigation. While the UNO Q code is available on GitHub and the README files provide solid documentation, that wasn’t enough. “I’m quite curious by nature and like to understand things at a low level,” they note. “Reading the documentation wasn’t enough for me: I wanted to observe it with a logic analyzer, measure real timings between messages, and understand exactly how the frames exchanged between the MPU and the MCU were structured.”
This kind of rigorous, hands-on exploration resulted in detailed blog posts that have become valuable resources for the community. Their deep dive into the RPC communication protocol breaks down exactly how the microcontroller and processor talk to each other, complete with timing diagrams and real measurements.
Their analysis of boot time addresses misinformation circulating online with objective data: “Some people mentioned 20 seconds, others 40, and so on. After measuring it objectively, the actual boot time is around 40 seconds from power-on to the execution of a preloaded sketch. […] Many people see [the boot time] as a negative point, but in reality it’s completely normal for any SBC. There’s a lot happening under the hood: system boot, kernel initialization, services starting up, etc. The issue isn’t the boot time itself, but rather comparing it to boards based solely on microcontrollers, where startup is almost instantaneous. They belong to different categories.”
This kind of clear, technically grounded analysis can help understand the true purpose of UNO Q: “From my point of view, the UNO Q doesn’t replace traditional Arduino boards: it fills a different space. It’s well suited for projects that need the flexibility and power of a Linux system combined with real-time control and low latency, without consuming resources on the main processor. In that context, the architecture makes a lot of sense.”
Why sharing matters
We asked MyEmbeddedStuff why they started their blog in the first place: “I’m not a big fan of the current trend in embedded systems development,” they said. “It seems to me that, with the rise of artificial intelligence, there’s no longer as much research or sharing in forums, nor are different techniques discussed as frequently as before. I think many people might enjoy a blog-like format again, a space where ideas can be developed at their own pace.”Interested in finding out more? Check out MyEmbeddedStuff’s blog to learn from someone who approaches embedded systems with curiosity and a genuine desire to share what they’ve learned in a clear, accessible way.