Debian and Yocto Project Based Long-Term Maintenance Approaches for Embedded Products
Talkat Open Source Summit Europe + Embedded Linux Conference Europe 2019 · on Monday, 2019-10-28· at 11:30· Forum 2·
summary
Debian-based CIP core plus a Yocto-driven ISAR workflow targets 10+ years of security and reproducible updates, producing bootable images and SDKs tested by LAVA and pushed as artifacts to S3. Two flavors exist: a binary-compatible generic profile (Debian packages, installable at runtime) and a source-driven tiny profile (meta-debian + Poky, extreme size reduction). CIP currently validates about six hardware targets, uses bitbake/Yocto and ISAR, and reports image builds in “few 10 minutes” vs source builds that take hours.
AI-written summary · about
chapters (15)
- 0:00Start
- 1:06Agenda
- 1:36Requirements in Industrial Product Development
- 4:21CIP is the solution
- 7:41CIP Core: Position in CIP Projects
- 8:59CIP Core: Implementation
- 10:28Deby (meta-debian)
- 12:00Deby: How it works
- 14:15Image Generation Sequence of Isar
- 15:46Example: Building Images for BeagleBone Black
- 16:24Preferred Use Cases
- 18:49CIP Core: Testing Architecture
- 19:51Building Products on Top of CIP Core
- 21:55Future Plans for CIP Core Implementation
- 23:51Summary
related talks
41mDebian & Yocto: State of the Art
34mDebian or Yocto Project? Which is the best for your Embedded Linux project?
41mEasily Generating Debian-Based Embedded Systems
49mDeby - Reproducible and Maintainable Embedded Linux Environment with Poky
34mDelivering Security Fixes Continuously Into Your Embedded Linux
36mLessons Learned: Migrating a Production Platform to Yocto
40mWhy the Yocto Project for My IoT Project
44mDebian for Embedded Systems: Best Practices