Bureaucrats, dave_user, Administrators
8,160
edits
Changes
→Target setup and first boot
[[File:DIVELK-NOR.png|thumb|center|400px|NOR flash default partitioning]]
{{ImportantMessage|text=The DIVELK bootable microSD card delivered along with the kit is set up to do a full bootstrap sequence. For more details, please refer to [[Working_with_the_Yocto_build_system#bootscript|this section]].}}
By default, U-Boot is configured to retrieve Linux kernel image stored in the microSD card [1]. In turn, Linux kernel shall mount root file system from the <code>mmcblk0p2</code> partition of the [[#DIVELK microSD Layout|microSD card itself]]. At the end of boot process, Linux shell shall be available on the serial console.
During the development stage, the target is usually connected via Ethernet LAN to the host machine and is configured to:
*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]]. An exmaple example of NFS ''Bridge mode'' configuration for DIVELK can be found [[Booting_the_system_via_NFS_(DIVELK) | here]]
In DAVE Embedded Systems development kits, this configuration is generally denoted as <code>net_nfs</code>. U-Boot bootloader supports this configuration. Some U-Boot environment variables are needed to set it up. They are detailed [[Booting_Linux_Kernel#Configuration_net_nfs|here]].
For more details about TFTP and NFS servers on host side, please refer to this [[Setting_up_tftp_and_nfs|page]].
===Target configuration for standalone boot===
Please refer to [[Standalone_boot_(DIVELK)|this page]].
