Matt Dickerson

*** Silent Killer in High-Speed Interface Design *** Every engineer working on PCIe, USB, CSI, DSI, LPDDR, SerDes, or any high-speed interface knows: "Timing closure will keep you Up at night." But here’s the thing—It is not always the big violations that kill a design. These can be found and fixed. The silent killers are the marginal cases: * That one Async Clock Domain Crossing that looked fine… until Silicon. * That Power mode Transition that only happens under rare Conditions. * That Corner case in Equalization that only fails in a specific voltage/temp combo. "These don’t show up in the standard verification flow. You have to hunt them down." What’s your approach to catching these hidden pitfalls?

164

5 Comments

📺 Ever wondered where PWM or PDM is actually used in real life? Most of us remember learning about modulation techniques like PWM (Pulse Width Modulation) or PDM (Pulse Density Modulation) in our embedded systems classes... ...and then we forgot them. Not because they’re useless, but because no one told us where they really shine. 🎯 One underrated yet daily use-case? Your TV or AC Remote. Yes, seriously. Every time you press a button to change the channel or switch off the AC, you're unknowingly triggering a PWM-based communication. 🔍 So How It Works: Infrared (IR) remotes use modulation techniques like PWM or PDM to encode data into light pulses. ➡️ Each key on your remote corresponds to a unique code ➡️That code is sent using bursts of IR light, modulated with PWM ➡️The receiver decodes the duration and gaps between pulses to figure out the command This is how your TV knows you pressed volume up, not power off. ⚙️ Why PWM? Resistant to noise Easy to implement in hardware Efficient for short-range line-of-sight communication 🤯 You thought PWM was only for motor control? Turns out — it’s literally in your hand, every time you use your remote. 💬 So next time you press a button on your remote… Remember: you’re not just flipping channels. You’re engaging a classic embedded system concept — in action! #EmbeddedSystems #microcontroller #programming #C #Cprogramming #SignalProcessing #TechFacts #Electronics

116

2 Comments

*** Why Silicons (Chips) Fail in System Bring-Up? *** Imagine silicon comes back from the fab. Everyone’s excited. Power it up, Run the first tests… and Critical basic function don’t work. This moment separates experienced teams from the rest. Because at this stage, it’s never just a Design issue—it’s an Interaction issue: o Analog, Digital, Verification, Firmware, and Test Teams, all meeting for the first time in real hardware. o Validation engineers uncovering behaviors no simulation ever caught. o Debugging across five different domains at once. You can’t simulate everything. But you can "prepare." The best teams don’t just verify IPs—they build a "Bring-up Mindset" into the entire development process. What’s the trickiest bring-up issue you’ve ever faced?

264

12 Comments

For Embedded Engineers considering a move in 2026, a few honest observations from the market. The strongest engineers I speak to are not the ones who know every RTOS or MCU family. They are the ones who can explain why a system was architected a certain way, how they handled failure modes, and what tradeoffs they made under real constraints. What is coming up repeatedly in interviews right now Ownership of firmware architecture, not just feature delivery Clear experience with real hardware bring up and debugging Comfort working cross functionally with EE and Mechanical teams The ability to talk through decisions, not just list tools On the flip side, the best companies are Having engineers interview engineers Keeping technical panels practical, not academic Being clear on impact, scope, and expectations early If you are evaluating opportunities this year, focus less on job titles and more on ownership, decision making, and the problems you will actually be trusted to solve. In the end, the engineers who stand out are the ones trusted with decisions, not just code. #beUneek #EmbeddedEngineers #Embedded

323

6 Comments

Every time I mention Zephyr, I inevitably hear “just use FreeRTOS.” To be clear, FreeRTOS is an excellent tool, but that advice often skips an important step: understanding the kind of project you’re actually building. In my latest post, I break down how FreeRTOS and Zephyr differ not just in features, but in philosophy. FreeRTOS excels as a lightweight, flexible kernel that’s easy to drop into constrained or purpose-built systems, while Zephyr takes a more opinionated, platform-oriented approach that prioritizes structure, portability, and long-term maintainability. The key takeaway isn’t that one RTOS is better than the other; it’s that they’re different tools for different purposes. Zephyr’s additional overhead can be a worthwhile tradeoff for complex or evolving products, while FreeRTOS often shines when you want maximum control and minimal abstraction. If you’re choosing an RTOS based on habit or hype, it’s worth stepping back and asking what your system actually needs. I’d love to hear from others who’ve used FreeRTOS, Zephyr, or both: what kinds of projects have you found each one best suited for? The full post can be found here: https://lnkd.in/gAM_fz_A #embedded #RTOS #programming #microcontroller #FreeRTOS #Zephyr The Zephyr Project

388

28 Comments

