Ingredients of a System Image: Difference between revisions

From Wiki-DB
Jump to navigationJump to search
(Created page with "{| class="wikitable" | style="width: 100%; color: #000000; background: #FFFFFF;" valign="top" | !<tt>Image Component </tt> !<tt>Required </tt> !<tt>Recommended </tt> !<tt>Note</t...")
 
No edit summary
Line 1: Line 1:
Our DHCOM computer on module units are supplied initially programmed with the bootloader U-Boot. We offer pre-programming with the firmware image for the delivery in the series. The following table indicates which components therefor necessarily have to be already provided by you and which are optional depending on the situation.
== Linux ==
{| class="wikitable" | style="width: 100%; color: #000000; background: #FFFFFF;" valign="top" |
{| class="wikitable" | style="width: 100%; color: #000000; background: #FFFFFF;" valign="top" |
!<tt>Image Component </tt>
!<tt>Image Component </tt>

Revision as of 09:07, 16 March 2016

Our DHCOM computer on module units are supplied initially programmed with the bootloader U-Boot. We offer pre-programming with the firmware image for the delivery in the series. The following table indicates which components therefor necessarily have to be already provided by you and which are optional depending on the situation.

Linux

Image Component Required Recommended Note
Bootloader U-Boot No No In the most cases there are no project specific features in the bootloader. If you do not provide a customized bootloader we at DH electronics assume it is ok to use our latest version with the best hardware support.
U-Boot Environment No Yes If your project does not need any special variables or kernel arguments we use our latest standard bootloader u-boot environment. A quick change during the development can be missed likely. We recommend to provide your "printenv" output.
Settings Yes Yes
Splash Bitmap No Yes
uLinuxEnv.txt No Yes Please refer to "U-Boot Environment". uLinuxEnv.txt is a enhancement of the U-Boot Environment.
Linux Kernel Yes Yes
Linux Devicetree Yes Yes
Linux Rootfilesystem Yes Yes
Automatic Prog. Images The following components are used to program the image. They are not programmed to the target.
Update Kernel No Yes
Visualization Bitmaps <br\>- progress.bmp<br\>- error.bmp<br\>- done.bmp No Yes
DHupdate.ini No Yes