|
@@ -37,12 +37,12 @@ not supported.
|
|
|
Flashing U-Boot onto an SD card
|
|
|
-------------------------------
|
|
|
|
|
|
-After a successful build, the generated SPL and U-boot binaries can be copied
|
|
|
+After a successful build, the generated SPL and U-Boot binaries can be copied
|
|
|
to an SD card. Adjust the SD card device as necessary:
|
|
|
|
|
|
$ sudo dd if=u-boot-with-spl.imx of=/dev/mmcblk0 bs=1k seek=1
|
|
|
|
|
|
-This is equivalent to separately copying the SPL and U-boot using:
|
|
|
+This is equivalent to separately copying the SPL and U-Boot using:
|
|
|
|
|
|
$ sudo dd if=SPL of=/dev/mmcblk0 bs=1k seek=1
|
|
|
$ sudo dd if=u-boot-dtb.img of=/dev/mmcblk0 bs=1k seek=197
|
|
@@ -50,11 +50,11 @@ $ sudo dd if=u-boot-dtb.img of=/dev/mmcblk0 bs=1k seek=197
|
|
|
The default bootscripts expect a kernel fit-image file named "fitImage" in the
|
|
|
first partition and Linux ext4 rootfs in the second partition.
|
|
|
|
|
|
-Flashing U-boot to the SPI Flash, for booting Linux from NAND
|
|
|
+Flashing U-Boot to the SPI Flash, for booting Linux from NAND
|
|
|
-------------------------------------------------------------
|
|
|
|
|
|
-The SD card created above can also be used to install the SPL and U-boot into
|
|
|
-the SPI flash. Boot U-boot from the SD card as above, and stop at the autoboot.
|
|
|
+The SD card created above can also be used to install the SPL and U-Boot into
|
|
|
+the SPI flash. Boot U-Boot from the SD card as above, and stop at the autoboot.
|
|
|
|
|
|
Then, clear the SPI flash:
|
|
|
|
|
@@ -64,13 +64,13 @@ Then, clear the SPI flash:
|
|
|
Load the equivalent of u-boot-with-spl.imx from the raw MMC into memory and
|
|
|
copy to the SPI. The SPL is expected at an offset of 0x400, and its size is
|
|
|
maximum 392*512-byte blocks in size, therefore 0x188 blocks, totaling 0x31000
|
|
|
-bytes. Assume U-boot should fit into 640KiB, therefore 0x500 512-byte blocks,
|
|
|
+bytes. Assume U-Boot should fit into 640KiB, therefore 0x500 512-byte blocks,
|
|
|
totalling 0xA0000 bytes. Adding these together:
|
|
|
|
|
|
=> mmc read ${loadaddr} 0x2 0x688
|
|
|
=> sf write ${loadaddr} 0x400 0xD1000
|
|
|
|
|
|
-The SPL is located at offset 0x400, and U-boot at 0x31400 in SPI flash, as to
|
|
|
+The SPL is located at offset 0x400, and U-Boot at 0x31400 in SPI flash, as to
|
|
|
match the SD Card layout. This would allow, instead of reading from the SD Card
|
|
|
above, with networking and TFTP correctly configured, the equivalent of:
|
|
|
|
|
@@ -84,7 +84,7 @@ image) and "root" (which contains a ubifs root filesystem).
|
|
|
The "bootm_size" variable in the environment
|
|
|
--------------------------------------------
|
|
|
|
|
|
-By default, U-boot relocates the device tree towards the upper end of the RAM,
|
|
|
+By default, U-Boot relocates the device tree towards the upper end of the RAM,
|
|
|
which kernels using CONFIG_HIGHMEM=y may not be able to access during early
|
|
|
-boot. With the bootm_size variable set to 0x30000000, U-boot relocates the
|
|
|
+boot. With the bootm_size variable set to 0x30000000, U-Boot relocates the
|
|
|
device tree to below this address instead.
|