Changes

Jump to: navigation, search

Deploying Embedded Linux Systems

560 bytes added, 12:40, 29 May 2019
no edit summary
Please note that init implementations can differ: Busybox offers its own version while other distributions, like Angstrom, can provide the classic System V version. More modern distros, like Ubuntu, implements Upstart, a complete replacement of the init daemon. For further information on the init process, please visit [http://www.yolinux.com/TUTORIALS/LinuxTutorialInitProcess.html this page].
 
= Non-volatile memories partitioning scheme =
In general, many different schemes can be implemented. Cost, reliability, speed are just some of the parameters to be considered when designing the partitioning scheme. [[Standalone_boot_(BELK/BXELK)|This article]] shows two quite different schemes on the same platform, for example.
 
= Startup sequence =
Nowadays, a large number of newly designed embedded systems are used in Internet-connected products. As such, these systems have to face severe issues in terms of cybersecurity. This topic is huge and it is obviously beyond the scope of this document. It is worth remembering, however, that modern SOCs provide a rich set of native functionalities that address this issue. For instance, see [[XUELK-WP-001:_Secure_boot_on_iMX6UL|this page]] or [[BELK-TN-001:_Real-timeness,_system_integrity_and_TrustZone%C2%AE_technology_on_AMP_configuration|this technical note]].
=Licensing=
It is known that a GNU/Linux system is based on a large amount of open source software. As Consequently, the manufacturers of a product embedding suchsoftware must deal with the open source license compliance. This topic is beyond the scope of this document, but a couple of links are provided anyway:*[[https://elinux.org/Legal_Issues|This article] provides an overview of license-related legal issues*Yocto build system generates automatically a manifest file to make the compliance management easier. For more details, please refer to [[https://www.yoctoproject.org/docs/1.8/dev-manual/dev-manual.html#maintaining-open-source-license-compliance-during-your-products-lifecycle|this link]]
https://elinux.org/Legal_Issues
=Misc=
4,650
edits

Navigation menu