variants/hardkernel_odroid_h4/building-manual.md: Update SBL build instructions

Signed-off-by: Michał Żygowski <michal.zygowski@3mdeb.com>
This commit is contained in:
Michał Żygowski
2025-08-06 10:32:02 +02:00
parent ff9b547240
commit 94ee2fbf6f

View File

@@ -57,7 +57,7 @@ To build Dasharo (Slim Bootloader + UEFI) firmware image, first clone and enter
Slim Bootloader repository:
```bash
git clone https://github.com/Dasharo/slimbootloader.git -b odroid_h4_support
git clone https://github.com/Dasharo/slimbootloader.git
cd slimbootloader
```
@@ -76,41 +76,20 @@ then follow the steps below:
git checkout hardkernel_odroid_h4_v0.9.0
```
2. Checkout submodules:
```bash
git submodule update --init --checkout --recursive
```
3. We need vendor image from which IDF and ME regions will be used when
stitching loader. You can use official Dasharo release binary if you have
access to it or you can download AMI BIOS from
<https://dn.odroid.com/ODROID-H4/bios/>. After downloading ZIP make sure to
extract needed binary to slimbootloader repository under `image.rom` name:
```sh
unzip /path/to/ADLN-H4_B1.08.zip ADLN-H4_B1.08.bin
mv ADLN-H4_B1.08.bin image.rom
```
In above commands replace `1.08` with BIOS version you downloaded.
4. Build UEFI Payload and Slim BootLoader
2. Build UEFI Payload and Slim BootLoader
```sh
./build.sh odroid_h4
```
You can also pass path to vendor image via `INPUT_IMAGE` variable
!!! note
```sh
INPUT_IMAGE=~/Downloads/hardkernel_odroid_h4_v0.9.0.rom ./build.sh odroid_h4
```
If you wish to build Slim Bootloader with your own keys, run
`SBL_KEY_DIR=<path_to_keys> ./build.sh odroid_h4` instead, where the
`<path_to_keys>` is the path to the directory with keys generated with
`python BootloaderCorePkg\Tools\GenerateKeys.py -k <path_to_keys>` from the
clone Slim Bootloader directory. `<path_to_keys>` may be an absolute path
or path relative to Slim Bootloader repository directory.
The resulting Slim Bootloader image will be placed in the Slim Bootloader
directory as `Outputs/odroidh4/ifwi-release.bin`.
> The UEFI payload has almost no features enabled. Passing the following
> additional arguments: `-D VARIABLE_SUPPORT=SPI -D SECURE_BOOT_ENABLE=TRUE`
> `-D SMM_SUPPORT=TRUE -D CRYPTO_PROTOCOL_SUPPORT=TRUE` to enable variable
> and Secure Boot support results in a hang in the payload.
The resulting Slim Bootloader image will be placed in the Slim Bootloader
directory as `Outputs/odroid_h4/ifwi-release.bin`.