Booting from network means loading the kernel and device-tree over TFTP. The bootloader itself must already be loaded from any other boot device available.
Procedure:
Development Host Preparations :-
On the development host, a TFTP server must be installed and configured. The following tools will be needed to boot the Kernel from Ethernet:
A TFTP server and
An optional tool for starting/stopping a service (xinetd).
Following packages need to be install in the host PC.Before installing the below packages, please check your internet(Ethernet Cable) connection.
After the installation, there are two ways to configure the TFTP server :
As a standalone daemon
Controlled and handled by xinetd
First, create a directory to store the TFTP files :
host$sudomkdir/tftpboot
host$sudochmod-R777/tftpboot
host$sudochown-Rnobody/tftpboot## This command is changing the ownership of the "/tftpboot" directory and everything underneath it to the user or group specified as "nobody."
Then copy your BSP image files to this directory.You also need to configure a static IP address for the appropriate interface. The default IP address of the PHYTEC evaluation boards is 192.168.3.11. So setting 192.168.3.10 with netmask 255.255.255.0 as a host address is a good choice.
We also recommend erasing the environment of the old barebox. Otherwise, the new barebox will use the old environment.
bootloader$erase/dev/nand0.barebox-environment.bb
Aftererasingtheenvironment,youhavetoresetyourboard.Otherwise,the barebox willstillusetheoldenvironment.bootloader$reset#Again stop it in bootloader level
#Again bootloader$ifupeth0
Update the Kernel and devicetree :
Create UBI volumes for Linux kernel, oftree, and root filesystem in NAND :