arm: mvebu: Update docs for Allied Telesis x220
The current documentation doesn't work as-is for extracting the DDR training binary from the vendor bootloader. There are some seemingly undocumented alignment requirements that we need to meet by padding the binary file. Add some instructions on how to do this with objcopy. Also fix a minor spelling mistake while we're here. Signed-off-by: Chris Packham <judge.packham@gmail.com> Reviewed-by: Stefan Roese <stefan.roese@mailbox.org> [sr: fix title underline length]
This commit is contained in:
committed by
Stefan Roese
parent
c2bd067668
commit
cd26b17f87
@@ -18,8 +18,8 @@ markets.
|
||||
- GS980M/52
|
||||
- x230-52
|
||||
|
||||
DDR Traning (binhdr)
|
||||
--------------------
|
||||
DDR Training (binhdr)
|
||||
---------------------
|
||||
|
||||
The AlleyCat3 uses a binary blob for it's DDR training. This is launched by
|
||||
the built-in bootloader prior to U-Boot starting.
|
||||
@@ -37,3 +37,5 @@ image
|
||||
.. prompt:: bash $
|
||||
|
||||
./tools/dumpimage -T kwbimage -p 1 -o board/alliedtelesis/x220/binary.0 u-boot.kwb
|
||||
arm-softfloat-linux-gnueabi-objcopy -I binary -O binary --pad-to=0x12fcc \
|
||||
board/alliedtelesis/x220/binary.0 board/alliedtelesis/x220/binary.0
|
||||
|
||||
Reference in New Issue
Block a user