3,260
edits
Changes
m
=== Flash_self === This configuration is conceived for standalone operation. Both the kernel and the root file system are retrieved from Flash (see section 2.4). Once U-Boot has transferred the control to Linux, its job is completed. From now on Linux kernel has the control of the hardware. At the end of Linux boot process, the user can interact with the system with the typical Unix-like shell through the same serial connection used for U-Boot. To run this configuration just issue the command run flash_self. Ethernet interface will be enabled by default. To disable it, just remove addip variable from the flash_self variable. === Net_nfs === This configuration is very helpful during the software development (both for kernel and applications). The kernel image is downloaded via TFTP while the root file system is remotely mounted via NFS from the host. It is assumed that the development host:* is connected with DivaEVB through an Ethernet LAN* exports the directory containing the root file system for the Diva system through the NFS server* runs a TFTP server.* has 192.168.0.23 as IP address (netmask 255.255.255.0).If the host system does not match this configuration, it's required to change the necessary u-boot variables and store them permanently with the <code>saveenv</code> command. For example, let's say the server has different IP address, eg 192.168.0.72:<pre>=> setenv serverip 192.168.0.72 => saveenv Saving Environment to NAND... Erasing Nand... Erasing at 0x0 -- 2490368% complete. Writing to Nand... done =></pre> To run this configuration, just issue the command following command:<pre>run net_nfs</pre> === Automatic boot === If you wish Diva system to automatically boot with one of the above configurations, just set up and store the bootcmd variable. For example, for the flash_self configuration, enter the following commands:<pre>=> setenv setenv bootcmd $(flash_self)=> setenv serverip 192.168.0.72 => saveenv Saving Environment to NAND... Erasing Nand... Erasing at 0x0 -- 2490368% complete. Writing to Nand... done =></pre>Next time the system boots, U-Boot will wait for three seconds (to stop the wait just press any key in the console) before executing the commands stored in the bootcmd variable. This time can be changed by setting the bootdelay variable. Generally speaking the whole boot process can be further and heavily customized. For more details please Please refer to the doc/README.autoboot file in the U-Boot sources[[Booting_Linux_Kernel]] article.
→Boot configurations
== Boot configurations ==
== Memory Map ==
