3.1.1.5. SD, eMMC and USB¶

The commands for using SD cards, eMMC flash and USB mass storage devices (hard drives, flash drives, card readers, etc) are all very similar. The biggest difference is that on some hardware we may not be able to run U-Boot out of ROM from the storage device as it is unsupported. Once U-Boot is running however, any of these may be used for the kernel and the root filesystem.

Usually in all the platforms there will be two MMC instances of which one would be SD and the other would be eMMC. The index of them can vary from one class of platforms to the other. For a given platform, the device number (device num) can be found in the following way,

U-Boot# mmc list
sdhci@fa10000: 0 (eMMC)
sdhci@fa00000: 1 (SD)


3.1.1.5.1. Partitioning eMMC from U-Boot¶

The eMMC device typically ships without any partition table. We make use of the GPT support in U-Boot to write a GPT partition table to eMMC. In this case we need to use the uuidgen program on the host to create the UUIDs used for the disk and each partition.

$uuidgen ...first uuid...$ uuidgen
...second uuid...

U-Boot # printenv partitions
uuid_disk=${uuid_gpt_disk};name=rootfs,start=2MiB,size=-,uuid=${uuid_gpt_rootfs}
U-Boot # setenv uuid_gpt_disk ...first uuid...
U-Boot # setenv uuid_gpt_rootfs ...second uuid...

3.1.1.5.3. Updating an SD card or eMMC using DFU¶

To see the list of available places to write to (in DFU terms, altsettings) use the mmc part command to list the partitions on the MMC device and printenv dfu_alt_settings_mmc or dfu_alt_settings_emmc to see how they are mapped and exposed to dfu-util.

U-Boot# mmc part

Partition Map for MMC device 0  --   Partition Type: DOS

Partition     Start Sector     Num Sectors     Type
1                   63          144522       c Boot
2               160650         1847475      83
3              2024190         1815345      83
U-Boot# printenv dfu_alt_info_mmc
dfu_alt_info=boot part 0 1;rootfs part 0 2;MLO fat 0 1;u-boot.img fat 0 1;uEnv.txt fat 0 1"


Note

The above command mmc part lists the partitions in the current selected device. So, to list the partitions in eMMC or SD one needs to switch to the required device by using the command mmc dev <device num>.

This means that you can tell dfu-util to write anything to any of:

• boot
• rootfs
• MLO
• u-boot.img
• uEnv.txt

And that the MLO, u-boot.img and uEnv.txt files are to be written to a FAT filesystem.

To start DFU on the target on the first MMC device:

U-Boot # setenv dfu_alt_info ${dfu_alt_info_mmc} U-Boot # dfu 0 mmc 0  On boards like AM57x GP EVM or BeagleBoard x15, where the second USB instance is used as USB client, the dfu command becomes: U-Boot # dfu 1 mmc 0  Then on the host PC to write MLO to an existing boot partition: $ sudo dfu-util -D MLO -a MLO


On the host PC to overwrite the current boot partition contents with a new created on the host FAT filesystem image:

$sudo dfu-util -D fat.img -a boot  3.1.1.5.4. Booting Linux from SD card or eMMC¶ Within the default environment for each board that supports SD/MMC there is a boot command called mmcboot that will set the boot arguments correctly and start the kernel. In this case however, you must first run loaduimagefat or loaduimage to first load the kernel into memory. For the exact details of each use printenv on the mmcboot, loaduimagefat and loaduimage variables and then in turn printenv other sub-sections of the command. The most important variables here are mmcroot and mmcrootfstype. 3.1.1.5.5. Booting tiboot3.bin, tispl.bin and u-boot.img from eMMC boot partition (For K3 class of SoCs)¶ The K3 based processors support booting from the eMMC boot partition. The following commands can be used to download tiboot3.bin, tispl.bin and u-boot.img from an SD card and write them to the eMMC boot0 partition at respective addresses. Note By default, SDK chooses boot0 partition for eMMC boot (equivalently done using mmc partconf 0 1 1 1). Boot partition can also be switched from boot0 to boot1 by using mmc partconf 0 1 2 1. This enables booting from boot1 partition. Switch to boot1 partition using mmc dev 0 2 and follow regular eMMC write commands (seen below). On rebooting with regular eMMC dip switch settings, boot1 partition will be used. => mmc dev 0 1 => fatload mmc 1${loadaddr} tiboot3.bin
=> mmc write ${loadaddr} 0x0 0x800 => fatload mmc 1${loadaddr} tispl.bin
=> mmc write ${loadaddr} 0x800 0x1000 => fatload mmc 1${loadaddr} u-boot.img
=> mmc write ${loadaddr} 0x1800 0x2000  For loading images from a FAT partition on a different media, replace mmc with the required media. For example, to load images from a FAT partition on a USB Storage device connected to the zeroth instance of usb, => fatload usb 0${loadaddr} <file name>


