U-Boot
ATCA-F140 Series Installation and Use (6806800M67S)
115
5.3.2
Configuring U-Boot to Boot from RAM Disk
If the Linux kernel and root file system are available as RAM disk image, you may want to
boot from that RAM disk.
This procedure assumes that the U-Boot command
ramboot
has been defined and that the
RAM disk image is stored on an external TFTP server that is connected to the ATCA-F140.
During each boot process, the image is downloaded from the TFTP server into the main
memory of the blade. The external TFTP server must be connected using the ATCA-F140
face plate connector "ETH5", which is the Ethernet management interface. Any other
interfaces, such as the base or fabric interfaces, are not yet functional at this stage of the
boot phase, as the corresponding drivers are not initialized yet.
1.
Specify the IP address of the ATCA-F140 and the TFTP server that contains the RAM
disk:
setenv ipaddr <IP address of ATCA-F140>
setenv serverip <IP address of TFTP server>
2.
Depending on your network configuration, you may have to specify a gateway IP
address and a netmask. Use the following commands:
setenv gatewayip <gateway IP>
setenv netmask <netmask>
3.
Specify the name of the RAM disk image file:
setenv ramdiskfile <filename>
setenv blobfile <dtb file name>
4.
Configure U-Boot to boot from RAM disk:
setenv bootcmd $ramboot
5.
Specify the name of the kernel image file:
setenv bootfile <filename>
6.
Enter
saveenv
, and then enter
boot.
5.3.3
Configuring U-Boot to Boot from Flash
The blade provides two redundant boot flashes which contain the U-boot images and also
Linux kernel images. It also contains two redundant root file systems.
This section describes how to configure U-boot to boot a Linux kernel stored in the boot
flash and to mount the root file system in the user flash. The procedure uses the U-Boot
script flashboot, which has been predefined by SMART Embedded Computing.
1.
Configure U-boot to boot from flash:
setenv bootcmd $flashboot
