Re: Providing (armhf) u-boot images together with d-i images?
On Mon, Dec 8, 2014 at 11:30 AM, Lennart Sorensen
> On Sat, Dec 06, 2014 at 01:07:35PM -0600, Robert Nelson wrote:
>> omap bootrom's with the introduction of the omap4 can be dd'ed liked
>> dd if=MLO of=/dev/sdX count=1 seek=1 conv=notrunc bs=128k
>> dd if=u-boot.img of=/dev/sdX count=2 seek=1 conv=notrunc bs=384k
> omap5 seems to have the MLO at 512 bytes from the start, so 128k would
> certainly not match in that case. More common seems to be the use of a
> "boot" partition with the files instead.
SWPU249AB OMAP543x Technical Reference Manual
(non public, so you have to register with ti, etc..)
188.8.131.52.4 Read Sector Procedure
The contents of an eMMC or SD card may be formatted as raw binary
(referred to as Raw(UDA) or within
a FAT file system. The ROM Code reads out sectors from raw image or
the booting file within the file
system and boots from it.
• Raw mode
In Raw(UDA) mode, an image can be at one of the four consecutive
locations in the main area: offset
0x0 (0 KiB)/0x20000 (128 KiB)/0x40000 (256 KiB)/0x60000 (384 KiB). For
this reason, the size of a
booting image must not exceed 128 KiB. However, a device with an image
greater than 128 KiB can
be flash starting at one of the aforementioned locations. Therefore,
the ROM code does not check the
image size. The only drawback is that the image crosses the subsequent
image boundary. Raw mode
is detected by reading sectors 0, 256, 512, and 768. The content of
these sectors is verified for the
presence of a TOC structure. For a GP device, a GP header must be
located at the beginning of the
booting image, as described in Section 184.108.40.206, Configuration Header.
Image data is read directly
from continuous sectors of a card. If raw mode is not detected, file
system mode is assumed.
PS... this dd locations also work for the upcoming AM572x
BeagleBoard-x15. (personally tested on the alpha boards)