In this episode, Tim Bird (Sony) joins us to discuss Linux in space:

• Tim’s path from early embedded Linux at Lineo (Sharp Zaurus) to 20+ years at Sony on cameras, TVs, phones — and now Sony’s space work (Space Communications Corp, the SLIM micro rover, and the STAR SPHERE satellite).
• How much Linux is already in orbit: ~50% of satellites by project, ~90%+ by raw count thanks to Starlink’s 10,000+ Linux-based satellites.
• The Space Grade Linux (SGL) project: modeled on Automotive Grade Linux, currently an ELISA work group, targeting a standalone Linux Foundation project in 2026. Delivers a meta-sgl Yocto layer with planned integrations for Space-ROS, Core Flight System, and F Prime.
• The “big five” challenges of space — radiation, thermal cycling, vacuum, launch vibration, and no service calls — and how commodity hardware (Ingenuity’s Qualcomm processor, Perseverance’s base station) is pushing past traditional rad-hard designs.
• Emerging work on fault-tolerant file systems (FTRFS, ZFS), QEMU-based radiation simulation, OTA updates at fleet scale (SpaceX Starlink), and why AI workloads on orbit favor a general-purpose OS.
• How to get involved: monthly SGL calls, the meta-sgl repo at github.com/elisa-tech, and the BeagleV-Fire reference board.
• Advice for newcomers: embedded is in a golden age — start cheap (Raspberry Pi, Arduino-based kits like CrunchLabs), blink some LEDs, and grow from there.

Discuss this episode at our community site.

In this episode, we reflect on 2025:

1. Intro and theme

   • Cliff and Khem look back on 2025, focusing on how AI, Zephyr/Yocto, and tooling changed daily engineering work.

2. AI as co-developer

   • Khem shifts from hand-written scripts to delegating tasks to AI as a co‑developer, not an autonomous agent.
   • Cliff adopts terminal-first AI tools (Cloud Code, etc.) for Bash, Ansible, Dockerfiles, and content workflows (newsletter/blog, diagrams).

3. Doc Driven Development workflow

   • Cloud Code plugin: Doc Driven Development, part of Cliff’s Claude plugins: tmpdir-claude-code-marketplace.
   • Workflow: write docs → AI generates plan → review → AI generates code, treating AI like a compiler whose inputs (docs/plans) are versioned.

4. Zephyr and AI-friendly context

   • Work with Zephyr (and West) keeps BSPs and app code in Git repos, making it easy for AI tools to see full build context and outperform GUI‑centric MCU tools with hidden code.
   • Zephyr is expected to become the default RTOS as capable MCUs remain inexpensive.

5. Yoe, Yocto, Jetson, and OTA

   • Jetson Nano and AGX Orin have been added to the Yoe Distribution as reference platforms with swupdate-based OTA and a rootfs+data partitioning strategy aimed at real products, not demos.
   • A rolling-release Yocto model plus meta-tegra’s upstream‑first approach keeps changes small and manageable.
   • Staying close to upstream and ensuring BSP changes land there first is called out as key to long-term maintainability of embedded products.

6. Kas and project structure

   • The Yoe Distro is migrating from shell-based project definitions to Kas for more structured, composable project descriptions and easier reuse/inheritance.

7. Editor and shell stack

   • Helix editor: helix.
   • Yazi file manager: yazi or org: yazi-rs.
   • Lazygit: lazygit.
   • Zellij terminal workspace: zellij.
   • Cliff standardizes on Helix plus Yazi, Lazygit, and Zellij for a fast terminal environment; Khem aliases vi to Helix after finding it better for huge files than Vim-with-plugins.
   • Khem experiments with Nushell’s table-centric pipelines, seeing potential with AI but noting syntax incompatibility with traditional shells.

8. Custom tools: BRun and HFID

   • BRun (Cliff’s project): brun.
   • BRun provides a YAML-defined, local workflow runner (GitHub Actions–like) for native Yocto builds, with chained tasks and smart notifications (emails, Notify.sh, tail logs on failure).
   • HFID is provided as a hosted service (not open source); concept and usage are described at HFID and in posts linked from BEC Systems.

9. Desktops, Omarchy, distros, and servers

   • Khem runs Hyprland tiling on Arch for low-memory build machines while still using KDE elsewhere; Arch makes switching easy at login.
   • Omarchy, DHH’s Arch+Hyprland Arch based distro for developers, is highlighted as a polished, opinionated entry point for new Linux users: omarchy.org.
   • Omarchy is great for people who want a ready-made Arch+Hyprland setup, while vanilla Hyperland is a better fit for experienced users who already have strong preferences.
   • Arch on servers works well when combined with Ansible-based configuration and non-golden-machine practices so systems can be rebuilt quickly if needed.

Discuss this episode at our community site.

In this episode, we discuss with Ted Speers the history of FPGAs and the inclusion of RISC-V technology in Microchip’s latest PolarFire products. Ted is an industry veteran and shares his experiences, including why they chose RISC-V and the resulting benefits. Pay special attention to his general advice starting 1:15:26.

Strategy is not being some smart guy figuring out we are going to do this, this, and this, and it’s all going to work out. Strategy is creating options for yourself. You always want to create optionality. As soon as you get locked into one track, that may lead to failure. So creating optionality, if you are a young person, is what you want to do with your career. One way to create optionality is to meet people. The way you make your own luck is create the options. Then you are in a robust, anti-fragile position.

Ted recommends books by Nassim Nicholas Taleb such as The Black Swan.

Discuss this episode at our community site.

In this episode, we discuss Embedded Linux with the authors of Mastering Embedded Linux Development. Highlights:

• How this book came to be.
• What is new in the fourth edition.
• Development platforms used in the book.
• Common Embedded Linux pitfalls.
• Why Yocto instead of Ubuntu.
• Android in embedded systems.
• And lots more …

If you are interested in Embedded Linux, this book is an excellent reference that covers a lot of topics (710 pages!!!).

You can buy this book at most of the usual places. I got a DRM free version at Packt.

Discuss this episode at our community site.

Clang was recently moved from a seperate layer into oe-core. In this episode Khem shares why this happened and why Clang may be a good fit for your product development.

Discuss this episode at our community site.

Today we catch up with Matt Madison, the maintainer of the meta-tegra layer for NVIDIA Jetson embedded products.

Matt was also on our podcast last year.

Discuss this episode at our community site.

In this episode, we visit with Justin Schneck from Peridio about how Avocado OS is solving various problems in the embedded Linux space. Avocado’s attributes are composability, extensibility, and security. This platform composes embedded runtimes, which seems like a practical alternative to containers at the edge.

Discuss this episode at our community site.

In this episode, we discuss rolling releases, some of the advantages, and how we build the Yoe Distribution, which is a rolling release embedded Linux distro.

Discuss this episode at our community site.

In this episode, we learn:

• how the writing process works for Michael
• how it has affected his career
• The new book Michael is working on to help developers become more effective writers
• Good writers do not necessarily like writing. “I hate writing, but I love having written.”

If you are interested in becoming a better writer, sign up for updates at Refactoring English.

Also check out Michael’s blog.

During the show, Cliff shared a quote from Leslie Lamport:

“If you’re thinking without writing, you only think you’re thinking.”

Discuss this episode at our community site.

In this episode, we learn about Alex’s work with LLVM on RISC-V. Alex has been involved with RISC-V since it was first released and recently has been focused on making LLVM support better. Alex shares some details about this work, as well as general ideas on how he works. Alex is also the author of the LLVM Weekly Newsletter, which he has published for over 10 years.

Discuss this episode at our community site.

In this episode, we discuss what is simplicity, why does it matter, and how to get there.

Discuss this episode at our community site.

In this episode, we discuss the difference between a product and technology. A couple related blog posts from Khem on this subject:

• Product and platform/technology
• Opensource in context of product and platform/technology - Example

Discuss this episode at our community site.

In this episode, we discuss some of the new tools we started using (more) in 2024 that can help you become a more productive developer.

• Zellij
• Helix
• Terminals
  • Alacritty
  • Kitty
  • Ghostty
