[PATCH v5 20/23] doc: board: ti: Update documentation for binman flow

[Jan Kiszka]

On 07.07.23 15:30, Jerome Forissier wrote:
> 
> 
> On 7/7/23 14:34, Neha Malcom Francis wrote:
>> Earlier documentation specified builds for generating bootloader images
>> using an external TI repository k3-image-gen and core-secdev-k3. Modify
>> this to using the binman flow so that user understands how to build the
>> final boot images.
>>
>> Signed-off-by: Neha Malcom Francis <n-francis at ti.com>
>> Reviewed-by: Simon Glass <sjg at chromium.org>
>> ---
>>  doc/board/ti/am62x_sk.rst  | 42 ++++++++---------
>>  doc/board/ti/j721e_evm.rst | 50 +++++++++-----------
>>  doc/board/ti/k3.rst        | 95 +++++++++++++-------------------------
>>  3 files changed, 73 insertions(+), 114 deletions(-)
>>
>> diff --git a/doc/board/ti/am62x_sk.rst b/doc/board/ti/am62x_sk.rst
>> index 27d7b527c6..e4d58b4958 100644
>> --- a/doc/board/ti/am62x_sk.rst
>> +++ b/doc/board/ti/am62x_sk.rst
> [...]
>> @@ -139,35 +135,37 @@ Build procedure:
>>  ----------------
>>  1. ATF:
>>  
>> -.. code-block:: text
>> +.. code-block:: bash
>>  
>> - $ make CROSS_COMPILE=aarch64-none-linux-gnu- ARCH=aarch64 PLAT=k3 TARGET_BOARD=lite SPD=opteed
>> + $ make CROSS_COMPILE=aarch64-none-linux-gnu- ARCH=aarch64 PLAT=k3 \
>> +        TARGET_BOARD=lite SPD=opteed
>>  
>>  2. OPTEE:
>>  
>> -.. code-block:: text
>> +.. code-block:: bash
>>  
>> - $ make PLATFORM=k3 CFG_ARM64_core=y CROSS_COMPILE=arm-none-linux-gnueabihf- CROSS_COMPILE64=aarch64-none-linux-gnu-
>> + $ make PLATFORM=k3 CFG_ARM64_core=y CROSS_COMPILE=arm-none-linux-gnueabihf- \
>> +        CROSS_COMPILE64=aarch64-none-linux-gnu-
>>  
>>  3. U-Boot:
>>  
>>  * 3.1 R5:
>>  
>> -.. code-block:: text
>> +.. code-block:: bash
>>  
>> - $ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabihf- am62x_evm_r5_defconfig O=/tmp/r5
>> - $ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabihf- O=/tmp/r5
>> - $ cd <k3-image-gen>
>> - $ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabihf- SOC=am62x SBL=/tmp/r5/spl/u-boot-spl.bin SYSFW_PATH=<path to ti-linux-firmware>/ti-sysfw/ti-fs-firmware-am62x-gp.bin
>> -
>> -Use the tiboot3.bin generated from last command
>> + $ make ARCH=arm am62x_evm_r5_defconfig
>> + $ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabihf- \
>> +        BINMAN_INDIRS=<path/to/ti-linux-firmware>
>>  
>>  * 3.2 A53:
>>  
>> -.. code-block:: text
>> +.. code-block:: bash
>>  
>> - $ make ARCH=arm CROSS_COMPILE=aarch64-none-linux-gnu- am62x_evm_a53_defconfig O=/tmp/a53
>> - $ make ARCH=arm CROSS_COMPILE=aarch64-none-linux-gnu- ATF=<path to ATF dir>/build/k3/lite/release/bl31.bin TEE=<path to OPTEE OS dir>/out/arm-plat-k3/core/tee-pager_v2.bin DM=<path to ti-linux-firmware>/ti-dm/am62xx/ipc_echo_testb_mcu1_0_release_strip.xer5f O=/tmp/a53
>> + $ make ARCH=arm am62x_evm_a53_defconfig
>> + $ make ARCH=arm CROSS_COMPILE=aarch64-none-linux-gnu- \
>> +        BL31=<path to ATF dir>/build/k3/lite/release/bl31.bin \
>> +        TEE=<path to OPTEE OS dir>/out/arm-plat-k3/core/tee-pager_v2.bin \
> 
> Note that since OP-TEE 3.21.0, tee-raw.bin could/should be used instead of
> tee-pager_v2.bin. Indeed when the "pager" feature is not enabled, the two
> binaries are identical, and the newer name is hopefully less confusing.
> 

Ah, interesting. That will affect doc/board/siemens/iot2050.rst as well
(and our integration recipes).

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux