Specifications

update=echo done
=> setenv u-boot /tftpboot/duts/m28/u-boot.bin
=> run load update
if mmc rescan ; then if tftp ${update_sd_firmware_filename} ; then setexpr fw_sz ${filesize} / 0x200 ; setexpr fw_sz ${fw_sz} + 1 ; mmc write ${loadaddr} 0x800 ${fw_sz} ; fi ; fi
Using FEC0 device
TFTP from server 192.168.1.1; our IP address is 192.168.20.33
Filename 'duts/m28/u-boot.mx28.sd'.
Load address: 0x42000000
Loading: ###############################
done
Bytes transferred = 446080 (6ce80 hex)
MMC write: dev # 0, block # 2048, count 872 ... 872 blocks write: OK
done
=> reset
resetting ...
U-Boot 2012.07-00471-ge8925d7-dirty (Oct 01 2012 - 18:20:02)
CPU: Freescale i.MX28 rev1.2 at 454 MHz
BOOT: SSP SD/MMC #0, 3V3
I2C: ready
DRAM: 256 MiB
NAND: 256 MiB
MMC: MXS MMC: 0
In: serial
Out: serial
Err: serial
Net: FEC0 [PRIME], FEC1
Hit any key to stop autoboot: 0
=> version
U-Boot 2012.07-00471-ge8925d7-dirty (Oct 01 2012 - 18:20:02)
arm-linux-gnueabi-gcc (Debian 4.7.2-2) 4.7.2
GNU ld (GNU Binutils for Debian) 2.22
=>
5.5. Tool Installation
U-Boot uses a special image format when loading the Linux kernel or ramdisk or other images. This image
contains (among other things) information about the time of creation, operating system, compression type,
image type, image name and CRC32 checksums.
The tool mkimage is used to create such images or to display the information they contain. When using the
ELDK, the mkimage command is already included with the other ELDK tools.
If you don't use the ELDK then you should install mkimage in some directory that is in your command
search PATH, for instance:
$ cp tools/mkimage /usr/local/bin/
5.6. Initialization
To initialize the U-Boot firmware running on your m28 board, you have to connect a terminal to the board's
serial console port.
5.6. Initialization 39