r/embeddedlinux • • Nov 26 '25

How would you implement safe OTA updates for Linux-based IoT devices (without full OS reflash)?

28 Upvotes

I’m working on an industrial IoT device running Linux (NanoPi-level SBC).
I don’t need a full A/B partition OS update solution like Mender or Balena.

What I do need to update remotely:

  • systemd services

  • Python application

  • networking config (static IP / Wi-Fi configs)

  • internal scripts + system config files under /etc/, /usr/local/, etc.

My goal is something reliable, secure and rollback-friendly — but not heavy like full rootfs OTA.

Current thinking:

  • A versioned .tar.gz “update bundle” containing files + YAML instructions

  • OTA agent (Python) running as a systemd service

  • Steps: download → checksum verify → pre-install steps → update files → restart services → post-install steps → rollback on failure

  • Only reboot if needed

Before I go too far — how would you architects/designers approach this?

I’m curious about:

  • Proven patterns or best practices

  • What pitfalls I should avoid

  • Whether there are existing lightweight tools/libraries people use

  • Whether packaging updates as .deb or using containers is better long-term

Not looking for “just use Mender/RAUC/Balena” — I know those options.
I’m specifically looking for meaningful advice from people who’ve deployed mid-level Linux OTA at scale.

Any discussion or architecture examples would be hugely appreciated.


r/embeddedlinux • • Jun 11 '20

Top Five Libraries for creating GUI on Embedded Linux

28 Upvotes

r/embeddedlinux • • Jan 15 '21

emba, a Linux firmware scanner for embedded devices, got a big update - new static version detection, improved emulation module and the final aggregator with CVE and exploit detection - https://github.com/e-m-b-a/emba - check it out!

Thumbnail
gallery
26 Upvotes

r/embeddedlinux • • Oct 14 '20

Got your hands on an embedded Linux firmware and want to find vulnerable spots? Use emba, it's free and easy to use. If you like it, leave a ⭐ on github :)

Thumbnail
github.com
26 Upvotes

r/embeddedlinux • • Sep 14 '25

How do I go about learning embedded Linux? Suggest some projects

25 Upvotes

Already asked this on r/embedded subreddit, Discovered this subreddit just yesterday so asking here for your opinions.

I have been about 3 years in embedded domain worked on hardware and firmware mostly. I have daily driven linux (Ubuntu) for this tenure. I am well versed with OS and scheduler concepts(did it as a part of work, interview prep and basic training). I am thinking about learning embedded linux development (yocto, build root etc). How should I go about learning them hands- on and dive deep? What projects should I implement that will help me land such roles? Suggestions are welcome, thanks.

Is it better to buy a raspberry pi 4 and practice it or just practice it on qemu or other emulators?


r/embeddedlinux • • Feb 16 '25

what do you expect from a junior embedded Linux engineer to know?

25 Upvotes

Hello everyone!


I'm thinking about going into embedded Linux track, and I'm trying to be aware of the requirements of the job. I would appreciate any kind of advice!


r/embeddedlinux • • Nov 27 '22

How did you "break in" to embedded Linux development work?

25 Upvotes

I'm an embedded software engineer with 20+ years of experience developing C applications and drivers for micro-controllers on RTOS and bare-metal platforms. For the past several years I've noticed a consistently high demand for embedded Linux software engineers, and I'd like to branch into that area. Trouble is, they all seem to require several years of experience specific to developing for embedded Linux.

It seems like such a cach-22. No experience, no entry point to gain experience, but it just doesn't make sense that someone with a great deal of non-Linux embedded development experience can't "break in" to embedded Linux work.

Is there anyone else here that moved their career from the world of microcontrollers/RTOS/bare-metal to embedded Linux? How were you able to "break in" ?


r/embeddedlinux • • Oct 19 '26

project DTSee - A browser-based Device Tree explorer and visualizer for embedded Linux

24 Upvotes

Like many of you working on embedded Linux platforms, I have spent countless hours scrolling through massive Device Tree sources, jumping between dtsi/dts files, and trying to trace tangled phandles, clocks, interrupts, and regulators.

To make this less painful, I have been building DTSee, a free, browser-based Device Tree explorer designed to make navigating and understanding board descriptions a bit easier.

