Bureaucrats, dave_user, Administrators
8,226
edits
Changes
→bootscript
** Retrieve binary images (i.e. Linux kernel) via TFTP protocol
** Mount the development root file system via NFS protocol. This root file system is physically in the file system of the host machine as depicted [[Deploying_Embedded_Linux_Systems#The_development_environment|here]].
* deployment: the goal of this stage is to configure the target for normal operation, that is out of the development environment. A target root file system - optimized system–optimized in terms of memory footprint - is footprint–is used. This root file system is stored on onto the target's non-volatile memory.
To implement this workflow, the MVM provides
===Building user applications against a specific SDK===
About C/C++ application development and debugging, please refer to [[Debugging_with_Eclipse_(MVM)|this page]].
===Misc===
The MVM may include additional files used for other useful purposes. The following sections detail the usage of such files.
====bootscript====
U-Boot provides flexible mechanisms to support different forms of scripting. One of the most used to automate complex actions at start-up is based on the use of script images.
Most of DAVE Embedded Systems' Linux kits provide a ready-to-use microSD card that allows the target to boot in standalone mode. This means that all the required images (U-Boot, Linux kernel, device tree blob, etc.) for a complete boot are stored in the card itself.
This card makes use of a script image to do this. This image is usually a file named <code>boot.scr</code>. U-Boot provided along with DAVE Embedded Systems' Linux kits implements several customizations. One of these is tailored default environment. This environment is defined to execute <code>boot.scr</code> script image on start-up.
[[File: Bootscript_execution.png | 400px]]
This script image is in turn generated from a source file that is stored in the <code>/home/dvdk/<target></code> directory of the MVM and that is named <code>bootscript.txt</code>. For instance, [[Axel_Embedded_Linux_Kit_(XELK)#Binary_images_on_SD_card|this section]] shows how the script image is generated for the XELK kit.
For more details, please refer to the following links:
*https://www.denx.de/wiki/view/DULG/UBootScripts
*https://www.denx.de/wiki/view/DULG/UBootCmdGroupExec
===Related links===
*[[Yocto build system FAQs]]