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]

diff --git a/doc/board/alliedtelesis/x220.rst b/doc/board/alliedtelesis/x220.rst
index 6ca5f61ec4e12689cd8b798cfdc5f524d1308819..18bcac7f206b36e959cca3a48c3aaf0f972abd25 100644 (file)
--- a/doc/board/alliedtelesis/x220.rst
+++ b/doc/board/alliedtelesis/x220.rst
@@ -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