• tio
• fd
• rg
• Perplexity
• Yazi
• LazyGit

Discuss this episode at our community site.

In this episode, we discuss the tendency to end up on a hard fork of an OSS project, how this happens, and why we should consider another model.

Discuss this episode at our community site.

In this episode, we learn how the BeagleBoard Foundation does open hardware and how their products can be useful in your product development efforts.

Notes:

• how Beagleboard products are different than Raspberry PIs
• why open hardware is important
• overview of some of Beagleboard.org’s products
• why upstreaming development is important
• how to do things right
• discussion about RISC-V
• and more

See the Beagleboard.org main site and documentation site for more information.

Discuss this episode at our community site.

In this episode, we discuss our recent experiences building a product using Zephyr, and how Zephyr has helped us move fast and quickly integrate advanced features like a HTTP server, non-voltile store in flash, device support, etc. We also discuss how to set up a project in Zephyr and have built a project template that demostrates how to use the Zephyr T2 workspace setup. This template also includes common things projects need like a web application example.

Zephyr SimpleIoT

Discuss this episode at our community site.

In this episode, we discuss how 3D printing in manufacturing can help you by reducing cycle times, shorten lead times, etc.

Outline:

• what makes companies successful
• growing a company
• 3D printing in design and manufacturing
  • design during day, print through night, test in morning, and repeat
• design for manufacturing
  • production vs hobby 3D printers
  • types of filament
  • print part number and revision into each part
• manufacturing in-house vs outsourcing

Discuss this episode at our community site.

Matthew is an expert in Lean Manufacturing and shares with us an overview of the basic concepts and what has worked for him and the companies he works with. In this episode, we explore how ideas the manufacturing space can also improve our product development efforts.

Resources:

• Matthew’s web site
• The Toyota Way
• Lean Thinking
• The Motive

Discuss this episode at our community site.

In this episode, we discuss Yocto support for Nvidia embedded processors, such as the Jetson devices that are increasingly being used to power edge AI applications. Matt created and maintains the meta-tegra layer. meta-tegra is one of the highest quality BSPs we’ve used, so learn from Matt how he maintains it, what makes a good BSP, and many other thoughts from an experienced Yocto/Embedded Linux developer.

Discuss this episode at our community site.

In this episode, we discuss aspects running AI on edge systems (both microcontrollers and embedded Linux). Chris has a lot of experience doing this and has used AI at the edge in multiple projects to solve real problems. This episode provides an overview of the technology and will help you understand the steps to implementing an AI model in your system.

Chris has published an open source project for implementing neural networks on embedded systems.

Discuss this episode at our community site.

Great discussion with Eystein on updating systems, how Mender has evolved over the last ~10 years, and more:

• Eystein has a background in Math and cryptography
• Company started as CFEngine
• Things people tend to not think about with system update:
  • security
  • reliability (power loss, does it resume downloads when there are network issues, etc.)
  • future products – is the solution general
  • scheduling
  • updating multiple devices in the system
• Mendor milestones
  1. OSS release
  2. SaS service
  3. advanced environments, complex deployments, orchestration, etc
• OSS foundation
  • open-core model
  • product led growth
  • is working well
• Programming languages
  • Switching the Mender client from Go to C++ so the client is more portable.
• Platform vs Product
  • Product – narrow set of problems, pick what you need, less vendor lock-in
  • Platform – wide focus and tends toward locked in
• Interesting in the technology space
  • Bootloader standardization would help a lot
  • ARM System Ready looks interesting.
• Advice for young engineers

Discuss this episode at our community site.

In this episode, we had a great discussion with Drew about:

• Drew’s career – many interesting companies
• Toradex
  • manufacturers SOMs (System-on-Module)
  • started out providing WinCE solutions
• Torizon
  • opinionated stack
  • fully integration solution
  • container runtime – allows developers to deploy applications without knowing much about Linux
  • customize OS without doing Yocto builds
• Visual Studio Code plugin
  • simplifies management of Docker images, containers, cross compilation, remote debugging, etc.
