Difference between revisions of "Loading Images with U-Boot"
(created and added initial content) |
(added categories) |
||
| Line 3: | Line 3: | ||
== Requirements == | == Requirements == | ||
A TFTP server must be accessible on the local network. The specific details of TFTP server setup and configuration are beyond the scope of this document. EMAC recommends the <code>tftpd</code> package for use on Debian or Ubuntu Linux systems. For Windows, the [http://tftpd32.jounin.net/ Tftpd32] server works well. | A TFTP server must be accessible on the local network. The specific details of TFTP server setup and configuration are beyond the scope of this document. EMAC recommends the <code>tftpd</code> package for use on Debian or Ubuntu Linux systems. For Windows, the [http://tftpd32.jounin.net/ Tftpd32] server works well. | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | [[Category:Bootloaders]] | ||
Revision as of 08:08, 3 May 2013
While U-Boot is used to load and execute the OS after initial programming, it can also be used to program the OS images to the local flash. This page describes the process of using U-Boot to load Linux kernel and filesystem images from a TFTP server and save them to the local flash for use during the boot process. Review the U-Boot Overview page for an introduction to U-Boot before continuing.
Requirements
A TFTP server must be accessible on the local network. The specific details of TFTP server setup and configuration are beyond the scope of this document. EMAC recommends the tftpd package for use on Debian or Ubuntu Linux systems. For Windows, the Tftpd32 server works well.