Note

USB instance in AM64 SoC is brought out using a USB 2.0 micro-AB port on the GP EVM. This port can be used in both host and device modes. By default in U-Boot, peripheral mode is supported. For accessing USB storage devices in U-Boot, dr_mode should be set to “host” in the U-Boot device tree file. The following diff shows the required changes to be done. On Starter Kit, USB instance in AM64 SoC is brought out using a USB 3.0 Type A port, so the mode is set to host by default and the following diff would not be required.

diff --git a/arch/arm/dts/k3-am642-evm-u-boot.dtsi b/arch/arm/dts/k3-am642-evm-u-boot.dtsi
index d066973f89f1..ff8afee09402 100644
--- a/arch/arm/dts/k3-am642-evm-u-boot.dtsi
+++ b/arch/arm/dts/k3-am642-evm-u-boot.dtsi
@@ -55,7 +55,7 @@
};

&usb0 {
-       dr_mode="peripheral";
+       dr_mode="host";
u-boot,dm-spl;
};


To give the ROM access to the boot partition, the following commands must be used for the first time:

=> mmc partconf 0 1 1 1
=> mmc bootbus 0 2 0 0

• eMMC layout:
           boot0 partition (8 MB)                        user partition
0x0+----------------------------------+      0x0+-------------------------+
|     tiboot3.bin (1 MB)           |         |                         |
0x800+----------------------------------+         |                         |
|       tispl.bin (2 MB)           |         |                         |
0x1800+----------------------------------+         |        rootfs           |
|       u-boot.img (4 MB)          |         |                         |
0x3800+----------------------------------+         |                         |
|      environment (128 KB)        |         |                         |
0x3900+----------------------------------+         |                         |
|   backup environment (128 KB)    |         |                         |
0x3A00+----------------------------------+         +-------------------------+


Note

rootfs is written to the user partition. The user partition is first required to be formatted as a ext4 file system and then the rootfs has to be written. It is not possible to format a partition to ext4 in U-Boot. It is required to boot to kernel and write rootfs to user partition after formatting it to ext4. Kernel image and DT are expected to be present in the /boot folder of rootfs.

To boot kernel from eMMC, use the following commands after writing rootfs to user partition:

=> setenv mmcdev 0
=> setenv bootpart 0
=> boot


3.1.1.5.6. Booting to U-Boot prompt from USB storage¶

Booting to U-Boot prompt from USB storage is supported. The following are the steps to be followed,

1. Build the bootloader images using default “am64x_evm_r5_defconfig” and “am64x_evm_a53_defconfig” configs files. The configs required for USB MSC boot are already enabled. For instructions to build the bootloader images please refer to Build U-Boot.
2. Create a FAT32 partition with boot flag enabled on the USB storage device.
3. Copy the bootloader images(tiboot3.bin, tispl.bin, u-boot.img) into the above created partition.
4. Set the boot mode switches to usb host mode by referring to the Technical Reference manual.
5. Connect the USB Mass storage device with the bootloader images and boot up the board.

Note

While using usb reset or usb start command in U-Boot, or booting from a USB Mass storage device, some of the USB devices fail to get detected. This issue is seen because these USB devices are failing to follow the spec for power good delay. It can be resolved by overriding the power good delay using the environment variable usb_pgood_delay. Setting it to 2000 should be good enough for all cases.

3.1.1.5.7. Booting Linux from USB storage¶

To load the Linux kernel, Device Tree and the Root file system from USB Mass storage device, the following changes are required to be done,

• U-Boot

1. In U-Boot the USB controller can be used in either host or peripheral mode. For booting to linux kernel from USB storage device, the USB port is to be set as host.
2. By default, the USB controller is set in peripheral mode.
3. If the boot media used to boot to U-Boot is USB Host mode(Booting to U-Boot prompt from USB storage) then, the USB controller is set to host mode during runtime. Therefore, no changes would be required in this case.
4. If a boot media other than USB Host is used, the USB controller needs to be set host mode and custom bootloader images are required to be built. Please refer to note in section Booting tiboot3.bin, tispl.bin and u-boot.img from eMMC boot partition (For K3 class of SoCs)
• Kernel

1. In kernel, by default the USB subsystem is built as modules. For booting from USB mass storage device, USB subsytem is required to be built into the image. This can be done by making the following changes in the configuration used for building kernel,
CONFIG_USB=y
CONFIG_USB_XHCI_HCD=y
CONFIG_USB_XHCI_PLATFORM=y
CONFIG_USB_STORAGE=y

=> run usbboot