• Torizon device side software is OSS
• SW update system
  • many options: Mendor, RAUC, SWUpdate, OSTree
  • Toradex uses OSTree
    • OSTree is file based for delta updates, where RAUC and SWUpdate are block based.
    • single partition
    • Git-like store where changes can be rolled back, etc.
    • read-only rootfs
  • Uptane is provides protection against attackers
• Greenboot – used to verify system is functioning properly
• Toradex’s upstream first policy
• Challenges in developing with Embedded Linux
  • drinking from the OSS firehose
  • understanding all the components
  • realistic expectations about how long this stuff takes to develop
  • regulations
• The future
  • immutable distros

Discuss this episode at our community site.

The Embedded Open Source Summit is a Linux Foundation event that covers embedded computing systems (mainly Linux and Zephyr). Listen to learn industry trends that may affect your product development efforts.

Discuss this episode at our community site.

In this espisode, we discuss what Yocto Dynamic Layers are, how they can help you manage changes for multiple layers, and how this helps you build an Embeded Linux Platform that you can scale accross time and products.

Documentation

See how we use them in the Yoe Distribution for an example of how you might use dynamic layers.

Another discussion

Discuss this episode at our community site.

In this episode, we discuss workflow ideas that can help you improve your developer productivity.

Outline:

• How to find the right people?
• How to accelerate the rate of development?
• How to be more efficient?
• How will AI impact me?
• How do we adapt to change?

Discuss this episode at our community site.

In this episode, we discuss technology trends and opportunities in 2024 that can help you develop better products.

Outline:

• Hardware
• Embedded Linux
• Application development

Discuss this episode at our community site.

In this episode, we discuss how Open Source software can help you add value to your products.

This topic is also covered in this blog post.

Discuss this episode at our community site.

In this episode, we discuss the latest features in the Yoe Distribution that can help you build products more efficiently using Yocto.

• New platforms:
  • Nvidia Jetson Orin Nano
  • VisionFive2 RISCV64 SBC
• Yoe Projects - a better way to configure your project
• Qt 6.6
• switch to LLD linker
• ptests can not be run inside Docker

Discuss this episode at our community site.

In this episode, we discuss the “living on main” philosophy so that you can track the latest software developments more effectively, reduce technical debt, and participate in the software projects you use.

Outline:

• What do we mean by living on main?
• Traditional view of stability
• Advantages
• Examples
• How to do it

Discuss this episode at our community site.

In this episode, Burkhard shares his experiences about using Qt and Yocto:

• focus on HMIs in industrial equipment
• Why use Yocto instead of Ubuntu for embedded devices
• QML vs Qt C++ widgets
• Qt vs Web platform
• Hexagonal architecture
• Tips for selecting a SOC/SOM
• CI/CD

Discuss this episode at our community site.

Outline:

• how we got started with Arch Linux
• features useful for developers
  • latest packages of everything
  • pacman is the fast, low-friction package manager
  • documentation is the best
  • containers can be used to issolate tools for older projects
• discussion on stability
• Yay AUR helper – we highly recommend this for managing AUR packages.

Discuss this episode at our community site.

• backstory
  • working on a project using freeRTOS on STM32H743
  • a lot of work integrating things like Ethernet/USB
  • code generation has tradeoffs
  • without one week, 1 engineer working part-time had Zephyr running with most drivers working
• Build
  • Kconfig (very granular)
  • Device Tree -> C headers
  • extensive use of Macros
  • no C++
• differences between other RTOS models
  • most MCU tooling takes RTOS, and MCU integrates and delivers
  • Zephyr does the opposite – they take MCU HAL, and then integrate and deliver directly to developers
• Support/Community
  • Discord
  • Github discussions
• Shell
  • is amazing
  • proper terminal with tab completion, proper backspace support, etc
  • keeps what you are typing at bottom of screen even if there are logging messages scrolling
  • list threads, memory used, %CPU, etc
  • Projects like Beagle Connect Freedom – they are piping shell over radio connection
• Logging
  • standard levels ERR, WRN, INF, DBG
  • easy to add a logging domain in any module
  • Macros automatically apply LOG_WRN() to current logging domain
  • can change log level of each domain at runtime in shell