🚗 No Room for Error: How OCXOs Guide Autonomous Vehicles When a vehicle drives itself, timing isn’t just critical—it’s everything. Behind every safe lane change, smooth stop, and real-time decision lies an unsung hero: the Oven-Controlled Crystal Oscillator (OCXO). Here’s how OCXOs enable autonomy: 📍 Precise Sensor Sync – Coordinates LiDAR, cameras & radar with microsecond accuracy 🌡️ Temperature Resilient – Stable performance from freezing mornings to hot asphalt 📡 GNSS Reliability – Enhances GPS accuracy for exact positioning 📊 Clean Signal Integrity – Low phase noise ensures trustworthy navigation data Where OCXOs Drive Impact: • Sensor fusion for 360° awareness • Real-time path planning & obstacle avoidance • Vehicle-to-everything (V2X) communication At Dynamic Engineers, we engineer the timing solutions that help autonomous vehicles navigate our world with confidence—because on the road to autonomy, every nanosecond matters. #AutonomousVehicles #OCXO #AdvancedDriving #SensorFusion #SmartMobility #EmbeddedSystems #DynamicEngineers #Innovation #EverythingRF

11

11 Comments

With NVIDIA Alpamayo, autonomous vehicles are learning to reason, not just react. Learn more about how NVIDIA Alpamayo is accelerating the development of AV technology in this Hugging Face post, penned by Marco Pavone, Director of Autonomous Vehicle Research at NVIDIA. 🔗 Read the blog: https://bit.ly/4skRRYi 🚗 Check out the model: https://bit.ly/498T25E

9

Thinking about setting up a home lab to get hands-on with embedded systems? You don’t need a fortune or a fancy setup to start learning, experimenting, and building cool stuff. Here’s how I’d recommend getting started based on what’s worked for me and other engineers I’ve worked with 👇 1️⃣ Start Simple, Go Practical 🖥️ Grab a dev board like an Arduino, Raspberry Pi, or ESP32—whatever fits your level and goals. 🔌 Breadboards, jumper wires, resistors, LEDs… the classics still do the job. 🧰 No need for overkill—just enough to build and test your ideas. 2️⃣ Spend Smart 💸 You don’t need a $2k oscilloscope. A multimeter and a basic logic analyzer cover a lot. 🧾 Buy what you need when you need it. 🖨️ 3D printer or CNC? Only if you’ve got a clear use case (and space!). 3️⃣ Keep It Safe + Tidy ⚡ Always protect your setup—surge protectors, ventilation, and safe wiring. 📦 Label stuff, use drawers or even old takeaway containers. 🧹 A clean bench = fewer mistakes and better builds. 4️⃣ Don’t Build in a Bubble 🌐 Join Reddit threads, Discords, LinkedIn groups, or local meetups. 👥 Learning from others’ mistakes saves years of trial and error. 🤝 Community helps you push further, faster. 5️⃣ Stay Sharp 🧠 This space evolves fast—microcontrollers, RTOS, edge AI… it never stops. 📚 Online courses, GitHub, teardown videos—it all adds up. 🧪 Tinker often, break things, and figure out why they broke. 6️⃣ Log the Journey 📝 Keep track of what you build, what breaks, and what works. 💻 Use a Git repo, Notion page, or plain notebook—whatever sticks. 📸 Bonus: great portfolio material if you’re ever job hunting. 💬 Got a lab already or starting one soon? Would love to hear what gear, boards, or projects you’re diving into. Drop your setup or advice below 👇 Let’s learn and build together. 🔄💬⚙️ #EmbeddedEngineering #HomeLabSetup #DIYElectronics #EngineerLife #HandsOnLearning #RunTimeTips #Arduino #ESP32 #RaspberryPi

147

29 Comments

Ultimately, our goal at Binho is simple.  For those serious about embedded systems, we want to be the team and the toolkit that helps you ship.  That might mean contracting us to: - Design firmware and PCBs - Built a custom analyzer - Standardize on Mission Control and host adapters for your whole lab However you plug us in, the outcome we care about is the same.  Fewer unknowns, faster learning, and hardware that actually makes it out into the world.

22

Almost exactly 3 years ago I was privileged to stand on stage in Santa Clara and announce the first wave of AI for verification. Today we make probably the most exciting announcement since then! Really excited to work with the ChipStack team as we define and develop Agentic AI for IC development together! ~~ We’re excited to announce that ChipStack, a pioneer in agentic AI for chip design and verification, is joining Cadence. ChipStack’s generative AI-driven platform helps accelerate design and verification workflows through deep design understanding, intelligent test planning, test generation, and AI-assisted debugging. Why this matters for our customers: ✅ Accelerated Verification – Move from weeks to days for front end IC design. ✅ AI-Powered Productivity – Scale without proportional headcount. ✅ Unified Flow – ChipStack’s generative AI agents will integrate seamlessly into Cadence’s Agentic AI and EDA solutions. ChipStack brings deep expertise in AI-driven design understanding, intelligent test planning, and AI-assisted debugging—strengthening our commitment to innovation and time-to-market acceleration. 👉 Read blog: https://ow.ly/NX2E50XpxZI #ChipStack #AI #Semiconductor #Design #Verification