Key Features

  • Dual Format Support: Works with both DTS and DTB files (includes client-side DTB to DTS reconstruction).

  • Interactive Hierarchy: Easily drill down through nodes, properties, and child devices.

  • Graphical Relationships & Phandle Analysis: Visually trace how hardware components link together.

  • Hardware Context: Quick access to register ranges, clocks, interrupts, GPIOs, regulators etc.

  • 100% Client-Side: Everything is processed locally right in your browser. No files are ever uploaded, making it safe for proprietary or NDA work.

What is Next? (Roadmap Ideas)

The project is still in beta, and I am actively brainstorming features for future versions:

  • Device Tree Comparison: Diffing two DTBs or DTS files side-by-side.

  • Deeper Hardware Dependency Analysis: Visualizing power trees and clock trees more holistically.

  • Source Tracking: Following definitions and overrides cleanly across complex DTS/DTSI include chains.

Give it a spin

If you have a DTB or DTS file lying around, I would love for you to give it a try:

https://dt.kernelnoise.com

Your feedback is invaluable. Whether you run into missing references, incorrect interpretations, usability quirks, or have ideas for additional features, I want to hear it all. Cheers


r/embeddedlinux • • Jun 29 '26

Best way to learn Embedded Linux for someone with an MCU/firmware background?

24 Upvotes

I have a background in embedded systems and currently work mainly on MCUs, writing firmware in C/C++. I'm comfortable with topics like peripherals, RTOS, debugging, communication protocols (UART, SPI, I2C, CAN), and general embedded development.

Now I want to transition into Embedded Linux and would like some guidance on the best learning path and resources.

Specifically, I'm interested in learning:

Linux internals relevant to embedded systems

Device drivers

Device Tree

Bootloaders (U-Boot, etc.)

Kernel basics

Build systems like Yocto or Buildroot

Debugging techniques (JTAG, GDB, tracing tools)

Practical projects that can help me gain hands-on experience

I prefer learning through books, courses, and real projects rather than just theoretical material.

For those who made a similar transition from bare-metal/RTOS development to Embedded Linux, what resources, books, courses, or project ideas would you recommend?


r/embeddedlinux • • May 19 '22

I made a video comparing Yocto and Ubuntu Core for embedded Linux: what are your thoughts? [I work at Canonical]

Thumbnail
youtube.com
24 Upvotes

r/embeddedlinux • • Nov 16 '25

Suggest me some low budget hardware to learn embedded linux booting

23 Upvotes

Hello all I'm Embedded FW dev with strong understanding of bare Metal and RTOS and bootloaders however I want to learn Embedded Linux as I will need it at some point in my career but when learning I want hardware documentation to he more clear and clean raspberry Pi is good for beginners but they abstract alot of information and it's just good to make work but not great to learn internals of embedded linux so now I've two options BeagleBone vs ST and I have tight budget of around 5~6K INR do you guys have any recommendation on hardware board I should choose to learn for trial and errors on linux? Or do you know other suppliers with good documentation and cheap board which are helpful?

Or if someone's willing to sell their old working board which they no longer use will also be helpful in India.


r/embeddedlinux • • Sep 19 '25

learning embedded linux from bare metal embedded software background

23 Upvotes

Hi everyone,

 

I have around 10 years of solid experience in embedded system using bare metal, FreeRtos, Autosar , and dealing with different stack…. as well as hardware Design.

lately, I started looking for a jobs and I noticed that there are too many offers around the embedded Linux which I don’t have experience with.
I bought a raspberry pi to try to explore it and familiarize myself with and I have a couple of questions:

 

1-     Does developer in Linux generally uses text editor like vim to develop their code? I feel like it’s ok for a small code / project but for bigger project with different source / header files it become impossible to handle it.
In embedded we usually uses IDE like IAR, keil, vs code ..where we have all your source file for our project in one place and we can easily navigate between them, one other advantage is that you can easily navigate to the definition / declaration of each function even if it is located in other source file.
suppose you are a team of 3 software working on big project like developing a software for a router using embedded Linux, which tool do you uses to develop your code ? do you use IDE or vim?