• Tooling
  • well-integrated flashing
  • debugging uses the command line GDB
• Linux connections
• Performance
• challenges
  • configuration
  • tracing code through system calls
  • documentation is fairly good, but can be hard to find things
• opinion
  • The Zephyr project is a sustainable approach as MCUs become more complex

Discuss this episode at our community site.

• Would like to know a great way to prove your ideas and then sell them?
• The power of the demo
• Why it works
• what?
  • live demo
    • document camera
  • recording a video is effective – managers like video as they can more easily understand it
  • proposal document
• How to do it
  • you need to become a media producer
  • use OBS to record screen casts
  • the more you do it, the better you’ll become
  • KDENlive
  • OpenShot

Discuss this episode at our community site.

Show Notes:

• which do you find more inspiring – a stagnant pond covered in algae or a fast-flowing mountain stream?
• why should you share your work early and often?
• Two scenarios
  • everything done in private and then we try to integrate at the end
  • continuous stream of work done in a transparent way
    • can exist inside companies as well as OSS projects
  • stagnant pond vs fast flowing mountain stream
• why
  • builds trust
  • get feedback early
  • people can watch the work go by and optionally take a closer look if they are interested.
  • spreads knowledge
  • we do better work in public
  • injects energy into the team
  • no status meetings are required
• how do you do this?
  • work on a Git branch, rebase, squash commits, force push, delete, etc
  • do batches of work in a pull request
  • small commits/PRs – monster commits/PR are exhausting to review (at least daily)
  • stream of commit messages tell a story how you got from point A -> B
  • lead your work with documentation
• objections
  • My code is not perfect
  • I don’t want to bother people
  • It is only an experiment and may get redone anyway
  • I’m not comfortable showing my work/process

See also: TMPDIR handbook Discuss this episode at our community site.

How can you make your builds go faster? Some of the ideas we discuss in this episode:

• C/C++
  • the problem of headers
  • Clang CI tools
  • parallel builds
  • ccache/distc
  • linking technologies
• get a new workstation (the easiest way to speed up builds)
• Yocto
  • Yoe defaults to fast defaults where possible
  • sstate
  • Memory requirements per core – 4G RAM/Physical Core

Discuss this episode at our community site.

See also related blog article.

In this episode, we discuss the trajectory that technology takes and how understand this can help you make better technology predictions.

Discuss this episode at our community site.

In this episode, we discuss why you should consider a 64-bit processor for your embedded Linux project.

Discuss this episode at our community site.

In this episode, we are joined by Blake Miner to discuss databases.

Show notes:

• Introduction
  • Blake’s background, what type of work he does, company information, etc.
  • Data has substantial value
• What is a database?
  • General overview - store data, process it, and look it up later
  • Important that data stays intact in the event of a app/system crash, power loss, etc.
  • Important that conflicting concurrent changes are handled appropriately
  • What safety guarantees do I get? -> Transactions / ACID - Atomicity, Consistency, Isolation, Durability
    • atomicity -> abortability guarantee for a group of writes (i.e. upon failure)
    • consistency -> guarantee that certain (app-specific; sometimes database-specific) constraints are not violated
    • isolation -> describes how database handles concurrent edits of the same data. Serializable is the strongest guarantee. Snapshot isolation is very common.
    • durability -> storage guarantee (i.e. upon commit, data has fsync‘ed to disk). Study: SSDs get 1 bad block in first 4 years; disaster could wipe out an entire data center; nothing is perfect.
  • Storage / lookup: Data models / data structures
  • Derived data; caching
  • Concurrency; consistency & isolation
• Reactivity/Realtime
  • tradeoffs between reacting to DB changes vs using a message bus
  • streaming platforms such as NATS Jetstream and Kafka
• SQL
  • Tables and rows -> array of structs
  • SQL -> Declarative query language (query engine determines implementation details at runtime)
  • B-tree Indexes
• NoSQL Databases
  • “NoSQL” -> a marketing term
• Redis
  • Data structure store
  • In-memory vs. disk-based
• Embedded databases (i.e. API vs. commands over TCP)
• Designing Data-Intensive Applications by Martin Kleppmann. Blake recommends this book.

