Buildroot: Flexible Building of a Custom Embedded System

Buildroot: Flexible Building of a Custom Embedded System

Buildroot: flexible building of a custom embedded system © 2012 Essensium N.V. Parts © Thomas Petazzoni, Free Electrons This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License http://mind.be/content/Presentation_Buildroot-Open-Mobile.pdf Is the device really hackable? ?? How easily can I install modified software? Buildroot for Open Mobile Arnout Vandecappelle Buildroot: flexible building of a custom embedded system © 2012 Essensium N.V. Parts © Thomas Petazzoni, Free Electrons This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License http://mind.be/content/Presentation_Buildroot-Open-Mobile.pdfBuildroot for Open Mobile Overview 1 Buildroot for the device hacker 2 Buildroot for the device “vendor” 3 What's missing Buildroot for Open Mobile Arnout Vandecappelle Buildroot builds a complete system Buildroot builds: . Cross-compiling toolchain . Packages . Root filesystem image (ext2, jffs2, ubi, ...) . Kernel image . Bootloader (u-boot, barebox, syslinux, ...) Configuration system (Kconfig) Simple make-based system No run-time packaging system Small & medium-sized embedded devices Stable releases published every three months Active user/developer community Buildroot for Open Mobile Arnout Vandecappelle Workflow for Open Mobile device user (1/3) Neuros buildroot Makefiles Kconfigs patches make neuros_defconfig; make xconfig Buildroot for Open Mobile Arnout Vandecappelle Workflow for Open Mobile device user (2/3) compiler gnu.org C library kernel.org debugger sf.net tools boot loader make kernel gcc μClibc packages linux skeleton busybox init mtd-utils root fs image Buildroot for Open Mobile Arnout Vandecappelle Workflow for Open Mobile device user (3/3) Create upgrade image Upload to target Buildroot for Open Mobile Arnout Vandecappelle Workflow for Open Mobile device vendor (1/3) Makefiles board Kconfigs kernel device patches patches applications make xconfig; make Buildroot for Open Mobile Arnout Vandecappelle Workflow for Open Mobile device vendor (2/3) /etc/init.d/S80startapp Neuros /etc/network/interfaces buildroot Root Makefiles filesystem Kconfigs skeleton make linux_saveconfig; patches make savedefconfig Buildroot for Open Mobile Arnout Vandecappelle Workflow for Open Mobile device vendor (3/3) Create production image Upload to target Buildroot for Open Mobile Arnout Vandecappelle What is missing in buildroot No package manager (or appstore) . Doesn't generate packages to install individually (can create a package manager, though) . But can easily regenerate device firmware . Actually gives you more control No post-processing of images . E.g. write images to flash using JTAG . Device vendor should produce script to prepare upgrade image . Is very device-specific No standardized upgrade system . because there is no package manager . Somewhat device specific . See my talk in the Embedded devroom Buildroot for Open Mobile Arnout Vandecappelle Similar projects OpenWRT . focused on routers . does use package manager . UCI for configuration data PTXdist . very similar in goals and results . fully bash-based . slightly smaller community OpenEmbedded + derivatives . very popular . IMO more difficult to customize . slow :-) Buildroot for Open Mobile Arnout Vandecappelle Hacking the device is easy! Buildroot for Open Mobile Arnout Vandecappelle www.mind.be www.essensium.com Essensium NV Mind - Embedded Software Division Gaston Geenslaan 9, B-3001 Leuven Tel : +32 16-28 65 00 Fax : +32 16-28 65 01 email : [email protected] Buildroot for Open Mobile Arnout Vandecappelle.

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    16 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us