2-     Suppose I want to use the Bluetooth, so I installed the ‘libbluetooth-dev bluez’.
everytime i install a new packages i have a hard time locating the heder files for this packages, is there anyway to know where's the packagesd file are located ?
then I want to know how to explore the api provided by these new packages ? should I have to explore the header files or is there any best practice ? like having these api listed somewhere else like website etc..

3-     any advice for someone who want to learn embedded linux and coming from non liunux background ?any recommendation for online training that might improve my Linux skills ? what should i do learn first ?

4 - do you think it will be a hard journey to master embedded linux for my case ?

thanks, 😊


r/embeddedlinux • • Jan 15 '20

Buildroot fot beginners, part 1:General information, minimum system build, setup via menu

23 Upvotes

https://medium.com/@boozlachu/buildroot-part-1-general-information-minimum-system-build-setup-via-menu-32fdb389eebc

It's first part of my own manuals for buildroot beginners. I want so systemize my experience and share it for neofits.

Comments on the case are welcome.


r/embeddedlinux • • Dec 29 '25

What to learn Zyphr Rtos or Embedded linux driver development?

22 Upvotes

I am fairly new to embedded systems, though I have experience with STM32 and FreeRTOS. Whenever I search for embedded development roles on job portals, I frequently see Zephyr RTOS mentioned. Other job profiles specify Embedded Linux driver development. Does embedded driver development align with the profile of an embedded developer? Furthermore, should I focus on learning Embedded Linux development or Zephyr RTOS first?


r/embeddedlinux • • Dec 22 '25

How to break into Embedded / Embedded Linux after graduation and industry experience?

22 Upvotes

After graduating, I’ve been actively looking for entry-level opportunities in Embedded Systems and Embedded Linux for almost two years. I started my search right after graduation and continued it in parallel while working in industrial automation. During this time, I found that highly specialized embedded roles—especially Embedded Linux positions—are quite limited locally. Instead of staying idle, I focused on gaining strong hands-on experience in industrial automation, while continuing to build my embedded skill set alongside it. I also strengthened my electronics fundamentals and learned PCB design, working on schematics, PCB layout, and microcontroller-based hardware projects. I’m now exploring opportunities outside my country as well, particularly internships, co-ops, or junior roles that could help me transition fully into Embedded / Embedded Linux. I’d really appreciate any advice on how to approach this transition or where to focus my efforts.


r/embeddedlinux • • Sep 23 '20

I need to quickly get myself comfortable with Yocto (for a job), having never built stuff for Linux before. Is it better to get myself signed up to a course, get some books and plough through them or just mess around with boards until I "get it"?

22 Upvotes

I'm a bare metal embedded dev who has found themselves in a position where I need to develop an embedded Linux based product for my company. Th time frame for this product is tight-ish.

The way I see it there are three ways for me to approach this:

  1. Just get on with it by bringing up a dev board and fiddle with it until things work, reading up on the internet about stuff as I go along - I think in the long run this is the best way to actually learn CS stuff but it has two major drawbacks: making it extremely difficult for me to estimate future work, and general concern that I might be hacking a thing together as opposed to doing it properly. This approach will often teach people how to do things so that they work most of the time - but fail to teach people why they should be done that way, and hence not be that grate for gaining a real understanding of the necessary concepts.

  2. Get signed up to a course. My company signalled that they'd be willing to pay for some training for me, but I'm convinced about the effectiveness of courses. I've been sent on courses in my past job and I found them, well, super underwhelming and not that useful. I felt the main benefit of courses is having a syllabus, i.e. telling you what you need to know to be able to accomplish this and that. I feel like once I know what I need to learn, I could learn more effectively in my own time. Are things different with Linux / Yocto courses? Do you know good online ones which would give me a solid base?

  3. Get some books / youtube videos and self-educate. I feel this one can be super effective, but the tricky part is knowing exactly what I need to learn and finding the right resources for it. Do you have any suggestions for books for someone who is completely new to building stuff for linux?

I'm not sure which one of those approaches is likely to be the most effective, mostly time-wise. Both 2 and 3 have me spend a whole lot of time upfront on just learning before actually doing prototyping work for my company. That said, 1. can introduce problems down the line because of rookie mistakes and things not being done properly from the start.


