PROCESSOR-SDK-AM64X: $TI_SECURE_DEV_PKG/scripts/secure-binary-image.sh bl31.bin bl31.bin.signed error

Rio Chan

In this doc:

file:///C:/Rio_Shared_Folder_2014/AM64_HS_FS_Stuffs/AM64x-Processor-SDK-08_04_01_04-Documentation/08_04_01_04/linux/Foundational_Components/U-Boot/UG-General-Info.html#build-u-boot-label

There are those 2 cmds.

$ $TI_SECURE_DEV_PKG/scripts/secure-binary-image.sh bl31.bin bl31.bin.signed
$ $TI_SECURE_DEV_PKG/scripts/secure-binary-image.sh bl32.bin bl32.bin.signed


So, the script needs to find the bl31/bl32.bin, But the bin is here: ./arm-trusted-firmware/build/k3/lite/release/

My question:
  How to solve the below bug?

$TI_SECURE_DEV_PKG/scripts/secure-binary-image.sh bl31.bin bl31.bin.signed
bl31.bin: No such file or directory
cat: bl31.bin: No such file or directory
Error Loading extension section v3_ca
140346248573376:error:0F076041:common libcrypto routines:OPENSSL_hexstr2buf:malloc failure:../crypto/o_str.c:157:
140346248573376:error:0D0B30B2:asn1 encoding routines:asn1_str2type:illegal hex:../crypto/asn1/asn1_gen.c:698:string=
140346248573376:error:22074074:X509 V3 routines:v3_generic_extension:extension value error:../crypto/x509v3/v3_conf.c:246:value=SEQUENCE:sysfw_image_integrity
cat: bl31.bin: No such file or directory

BR Rio

over 2 years ago

0 Rio Chan over 2 years ago

TI__Genius 14835 points

in this doc, file:///C:/Rio_Shared_Folder_2014/AM64_HS_FS_Stuffs/AM64x-Processor-SDK-08_04_01_04-Documentation/08_04_01_04/linux/Foundational_Components_ATF.html#foundational-components-atf

More question, There is only bl31.bin generated, how about the bl32.bin?

on HS
$ cd $TFA_DIR
$ make ARCH=aarch64 CROSS_COMPILE=aarch64-none-linux-gnu- PLAT=k3 TARGET_BOARD=lite SPD=opteed

Sign the output binary (bl31.bin) located in: $TFA_DIR/build/k3/lite/release
$ {TI_SECURE_DEV_PKG}/scripts/secure-binary-image.sh $TFA_DIR/build/k3/lite/release/bl31.bin $TFA_DIR/build/k3/lite/release/bl31.bin.signed

0 Hong Guan64 over 2 years ago in reply to Rio Chan

TI__Guru 68620 points

software-dl.ti.com/.../UG-General-Info.html
Note from the above link:
"The instructions below assume all binaries are built manually. For instructions to build bl31.bin go to: OP-TEE. For instructions to build bl32.bin/tee-pager_v2.bin go to: ARM Trusted Firmware-A. To use existing images, go to <path-to-tisdk>/board-support/prebuilt-images to get the pre-build binaries that come in the pre-built sdk."

0 Rio Chan over 2 years ago in reply to Hong Guan64

TI__Genius 14835 points

to build bl32.bin/tee-pager_v2.bin go to: ARM Trusted Firmware-A.

(Rio: so, what's the command to build the bl32 here? , please give an example.)

To use existing images, go to <path-to-tisdk>/board-support/prebuilt-images to get the pre-build binaries that come in the pre-built sdk."

(Rio: Do we always need to rebuild the bl32.bin?

I think the bl31/bl32.bin no need to be built either for GP or for HS.

Cause customers won't modify it.

Is my understanding correct or wrong?

0 Hong Guan64 over 2 years ago in reply to Rio Chan

TI__Guru 68620 points

Rio Chan said:
(Rio: so, what's the command to build the bl32 here? , please give an example.)

https://software-dl.ti.com/processor-sdk-linux/esd/AM64X/08_04_01_04/exports/docs/linux/Foundational_Components_OPTEE.html

Rio Chan said:
(Rio: Do we always need to rebuild the bl32.bin?

The ATF and OPTEE binaris in SDK prebuilt binary folder could be used directly if user don't want to modify them.

0 Rio Chan over 2 years ago in reply to Hong Guan64

TI__Genius 14835 points

this section ATF only mention the BL31. , no BL32.

Plz tell us why?

file:///C:/Rio_Shared_Folder_2014/AM64_HS_FS_Stuffs/AM64x-Processor-SDK-08_04_01_04-Documentation/08_04_01_04/linux/Foundational_Components_ATF.html#foundational-components-atf

And as you said the BL32 is here, but why the BL31 is not mention at here? Please tell us why.

https://software-dl.ti.com/processor-sdk-linux/esd/AM64X/08_04_01_04/exports/docs/linux/Foundational_Components_OPTEE.html

0 Rio Chan over 2 years ago in reply to Rio Chan

TI__Genius 14835 points

Let me clear my question again:

Q1.

Why there is no BL32.bin build command in the ATF section?

Does it mean: When building the ATF, we don't need to care about the BL32?

Q2.

And when building the OPTEE, studying the OPTEE document,

why there is no BL31 mentioned in that page?

BR Rio

0 Hong Guan64 over 2 years ago in reply to Rio Chan

TI__Guru 68620 points

atf (bl31.bin) and optee (bl32.bin) is built independently.

0 Rio Chan over 2 years ago in reply to Hong Guan64

TI__Genius 14835 points

If this, the document should explain clearly before doing the build cmd.

Otherwise, this will confuse all the users.

Processors

Processors forum

PROCESSOR-SDK-AM64X: $TI_SECURE_DEV_PKG/scripts/secure-binary-image.sh bl31.bin bl31.bin.signed error