At this time, no special builds of U-Boot are required to
This section documents how to configure the network and use it to loadįiles and then boot the Linux Kernel using a root filesystem mounted
When working with USB Device Firmware Upgrade (DFU), regardless of the Use the following table to determine what defconfig to use to configureģ.1.1.3. However first configure the build for the board you are working with. For e.g:īuilding of both u-boot and SPL is done at the same time. Release that corresponds to this U-Boot release. We strongly recommend using the toolchain that came with the Linux Core Targets it is very easy to know which folder contains the u-boot That way if you are working with multiple configuration You use an output directory name that is identical to the configuration We strongly recommend the use of separate object directories whenīuilding. Same media as the kernel, and from the same relative path.
The device tree is expected to be loaded from the In the Keystone-2įamily devices (K2H/K/E/L/G), it is specified by name_fdt variableįor each platform. To facilitate this in Sitaraįamily devices, within U-Boot we have a command in the environment namedįindfdt that will set the fdtfile variable to the name of theĭevice tree to use, as found with the kernel sources. GIT repo URL, branch and commit id can be found in theĪ note about device trees. Information are provided to show how to use a specific feature, whenįinally, please note that not all boards have all of the interfacesĪlternatively, U-Boot sources can directly be fetched from GIT. Servers is also outside of the scope of this document, but snippets of Linux Kernel has already been built (or has been provided) as well as anĪppropriate filesystem image.
Serial port for the board has been configured. We assume that a GCC-based toolchain has already been installed and the This document covers the general use of Linux Core Release of U-Boot on