User Tools

Site Tools


civilinfrastructureplatform:cip_comparison_report

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_comparison_report [2019/04/09 09:07]
daniel.sangorrin fix some lists
civilinfrastructureplatform:cip_comparison_report [2019/05/14 02:12] (current)
daniel.sangorrin
Line 1: Line 1:
 ====== CIP Comparison report ====== ====== CIP Comparison report ======
  
-This document compares ​multiple ​software update tools in order to implement the CIP software updates architecture. We compared ​them from different points of view such as:+This document compares software update tools that are suitable ​to implement the [[civilinfrastructureplatform:​cip_software_updates_architecture|CIP software updates architecture]]. For a thorough comparison of open source software update tools please check the [[cip_comparison_report#​comparison_references|Comparison references]] section below. We compared ​the tools from different points of view such as:
   - network and storage efficiency   - network and storage efficiency
-  - ability to integrate with Debian-based build tools (Deby, ISAR, Debos)+  - ability to integrate with Debian-based build tools used in CIP Core (e.g.: Deby, ISAR)
   - community and member'​s expertise   - community and member'​s expertise
-  - support local and network ​updates+  - support ​for local and remote ​updates
   - security support (encryption,​ digital certificates,​ integrity)   - security support (encryption,​ digital certificates,​ integrity)
   - extendable with scripts   - extendable with scripts
Line 36: Line 36:
     * good community: Stephano, Denx(u-boot)     * good community: Stephano, Denx(u-boot)
     * CIP members experience (Siemens)     * CIP members experience (Siemens)
-    * supports yocto (meta-swupdate) and debian ​(on-going)+    * supports yocto (meta-swupdate) and Debian ​(on-going: waiting for libubootenv replacement)
     * low bandwidth (librsync deltas)     * low bandwidth (librsync deltas)
     * u-boot interface     * u-boot interface
Line 42: Line 42:
   * Bad points   * Bad points
     * hard to manage updates from v1 to v5 directly     * hard to manage updates from v1 to v5 directly
-    * depends on libubootenv which needs to be rebuilt for each target.+    * depends on a u-boot library that needs to be rebuilt for each target ​(on-going: replacement ​ https://​github.com/​sbabic/​libubootenv). 
 +      * Building SWUpdate 2019.04 with [[https://​github.com/​Kynetics/​meta-updatefactory/​commit/​c4c25b21d3ed4ae15f9716769c2644953e8eedb3#​diff-6a1eb0b91b36c4c636f9fa5b23f5514bR53|CONFIG_UBOOT_NEWAPI]] will make use of the standalone libubootenv library, and will read default initial environment from "/​etc/​u-boot-initial-env"​. 
 RAUC + Casync (command) RAUC + Casync (command)
   * https://​github.com/​rauc/​rauc   * https://​github.com/​rauc/​rauc
civilinfrastructureplatform/cip_comparison_report.1554800856.txt.gz · Last modified: 2019/04/09 09:07 by daniel.sangorrin