448

7 Comments

Good embedded software should survive a hardware swap. If changing your MCU breaks your logic, your architecture is wrong. And that’s a problem. Because in the real world: - Parts go out of stock - BOMs shift - Boards get respun - Vendors get replaced If your firmware is tightly coupled to the silicon, every hardware change becomes a major rewrite. But if your architecture is clean: - Business logic sits above clear interfaces - Drivers are swappable - Hardware quirks are isolated, not scattered Remember, modern embedded systems aren’t static. They’re evolving platforms. And good platforms don’t fall apart when one component changes. So if you’re serious about maintainability, build your system like it might outlive the hardware it runs on.

221

21 Comments

I visited Santa Monica earlier this year and was surprised by how many self-driving cars I saw—especially Waymo’s. It felt like the future had already landed. But beyond the cool factor, I started noticing the smaller systems, needs, and business gaps forming around them. In this post, I explore not only the major infrastructure shifts but also the hidden micro-opportunities—some so accessible that even solo builders and small investors can get involved. https://lnkd.in/g2vbivA3

10

🚨 DFT verification is no longer just a technical hurdle—it's a strategic imperative. As silicon complexity explodes and time-to-market windows shrink, traditional simulation methods are buckling under the weight of modern ATPG and MBIST workloads. The result? Verification bottlenecks that threaten tape-out schedules and product reliability. Microsoft faced this challenge head-on: “Questa One DFT (QDX) simulation utilizes advanced DFT-centric simulation capabilities to deliver faster performance than existing simulation solutions, slashing our verification time from weeks to days,” said Selim Bilgin, corporate vice president, Silicon Engineering at Microsoft. “In addition to these impressive speed ups, on Microsoft’s Azure Cobalt 100 platform, QDX delivers up to 20 percent further performance jump unlocking even greater efficiency for our EDA workloads.” Siemens is proud to partner with industry leaders like Microsoft to redefine what’s possible in DFT verification. Questa One Sim DX—part of the broader Questa One Smart Verification solution—delivers: ✅ Serial and parallel ATPG simulation acceleration ✅ Zero-delay and timing-aware scan simulation ✅ On-the-fly reconfiguration for retargeted pattern verification ✅ MBIST/BISR simulation optimizations ✅ Multi-core and cloud-native performance scaling 🔗 Learn how Questa One Sim DX can accelerate your DFT sign-off and eliminate verification bottlenecks:👉 https://sie.ag/TeyNK #DFTVerification #EDAInnovation #QDX

35

Embedded systems world has changed. But not everyone updated their mindset. We’re no longer just writing code for blinking LEDs or UART drivers. We're building: Distributed systems OTA-ready firmware Safety-critical applications Tools that generate code from models Software that is the product And yet... I still see engineers resisting new tools. Leaders ignoring automation. Documentation out of sync with code — because "we’ll do it later." "Imagine asking someone who has only worked on 8-bit MCUs to now architect a system with FPGAs, STM32s, CI/CD pipelines, and model-based design. That’s the real transformation happening in the field." I’m not judging — I’ve seen this first-hand. And I’ve grown not just from experience, but from: 1. Failing forward 2. Reading deeply 3. Learning from engineers smarter than me 🧠 Early-career engineers — you’re in a golden era. But don’t just collect courses. Build systems. Read deeply. Learn relentlessly. Adaptability > raw knowledge. Your career won’t be built on what you know. It’ll be built on how fast you adapt.

69

2 Comments

I see a lot of posts here about The Zephyr Project that go something like this: "I use <FreeRTOS/bare metal/etc> for simple embedded firmware projects. I use Zephyr for <complex combination of BLE/Wi-Fi/cellular/sensors/etc>. Once I got past the steep learning curve, the complexity of Zephyr was 100% worth the benefits in terms of modularity, portability, etc." I'm curious: for those of you who have become REALLY proficient with Zephyr, do you find yourself still turning to things like FreeRTOS for "simple" projects? Or do you find that you are just using Zephyr whenever possible now, even for projects that "don't require Zephyr"? Obviously there are cases where Zephyr is obviously not a good fit, and likewise, cases where Zephyr is obviously a great fit. I guess this question is about those in-between cases where you could go either way. Once you have mastered the complexity of Zephyr, are you finding that Zephyr is allowing you to move faster even for simple projects (because of the ecosystem, tooling, etc)? Or does the complexity of Zephyr have a non-diminishing overhead that doesn't make sense for some projects?

35

19 Comments