
Linux kernel 3.10.31 introduces incompatible naming of SD card devices.We accomplish this by having a bootcmd which simply loads a distribution-specific startup script ( 6x_bootscript) from the first partition of either SD card or SATA drive. To elaborate, we leave the precise boot instructions to the userspace image itself, since different distributions package things differently and require at least different kernel command-lines. Our default bootcmd is set to run 6x_bootscript.Display support has been in U-Boot for a while now, and you should see a display without any SD card present. If you power-on a device with one of our displays connected, you should get an on-screen image.This allows the board to present a block device (such as an SD card) to the host as a mass storage device via the USB OTG port. U-Boot images include the USB Mass Storage Gadget.The default bootcmd variable will try FAT first, then ext2 (which supports ext3 and ext4). Our images will boot from FAT, ext2, ext3, or ext4 filesystems.Consult the corresponding documentation for details. Note that some userspaces may require the use of a certain boot media. If found, the script will be run (and won’t return if successful). The default bootcmd string is set to iterate through all of the boot media on your board, looking for the file 6x_bootscript in partition 1. Our images will boot from either SD card slot or SATA.
U BOOT BOOTARGS SERIAL
If you boot without a working 6x_bootscript on SD card or SATA, you’ll get a prompt on the display and USB keyboard in addition to the serial port.

It’s configured for direct connection to common USB serial adapters (i.e.

There are a lot of posts in this blog that describe the state of U-Boot for our i.MX6 boards, but most of them describe the history. This post is now DEPRECATED! Please visit our Wiki instead.
