On 7/5/26 03:50, Chris Packham wrote:
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 <[email protected]>
Reviewed-by: Stefan Roese <[email protected]>
Thanks,
Stefan
---
Notes:
Changes in v2:
- Remove binary file accidentally included in v1
doc/board/alliedtelesis/x220.rst | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/doc/board/alliedtelesis/x220.rst b/doc/board/alliedtelesis/x220.rst
index 6ca5f61ec4e1..447867ac7d8a 100644
--- a/doc/board/alliedtelesis/x220.rst
+++ b/doc/board/alliedtelesis/x220.rst
@@ -18,7 +18,7 @@ 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
@@ -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