Discuss this episode at our community site.

Show notes:

• difference between a product and platform
• platform is a collection of modules and tools
• a platform is extensible, programmable, consists of reusable pieces and components
• desirable qualities in a platform and various considerations
  • a platform is a living being to some extent
  • availability
  • stability
  • performance
  • how easy is it to fix when things break
  • adaptability
• the iceberg analogy – most of your product is invisible, but this can cause problems
• how do you select the right technology for your platform?
  • important not have bias
  • products are short-lived, where platforms last a long time, so important to make the right choices in your platform.
  • it is good to depend on standards to avoid lock-in to one tool/technology
  • the wrong solutions do not scale
  • have a network of experts you can reach out to and get the information you need
  • knowing who to ask is the superpower in this age
• why you need some level of control over your platform
  • damage control: solve problems when they arise
  • moving things forward: can it be modified as new requirements come up
• building platforms for reuse
  • build systems are important
  • automation
  • continuous integration
• The Yoe Distribution and the Simple IoT project are examples of platforms that are re-usable and flexible, and applicable for a wide range of projects
• recomposable platforms scale not just vertically, but horizontally, which is the real power of them
• a lot of up-front discipline goes into this
• you create a platform not only for others, but yourself
  • you respect the APIs in the same way you expect others to respect them
  • APIs as a contract become very important
• Most people can track product costs very well. Platform costs are harder to track and are an investment in the future
  • example of an embedded Linux platform that goes into a product that lives for many years. A lot of work is required upfront to get the base system running, but then you can build on it for years.
  • A more constrained platform like a MCU + RTOS tends to be not as extensible and more limited to a product.
• Two kinds of platforms
  • Transaction platforms: facebook, twitter, etc
  • Innovation platforms: what we’ve been talking about
• personal platform
  • write things down
  • when helping someone, instead of emailing or messaging the solution, I write down the solution in some type of long lived documentation, and then share that documentation with them.
• do you own your platform?
  • owning your platform is more of a mindset rather than an rigid absolute
    • are you willing to learn and own the details of your platform
  • with OSS we not only use it, but we also have the option to be part of it

Discuss this episode at our community site.

Why are Go applications so reliable?

Available on your favorite podcast platform.

Discuss this episode at our community site.

Show notes:

• what does your day to day development look like
• recent platforms developed with Yoe
• why we mirror repositories (note, these are not forks)
• we use Yoe to test combinations of things
• Yoe testing strategy and tools
• master branch is usually stable
• how we generate the changelog and why it might be useful for any Yocto developer

Available on your favorite podcast platform.

Discuss this episode at our community site.

Show notes:

• Andrew has been involved in OSS for 2 decades
• likes packaged software – started by packaging software for SUSE for his own use
• too many people are concerned about what others will think of their work
• you keep doing OSS for yourself.
• successful community requires a safe, open, collaborative environment
• accept the fact you can’t please everyone. Once you try to please everyone, you please no one.
• marketing is the Achilles heel of many projects
• events are an easy way to market projects
• BSD
  • very nice community, and BSP projects seem to be thriving
  • collaboration between commercial entities is better than Linux – which may seem seem a bit surprising considering BSD is licensed with a permissive license
  • used a lot in education – great learning platform
• tips
  • read the documentation
  • build up a portfolio (Github, etc)
  • try it all out
  • don’t be afraid to ask
  • have fun
  • operating systems/distros are a good way to get exposed to a lot of different technologies – languages, compilers, projects, etc.

Available on your favorite podcast platform.

Discuss this episode at our community site.

• What is documentation
• Benefits of documentation
• Documentation is critical for scaling, collaboration, and distributed teams
• How documentation benefits ourselves
• Lesli Lamport’s thoughts: To think, you have to write. If you’re thinking without writing, you only think you’re thinking.
  • https://www.microsoft.com/en-us/research/wp-content/uploads/2016/07/leslie_lamport.pdf
• Code should not only be created for the compiler, but more importantly for other people
• Importance of idioms, automatic code formatting, and code linters
• Documentation should live close to the code (embedded in the code, or Markdown in the same repository)
• Benefits of Markdown
• Trade-offs between Markdown and other formats like Word
• How to optimize documentation for collaboration
• Biggest problem with documentation is that most of it gets stale and how to prevent this
• Documentation can be a platform for thinking about a design
• Discussion should happen around documentation, not the other way around
• Use CI tools to publish your documentation
• Useful tools: draw.io and Typora
• The futility of emailing documents
• Storing documents in Git and using pull requests (PRs) is a hugely beneficial for collaboration
• Cal Newport’s new book: A world without email
  • https://www.calnewport.com/books/a-world-without-email/
• Gitlab’s handbook has a lot of good ideas
  • https://about.gitlab.com/handbook/
• The more experienced you are, the more should you document
• Tools for generating documentation web sites
  • Docusaurus
  • Docsy (Hugo)
  • Pandoc
  • mdBook
  • mkdocs
  • Zola
    • book theme
  • GitBook
• Example of collecting documentation from multiple projects and creating a documentation site using Zola: https://github.com/simpleiot/docs.simpleiot.org
• The TMPDIR handbook:
  • https://gitlab.com/tmpdir/handbook
• Jupyter Notebook
  • https://jupyter.org/
• Treat documents as code, and code as documents!

Available on your favorite podcast platform.

Discuss this episode at our community site.

• what is a Yocto BSP
• who are a BSP’s users
• the purpose of a BSP
• examples of good BSPs
• importance of keeping BSPs and Distros separate
• dynamic layers
• issues with forking major components like GStreamer
• and many other aspects of BSPs

Available on your favorite podcast platform.

Discuss this episode at our community site.

• does Elm really live up to the expectation of no run time exceptions?
• Elm tooling
• elm-ui
• how Elm interacts with Javascript
• how Elm compares to other front end technologies. As a follow up we documented bundle size for various frameworks.
• why Elm is a really good option for those of us who are not front end experts.

Available on your favorite podcast platform.

Bonus: What are your favorite things about Elm?

Discuss this episode at our community site.

• review of various Linux update technologies
• discussion of experiments using swupdate
• description of the Yoe updater
• design ideas behind the Yoe updater
• recent work done on the Yoe updater to make it more generic
• Yoe handles installation, system initialization as well as update - this is very critical
• designed to support products with long life cycles where things may change (partition layout, etc.)
• how to add Yoe updater support to a new platform
• what pieces of the system does the Yoe updater touch
• how the Yoe updater handles rootfs corruption
• why system initialization is important for reliable systems
• why system initialization make sense in an initramfs
• keep it simple is really the mantra
• how the Yoe updater helps developers streamline their testing process by removing friction
• future plans of managing updates using Simple IoT

See also the documentation and implementation.

Available on your favorite podcast platform.

Discuss this episode at our community site.

• hardware options for implementing Embedded Linux systems (SOM, SBC, full custom)
• why we selected the Odroid-C2 for this project
• review of the BSP support for the Odroid-C2
• make sure you are worked with supported technology
• description of what it takes to use a watchdog to protect the boot process
• discussions on the trade-offs with the update architecture (we used a dual rootfs method on this project)
• trade-offs with implementing a read-only rootfs
• application architecture
  • written in Go
  • local display using a Qt WebEngine to implement a full screen browser on LCD
  • used InfluxDB for storing time series data
  • used Grafana to view engineering data
• how we do builds, release/changelog, and versioning
• options for browser implementations

Available on your favorite podcast platform.

Discuss this episode at our community site.

Discuss this episode at our community site.

Links:

• Thomas’s page on the Bootlin web site
• Buildroot

Discuss this episode at our community site.

Available on your favorite podcast platform.

Discuss this episode at our community site.

Discuss this episode at our community site.

Available on your favorite podcast platform.

Discuss this episode at our community site.

Discuss this episode at our community site.

Available on your favorite podcast platform.

Discuss this episode at our community site.

Discuss this episode at our community site.

Links:

• BEC Systems
• Yoe Distro
• Simple IoT
• Iterate hardware like software

Available on your favorite podcast platform.

Discuss this episode at our community site.