User Tools

Site Tools


civilinfrastructureplatform:cip-core

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
civilinfrastructureplatform:cip-core [2019/02/05 02:43]
daniel.sangorrin tiny vs generic info
civilinfrastructureplatform:cip-core [2020/07/29 01:10] (current)
daniel.sangorrin update to the current situation
Line 1: Line 1:
 ====== CIP Core project ====== ====== CIP Core project ======
 +
 +===== Regular meetings =====
 +
 +[[https://​wiki.linuxfoundation.org/​civilinfrastructureplatform/​cip-core-meetings|CIP core meetings]] ​
  
 ===== Overview ===== ===== Overview =====
  
-The Civil Infrastructure Platform (CIP) project aims to provide an open source base layer (OSBL) for embedded systems that require super long-term ​maintenance ​(SLTS). ​The OSBL consists ​of the super long-term support (SLTS) ​kernel, and the CIP Core packages. ​The CIP core packages are a set of industrial grade core open source ​software components and tools. The CIP Core project aims to implement reference file systems ​that use the CIP Core packages ​and can be tested on reference hardware.+The Civil Infrastructure Platform (CIP) project aims to provide an open-source base layer (OSBL) for embedded systems that require super long-term ​support ​(SLTS). OSBL is composed ​of the 
 +[[https://​wiki.linuxfoundation.org/​civilinfrastructureplatform/​cipkernelmaintenance|CIP ​kernel]] source code, and the CIP Core source ​packages. CIP Core source ​packages are a list of Debian Long Term Support (LTS) source ​packages ​that members of the CIP project consider important ​and want to [[https://​www.freexian.com/​services/​debian-lts.html|sponsor]].
  
-{{:civilinfrastructureplatform:​whole-picture.png}}+CIP core has two profiles: 
 +  * The tiny profile is built from Debian source code and is useful for devices with storage restrictions,​ extreme performance and flexibility requirements,​ and low-complexity applications.  
 +  * The generic profile is built from Debian binary packages and covers devices that require more functionality,​ have less performance and flexibility requirements,​ and more storage.
  
-It is not decided yet which components will be part of the final CIP Core packagesHoweverthe current candidates ​for the initial component set are show in the figure below.+The CIP Core project provides example filesystem images using available build and image generation toolsCurrentlywe are using [[https://​github.com/​meta-debian/​|meta-debian]] ​for Deby, and [[https://​github.com/​ilbers/​isar|ISAR]] for isar-cip-core. However, we are open to the submission of new reference implementations using other build tools (e.g. Debos).  
 +  * [[https://​gitlab.com/​cip-project/​cip-core/​deby|Deby]]:​ tiny profile 
 +  * [[https://​gitlab.com/​cip-project/​cip-core/​isar-cip-core|isar-cip-core]]:​ generic profile
  
-{{:civilinfrastructureplatform:​candidate-core-packages.png}} +The main goals of CIP Core are: 
- +  * Contribute to the sponsoring and testing of Debian LTS 
-The CIP Core project will create its file systems ​from Debian LTS sources and/or binaries and the CIP kernelIn particular, ​CIP Core defines 2 profilestiny and genericThe tiny profile aims at creating file system images that are small in size and very customizedCurrently the tiny profile is implemented with Deby (yocto/OE + meta-debian) which builds the file system image from Debian source code. In contrast, the generic profile aims at middle to high-end embedded systems not constrained by size and requiring less customization. Currently the generic profile is implemented with ISAR (bitbake + Debian binaries).+  * Serve as a reference base from which users can develop their OS images 
 +  * Serve as a reference implementation on important topics such as software updates, security standards, or real-time
 +  * Provide ​file systems ​for testing on the [[https://wiki.linuxfoundation.org/​civilinfrastructureplatform/​ciptesting/​cipreferencehardware|CIP reference hardware]] boards using [[https://lava.ciplatform.org/|LAVA]].
  
 +{{:​civilinfrastructureplatform:​whole-picture.png}}
 {{:​civilinfrastructureplatform:​minimum-base-system.png}} {{:​civilinfrastructureplatform:​minimum-base-system.png}}
  
-The source code is currently hosted [[https://​gitlab.com/​cip-project/​cip-core/​|here]].+===== Package list =====
  
-===== CIP Tiny profile Deby-based images =====+The list of CIP Core packages and the process to add or remove packages is described [[https://​gitlab.com/​cip-project/​cip-core/​cip-pkglist|here]].
  
-[[http://elinux.org/images/9/96/​ELCE2016_Hayashi_Deby.pdf|Deby]] is a reference distribution ​built with poky and [[https://​github.com/​meta-debian/​meta-debian|meta-debian]],​ a layer for the poky build system that allows cross-building file system images from Debian source packages.+===== Deby ===== 
 + 
 +[[https://gitlab.com/cip-project/cip-core/deby|Deby]] is built with poky and [[https://​github.com/​meta-debian/​meta-debian|meta-debian]],​ a layer for the poky build system that allows cross-building file system images from Debian source packages ​(see [[http://​elinux.org/​images/​9/​96/​ELCE2016_Hayashi_Deby.pdf|Deby slides pdf]]). Deby does not use Yocto/OE source code.
  
 {{:​civilinfrastructureplatform:​deby.png}} {{:​civilinfrastructureplatform:​deby.png}}
  
-The CIP Core project provides reference Deby file systems images that include the CIP Core packages and can be tested on the following reference hardware.  +==== ISAR-CIP-Core ​====
- +
-  * Renesas RZ/G1M (iwg20m) +
-  * BeagleBone Black +
-  * QEMU x86_64 +
-  * Cyclone-V (experimental) +
- +
-To build the images you need to follow the README for each board. For example, to build CIP Core for the Renesas iwg20m board just follow the instructions in  [[https://​gitlab.com/​cip-project/​cip-core/​deby/​blob/​master/​poky/​meta-cip-iwg20m/​README.IWG20M.txt|README.IWG20M.txt]];​ and to build CIP Core for the Beaglebone back you can follow the instructions in [[https://​gitlab.com/​cip-project/​cip-core/​deby/​blob/​master/​poky/​meta-cip-bbb/​README.BBB.txt|README.BBB.txt]]. Also check the [[https://​wiki.linuxfoundation.org/​civilinfrastructureplatform/​cip-core-quickstart|Quickstart]] guide. +
- +
-===== CIP Generic profile ​ISAR-based images =====+
  
-The CIP Core project also plans to provide ​reference ​file systems built with ISAR. Currently, the ISAR implementation is located ​[[https://gitlab.com/cip-playground/isar-cip-core|here]].+[[https://​gitlab.com/​cip-project/​cip-core/​isar-cip-core|ISAR-CIP-Core]] is a reference ​implementation of the generic profile and uses [[https://​github.com/​ilbers/​isar|ISAR]]. ISAR uses bitbake to generate the filesystem image by reusing Debian binaries and rebuilding packages that need modifications for the target board (see [[https://events19.linuxfoundation.org/wp-content/​uploads/​2018/​07/isar-ossj2019-7.pdf|ISAR slides pdf]]).
  
 {{:​civilinfrastructureplatform:​isar-elbe.png}} {{:​civilinfrastructureplatform:​isar-elbe.png}}
  
civilinfrastructureplatform/cip-core.1549334597.txt.gz · Last modified: 2019/02/05 02:43 by daniel.sangorrin