From: "Christian Hewitt" <christianshewitt@gmail.com>
To: u-boot-amlogic@groups.io, exkc_maillist@list.ru
Subject: Re: [PATCHv3 3/3] doc: boards: amlogic: add documentation for Beelink GT1 Ultimate
Date: Sun, 26 Mar 2023 09:13:00 +0400 [thread overview]
Message-ID: <E5B061AF-2BFA-4402-9832-19B257EFB7D5@gmail.com> (raw)
In-Reply-To: <VmFj.1679807446518599359.Etqf@groups.io>
> On 26 Mar 2023, at 9:10 am, exkc_maillist via groups.io <exkc_maillist=list.ru@groups.io> wrote:
>
> Add build instructions for the Beelink GT1 Ultimate board.
>
> Signed-off-by: Karl Chan <exxxxkc@getgoogleoff.me>
> ---
> board/amlogic/q200/MAINTAINERS | 2 +
> doc/board/amlogic/beelink-gt1-ultimate.rst | 109 +++++++++++++++++++++
> 2 files changed, 111 insertions(+)
> create mode 100644 doc/board/amlogic/beelink-gt1-ultimate.rst
>
> diff --git a/board/amlogic/q200/MAINTAINERS b/board/amlogic/q200/MAINTAINERS
> index 9c84cca27e..aece8d5e05 100644
> --- a/board/amlogic/q200/MAINTAINERS
> +++ b/board/amlogic/q200/MAINTAINERS
> @@ -4,9 +4,11 @@ S: Maintained
> L: u-boot-amlogic@groups.io
> F: board/amlogic/q200/
> F: include/configs/q200.h
> +F: configs/beelink-gt1-ultimate_defconfig
> F: configs/khadas-vim2_defconfig
> F: configs/libretech-s905d-pc_defconfig
> F: configs/libretech-s912-pc_defconfig
> F: configs/wetek-core2_defconfig
> +F: doc/board/amlogic/beelink-gt1-ultimate.rst
> F: doc/board/amlogic/khadas-vim2.rst
> F: doc/board/amlogic/wetek-core2.rst
> diff --git a/doc/board/amlogic/beelink-gt1-ultimate.rst b/doc/board/amlogic/beelink-gt1-ultimate.rst
> new file mode 100644
> index 0000000000..487b922650
> --- /dev/null
> +++ b/doc/board/amlogic/beelink-gt1-ultimate.rst
> @@ -0,0 +1,109 @@
> +.. SPDX-License-Identifier: GPL-2.0+
> +
> +U-Boot for Beelink GT1 Ultimate (S912)
> +======================================
> +
> +Beelink GT1 Ultimate is an Android STB manufactured by Shenzen AZW (Beelink) with the
> +following specification:
> +
> +- 2GB or 3GB DDR3 RAM
> +- 32GB eMMC
> +- HDMI 2.1 video
> +- S/PDIF optical output
> +- 10/100/1000 Ethernet
> +- AP6356S Wireless (802.11 a/b/g/n/ac, BT 4.2)
> +- 3x USB 2.0 ports
> +- IR receiver
> +- 1x micro SD card slot
> +- 1x Power LED (white)
> +- 1x Reset button (internal)
> +
> +The GT1 (non-ultimate) board has QCA9377 WiFi/BT but is otherwise identical and should
> +be capable of booting images prepared for the Ultimate box (NB: there are known clones
> +of both boxes which may differ in specifications).
> +
> +Beelink do not provide public schematics, but have been willing to share them with known
> +distro developers on request.
> +
> +U-Boot Compilation
> +------------------
> +
> +.. code-block:: bash
> +
> + $ export CROSS_COMPILE=aarch64-none-elf-
> + $ make beelink-gt1-ultimate_defconfig
> + $ make
> +
> +U-Boot Signing with Pre-Built FIP repo
> +--------------------------------------
> +
> +.. code-block:: bash
> +
> + $ git clone https://github.com/LibreELEC/amlogic-boot-fip --depth=1
> + $ cd amlogic-boot-fip
> + $ mkdir my-output-dir
> + $ ./build-fip.sh beelink-gt1 /path/to/u-boot/u-boot.bin my-output-dir
> +
> +U-Boot Manual Signing
> +---------------------
> +
> +Amlogic does not provide firmware sources or tools needed to create the bootloader image
> +and Beelink has not publicly shared the U-Boot sources needed to build the FIP binaries
> +for signing. However you can download them from the amlogic-fip-repo.
> +
> +.. code-block:: bash
=> line space is needed here
> + $ git clone https://github.com/LibreELEC/amlogic-boot-fip --depth=1
> + $ cd amlogic-boot-fip/beelink-gt1
> + $ export FIPDIR=$PWD
> +
> +Go back to the mainline U-Boot source tree then:
> +
> +.. code-block:: bash
> +
> + $ mkdir fip
> + $ cp $FIPDIR/bl2.bin fip/
> + $ cp $FIPDIR/acs.bin fip/
> + $ cp $FIPDIR/bl21.bin fip/
> + $ cp $FIPDIR/bl30.bin fip/
> + $ cp $FIPDIR/bl301.bin fip/
> + $ cp $FIPDIR/bl31.img fip/
> + $ cp u-boot.bin fip/bl33.bin
> +
> + $ $FIPDIR/blx_fix.sh \
> + fip/bl30.bin \
> + fip/zero_tmp \
> + fip/bl30_zero.bin \
> + fip/bl301.bin \
> + fip/bl301_zero.bin \
> + fip/bl30_new.bin \
> + bl30
> +
> + $ python $FIPDIR/acs_tool.pyc fip/bl2.bin fip/bl2_acs.bin fip/acs.bin 0
> +
> + $ $FIPDIR/blx_fix.sh \
> + fip/bl2_acs.bin \
> + fip/zero_tmp \
> + fip/bl2_zero.bin \
> + fip/bl21.bin \
> + fip/bl21_zero.bin \
> + fip/bl2_new.bin \
> + bl2
> +
> + $ $FIPDIR/aml_encrypt_gxl --bl3enc --input fip/bl30_new.bin
> + $ $FIPDIR/aml_encrypt_gxl --bl3enc --input fip/bl31.img
> + $ $FIPDIR/aml_encrypt_gxl --bl3enc --input fip/bl33.bin
> + $ $FIPDIR/aml_encrypt_gxl --bl2sig --input fip/bl2_new.bin --output fip/bl2.n.bin.sig
> + $ $FIPDIR/aml_encrypt_gxl --bootmk \
> + --output fip/u-boot.bin \
> + --bl2 fip/bl2.n.bin.sig \
> + --bl30 fip/bl30_new.bin.enc \
> + --bl31 fip/bl31.img.enc \
> + --bl33 fip/bl33.bin.enc
> +
> +Then write U-Boot to SD or eMMC with:
> +
> +.. code-block:: bash
> +
> + $ 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=1 count=440
> --
> 2.39.2
>
>
>
>
>
prev parent reply other threads:[~2023-03-26 5:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-26 5:10 [PATCHv3 3/3] doc: boards: amlogic: add documentation for Beelink GT1 Ultimate exkc_maillist
2023-03-26 5:13 ` Christian Hewitt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E5B061AF-2BFA-4402-9832-19B257EFB7D5@gmail.com \
--to=christianshewitt@gmail.com \
--cc=exkc_maillist@list.ru \
--cc=u-boot-amlogic@groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).