Bureaucrats, dave_user, Administrators
8,154
edits
Changes
→Target configuration for the development stage (net_nfs)
This page describes how to quickly start working with the BELK/BXELK kit. The following paragraphs will guide you through the setup and installation procedures.
===Kit registration===
{{ImportantMessage|text='''Customers are strongly recommended to register their kits'''. Registration grants access to reserved material such as source code and additional documentation.}}
===Target setup and first boot===
===Target configuration for the development stage (<code>net_nfs</code>)===
{{ImportantMessage|text=The default BELK/BXELK Virtual Machine network configuration is using NAT: this allows to accessing external network (i.e. Internet) using the host computer's networking connection.
For software development using <code>net_nfs</code> with tftp/nfs protocols, please configure your VM network interface in ''Bridge mode'' (see below)}}
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 example of ''Bridge mode'' configuration 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.
===Target configuration for standalone boot===
Please refer to [[Standalone_boot_(BELK/BXELK)|this page]].
===Recovery procedure===
In case the target is not able to boot from NOR flash for any reason, this [[System_boot_and_recovery_via_microSD_card_(BELK/BXELK)|recovery procedure]] can be use to boot from microSD card.
