u-boot

History

Jean-Jacques Hiblot d5abcf94c7 ti: boot: Register the MMC controllers in SPL in the same way as in u-boot To keep a consistent MMC device mapping in SPL and in u-boot, let's register the MMC controllers the same way in u-boot and in the SPL. In terms of boot time, it doesn't hurt to register more controllers than needed because the MMC device is initialized only prior being accessed for the first time. Having the same device mapping in SPL and u-boot allows us to use the environment in SPL whatever the MMC boot device. Signed-off-by: Jean-Jacques Hiblot <jjhiblot@ti.com>		2017-03-19 22:17:14 -04:00
..
Kconfig	kconfig: remove redundant "string" type in arch and board Kconfigs	2014-09-13 16:43:55 -04:00
MAINTAINERS	Add board MAINTAINERS files	2014-07-30 08:48:06 -04:00
Makefile	board: ti: convert makefiles to Kbuild style	2013-10-31 13:26:44 -04:00
README	omap5_uevm: Add CONFIG_SUPPORT_EMMC_BOOT, document usage	2014-02-07 18:17:49 +02:00
evm.c	ti: boot: Register the MMC controllers in SPL in the same way as in u-boot	2017-03-19 22:17:14 -04:00
mux_data.h	ARM: OMAP4/5: Remove dead code against CONFIG_SYS_ENABLE_PADS_ALL	2014-01-24 09:38:39 -05:00

README

Summary
=======

This document covers various features of the 'omap5_uevm' build and some
related uses.

eMMC boot partition use
=======================

It is possible, depending on SYSBOOT configuration to boot from the eMMC
boot partitions using (name depending on documentation referenced)
Alternative Boot operation mode or Boot Sequence Option 1/2.  In this
example we load MLO and u-boot.img from the build into DDR and then use
'mmc bootbus' to set the required rate (see TRM) and 'mmc partconfig' to
set boot0 as the boot device.
U-Boot # setenv autoload no
U-Boot # usb start
U-Boot # dhcp
U-Boot # mmc dev 1 1
U-Boot # tftp ${loadaddr} omap5uevm/MLO
U-Boot # mmc write ${loadaddr} 0 100
U-Boot # tftp ${loadaddr} omap5uevm/u-boot.img
U-Boot # mmc write ${loadaddr} 300 400
U-Boot # mmc bootbus 1 2 0 2
U-Boot # mmc partconf 1 1 1 0