doc: boards: amlogic: update documentation for SEI510

Signed-off-by: Christian Hewitt <christianshewitt@gmail.com>
Link: https://lore.kernel.org/r/20230320114609.930145-26-christianshewitt@gmail.com
[narmstrong: fixed doc build]
Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
This commit is contained in:
Christian Hewitt 2023-03-20 11:46:01 +00:00 committed by Neil Armstrong
parent 1437ff3b95
commit d1f366f5c2

View file

@ -1,21 +1,20 @@
.. SPDX-License-Identifier: GPL-2.0+ .. SPDX-License-Identifier: GPL-2.0+
U-Boot for Amlogic SEI510 U-Boot for Amlogic SEI510 (S905X2)
========================= ==================================
SEI510 is a customer board manufactured by SEI Robotics with the following SEI510 is a customer board manufactured by SEI Robotics with the following specification:
specifications:
- Amlogic S905X2 ARM Cortex-A53 quad-core SoC - Amlogic S905X2 ARM Cortex-A53 quad-core SoC
- 2GB DDR4 SDRAM - 2GB DDR4 SDRAM
- 10/100 Ethernet (Internal PHY) - 10/100 Ethernet (Internal PHY)
- 1 x USB 3.0 Host - 1x USB 3.0 Host
- eMMC - eMMC
- SDcard - SDcard
- Infrared receiver - Infrared receiver
- SDIO WiFi Module - SDIO WiFi Module
U-Boot compilation U-Boot Compilation
------------------ ------------------
.. code-block:: bash .. code-block:: bash
@ -24,14 +23,21 @@ U-Boot compilation
$ make sei510_defconfig $ make sei510_defconfig
$ make $ make
Image creation U-Boot Signing with Pre-Built FIP repo
-------------- --------------------------------------
For simplified usage, pleaser refer to :doc:`pre-generated-fip` with codename `sei510` .. code-block:: bash
Amlogic doesn't provide sources for the firmware and for tools needed $ git clone https://github.com/LibreELEC/amlogic-boot-fip --depth=1
to create the bootloader image, so it is necessary to obtain them from $ cd amlogic-boot-fip
the git tree published by the board vendor: $ mkdir my-output-dir
$ ./build-fip.sh sei510 /path/to/u-boot/u-boot.bin my-output-dir
U-Boot Manual Signing
---------------------
Amlogic does not provide sources for the firmware and tools needed to create a bootloader
image so it is necessary to obtain binaries from sources published by the board vendor:
.. code-block:: bash .. code-block:: bash
@ -46,7 +52,7 @@ the git tree published by the board vendor:
$ make $ make
$ export UBOOTDIR=$PWD $ export UBOOTDIR=$PWD
Download the latest Amlogic Buildroot package, and extract it : Download the latest Amlogic Buildroot package and extract it:
.. code-block:: bash .. code-block:: bash
@ -55,7 +61,7 @@ Download the latest Amlogic Buildroot package, and extract it :
$ export BRDIR=$PWD/buildroot_openlinux_kernel_4.9_fbdev_20180706 $ export BRDIR=$PWD/buildroot_openlinux_kernel_4.9_fbdev_20180706
$ export FIPDIR=$BRDIR/bootloader/uboot-repo/fip $ export FIPDIR=$BRDIR/bootloader/uboot-repo/fip
Go back to mainline U-Boot source tree then : Go back to the mainline U-Boot source tree then:
.. code-block:: bash .. code-block:: bash
@ -77,56 +83,56 @@ Go back to mainline U-Boot source tree then :
$ cp u-boot.bin fip/bl33.bin $ cp u-boot.bin fip/bl33.bin
$ sh fip/blx_fix.sh \ $ sh fip/blx_fix.sh \
fip/bl30.bin \ fip/bl30.bin \
fip/zero_tmp \ fip/zero_tmp \
fip/bl30_zero.bin \ fip/bl30_zero.bin \
fip/bl301.bin \ fip/bl301.bin \
fip/bl301_zero.bin \ fip/bl301_zero.bin \
fip/bl30_new.bin \ fip/bl30_new.bin \
bl30 bl30
$ sh fip/blx_fix.sh \ $ sh fip/blx_fix.sh \
fip/bl2.bin \ fip/bl2.bin \
fip/zero_tmp \ fip/zero_tmp \
fip/bl2_zero.bin \ fip/bl2_zero.bin \
fip/acs.bin \ fip/acs.bin \
fip/bl21_zero.bin \ fip/bl21_zero.bin \
fip/bl2_new.bin \ fip/bl2_new.bin \
bl2 bl2
$ $FIPDIR/g12a/aml_encrypt_g12a --bl30sig --input fip/bl30_new.bin \ $ $FIPDIR/g12a/aml_encrypt_g12a --bl30sig --input fip/bl30_new.bin \
--output fip/bl30_new.bin.g12a.enc \ --output fip/bl30_new.bin.g12a.enc \
--level v3 --level v3
$ $FIPDIR/g12a/aml_encrypt_g12a --bl3sig --input fip/bl30_new.bin.g12a.enc \ $ $FIPDIR/g12a/aml_encrypt_g12a --bl3sig --input fip/bl30_new.bin.g12a.enc \
--output fip/bl30_new.bin.enc \ --output fip/bl30_new.bin.enc \
--level v3 --type bl30 --level v3 --type bl30
$ $FIPDIR/g12a/aml_encrypt_g12a --bl3sig --input fip/bl31.img \ $ $FIPDIR/g12a/aml_encrypt_g12a --bl3sig --input fip/bl31.img \
--output fip/bl31.img.enc \ --output fip/bl31.img.enc \
--level v3 --type bl31 --level v3 --type bl31
$ $FIPDIR/g12a/aml_encrypt_g12a --bl3sig --input fip/bl33.bin --compress lz4 \ $ $FIPDIR/g12a/aml_encrypt_g12a --bl3sig --input fip/bl33.bin --compress lz4 \
--output fip/bl33.bin.enc \ --output fip/bl33.bin.enc \
--level v3 --type bl33 --level v3 --type bl33
$ $FIPDIR/g12a/aml_encrypt_g12a --bl2sig --input fip/bl2_new.bin \ $ $FIPDIR/g12a/aml_encrypt_g12a --bl2sig --input fip/bl2_new.bin \
--output fip/bl2.n.bin.sig --output fip/bl2.n.bin.sig
$ $FIPDIR/g12a/aml_encrypt_g12a --bootmk \ $ $FIPDIR/g12a/aml_encrypt_g12a --bootmk \
--output fip/u-boot.bin \ --output fip/u-boot.bin \
--bl2 fip/bl2.n.bin.sig \ --bl2 fip/bl2.n.bin.sig \
--bl30 fip/bl30_new.bin.enc \ --bl30 fip/bl30_new.bin.enc \
--bl31 fip/bl31.img.enc \ --bl31 fip/bl31.img.enc \
--bl33 fip/bl33.bin.enc \ --bl33 fip/bl33.bin.enc \
--ddrfw1 fip/ddr4_1d.fw \ --ddrfw1 fip/ddr4_1d.fw \
--ddrfw2 fip/ddr4_2d.fw \ --ddrfw2 fip/ddr4_2d.fw \
--ddrfw3 fip/ddr3_1d.fw \ --ddrfw3 fip/ddr3_1d.fw \
--ddrfw4 fip/piei.fw \ --ddrfw4 fip/piei.fw \
--ddrfw5 fip/lpddr4_1d.fw \ --ddrfw5 fip/lpddr4_1d.fw \
--ddrfw6 fip/lpddr4_2d.fw \ --ddrfw6 fip/lpddr4_2d.fw \
--ddrfw7 fip/diag_lpddr4.fw \ --ddrfw7 fip/diag_lpddr4.fw \
--level v3 --level v3
and then write the image to SD with: Then write U-Boot to SD or eMMC with:
.. code-block:: bash .. code-block:: bash
$ DEV=/dev/your_sd_device $ DEV=/dev/boot_device
$ dd if=fip/u-boot.bin.sd.bin of=$DEV conv=fsync,notrunc bs=512 skip=1 seek=1 $ dd if=fip/u-boot.bin.sd.bin of=$DEV conv=fsync,notrunc bs=512 skip=1 seek=1
$ dd if=fip/u-boot.bin.sd.bin of=$DEV conv=fsync,notrunc bs=1 count=444 $ dd if=fip/u-boot.bin.sd.bin of=$DEV conv=fsync,notrunc bs=1 count=440