r/embeddedlinux • • Oct 01 '26

monthly thread Embedded Linux Jobs Monthly Thread - October 2026

21 Upvotes

Rules For Individuals

  • Don't create top-level comments - those are for employers.

  • Feel free to reply to top-level comments with on-topic questions.

  • Reply to the top-level comment that starts with individuals looking for work.

Rules For Employers

  • The position must be related to embedded linux (for general embedded jobs, check r/embedded's dedicated threads)

  • You must be hiring directly. No third-party recruiters.

  • One top-level comment per employer. If you have multiple job openings, that's great, but please consolidate their descriptions or mention them in replies to your own top-level comment.

  • Don't use URL shorteners.

  • Templates are awesome. Please use the following template. As the "formatting help" says, use two asterisks to bold text. Use empty lines to separate sections.

  • Proofread your comment after posting it, and edit any formatting mistakes.

Template

  • Company: [Company name; also, use the "formatting help" to make it a link to your company's website, or a specific careers page if you have one.]

  • Type: [Full time, part time, internship, contract, etc.]

  • Description: [What does your company do, and what are you hiring embedded linux devs for? How much experience are you looking for, and what seniority levels are you hiring for? The more details you provide, the better.]

  • Location: [Where's your office - or if you're hiring at multiple offices, list them. If your workplace language isn't English, please specify it.]

  • Remote: [Do you offer the option of working remotely? If so, do you require employees to live in certain areas or time zones?]

  • Visa Sponsorship: [Does your company sponsor visas?]

  • Technologies:


r/embeddedlinux • • Dec 12 '25

Junior Embedded Engineer Seeking Career Advice: Bare Metal vs RTOS vs Linux

21 Upvotes

Hello,

I am currently working as a junior embedded engineer at a small company in South Korea, and I have about two years of experience.

Most of my work is based on outsourced projects using fine dust (PM) measurement sensors. I mainly build fine dust sensor stations for places such as farms, schools, and control rooms.
In addition, I am currently developing a CAN communication keypad that will be used by a large Korean heavy equipment manufacturer.

So far, I have been writing code mostly in bare metal. Recently, I received advice (including from ChatGPT) suggesting that I should transition from bare metal to RTOS as soon as possible, and then move toward Linux BSP development in order to increase my market value.

After doing some research on my own, I learned that RTOS and Linux are generally better choices for developing more advanced embedded products, especially those that include displays and communication features.

I have tried to set a rough direction for myself, but I would really appreciate any additional advice.
I am also interested in working outside of Korea, particularly in North America. I am curious whether the technology stacks used in the US or Europe are similar to what I described above.

Thank you very much for your time and advice.


r/embeddedlinux • • Dec 21 '23

Why learn embedded Linux?

21 Upvotes

I have been working as an embedded system developer for the past 2 years. However, I have zero experience with embedded Linux.

I have searched for the answers to "Why learn embedded Linux? " But I haven't got any clear answers from the internet as of yet. I am hoping to get a clear answer in this community.

Also, if embedded Linux is common why aren't there many projects related to it no Upwork?

Thanks


r/embeddedlinux • • Apr 30 '21

I’m putting a WiFi router into a wall charger!

Thumbnail
machinehum.medium.com
21 Upvotes

r/embeddedlinux • • Feb 25 '21

emba - an analyzer for Linux-based firmware of embedded devices: We developed many great features in the last few weeks, like full Docker support, better modules for detailed analyzing, a web report and a complete rewrite of our documentation: Check it out and tell us, if you like it or not.

Thumbnail
github.com
21 Upvotes

r/embeddedlinux • • Mar 08 '26

Took the first step in learning embedded linux

20 Upvotes

I am happy today. I used buildroot to create an image which has minimum modules to play an MP3 file via usb headphones. This is my hello world of multimedia embedded linux.

It was quite an experience. I have used Linux as my host machine for years. I have been writing code for MCU based products sincr 4 years. But doing this project was very satisfying experience.

I like how linux has kind of everything. So you want to make a minimal OS for your electronic product? Sure, make one. All the tools are at your disposal. If you don't find the tools you need, just make your own and share it with people. I like this idea a lot.

I ran into many problems like missing out on some packages (I hope this is the right word), having low space in my sdcard for storing the MP3 song, making a connection between the host and eLinux device to share the file system, etc. It wa fun.

And hands down, buildroot is one of the most useful tools I have ever used. Just amazing. You can select packages and build an OS?? Wowwww.

This is what I understand: to play an MP3 file, there are many software packages required and they have individual jobs. You build them, link them all together and use a program which is written to call all these sub-programs to play the music. I have so much to learn and understand, but I need to understand where to draw the line and move forward. My end goal is to make a media player device using my BBB board.

I like many songs, but I felt the happiest when I played the 735KB MP3 file I downloaded from internet simply because I figured out the environment required for it play it.


r/embeddedlinux • • Feb 28 '26

Beginner Embedded Developer (1.5 YOE) Looking for Freelance / Part-Time Projects

20 Upvotes

Hi everyone,

I’m a 23-year-old embedded systems engineer from Gujarat, India, currently working full-time in a core embedded role with around 1.5 years of experience.

I’m looking to take up small freelance or part-time embedded projects to sharpen my skills and gain more real-world exposure.

My experience includes:

•	C programming (bare-metal & embedded)

•	Basic RTOS concepts

•	ARM-based systems

•	Firmware debugging & bring-up

•	Working with peripherals (UART, SPI, I2C, GPIO, etc.)

•	Basic Linux understanding (boot flow, drivers overview)

I consider myself still in the learning phase, so I’m open to:

•	Small paid tasks

•	Prototype development

•	Debugging help

•	Assisting in ongoing projects

•	Even collaborative/learning-based work

I’m reliable, consistent, and genuinely interested in building strong fundamentals in embedded systems.

If anyone has small projects, startup work, or needs support in embedded firmware development, I’d be happy to connect.

Thanks in advance 🙂


r/embeddedlinux • • Dec 12 '25

Real-Time Inter-Process Communication (IPC) Libraries for Embedded Linux (C & Rust)

20 Upvotes

I’ve been working on a pair of sibling libraries that provide real-time–capable inter-process communication for embedded Linux systems:

Both libraries are fully compatible with each other, so an application written using the C version can communicate seamlessly with one using the Rust version.

Status / Disclaimer

These libraries are early-stage and currently unstable.
Documentation is still sparse, but each repo includes at least one working example that shows how everything fits together. Feedback is very welcome.

Motivation

A core principle of the Unix philosophy is “do one thing and do it well.”
Microservice-like architectures follow the same idea—break functionality into small, cleanly separated processes.

In embedded systems, however, I often hear the argument that real-time constraints prohibit IPC, which often leads to tightly coupled (and sometimes messy) software architectures. My goal with this project is to show that real-time IPC is absolutely possible with the right design.

How It Works

At the heart of both libraries is a zero-copy, wait-free, single producer single consumer circular message queue. Key characteristics:

  • Zero-copy data transfer

  • Wait-free SPSC algorithm

  • Cacheline-aligned fixed-size messages

  • Nearly no runtime overhead — can even outperform mutex-protected shared data access within a single process

  • Uses shared memory + optional eventfds for signaling

Basic Flow

  1. The client sets up producer/consumer queues in a shared memory region and creates optional eventfds.

  2. It sends a unix message containing queue parameters, user data, the shared memory file descriptor, and eventfds to the server.

  3. The server maps the shared memory and initializes its queues.

  4. Both ends can now exchange messages in deterministic, real-time–safe fashion.

Current State

  • Two implementations: C and Rust

  • Cross-compatible (Rust ↔ C)

  • Suitable for embedded/RT workloads, but still evolving

Future Work

I’m developing a schema compiler in Python using Lark:

  • Repo: https://github.com/mausys/rtipc-compiler

  • Current status: Parsing + structure verification are implemented; code generation not yet started

  • Goal: Generate message definitions for multiple languages—similar to protobuf, flatbuffers, cap’n proto, thrift, etc., but much simpler because only fixed-size messages need to be supported.

Higher-level languages (Java, Python, C#, etc.) will interface through the C bindings.

If anyone is interested in real-time IPC, has feedback, or wants to experiment with the examples, I’d love to hear your thoughts!