AM625: top level make uboot fail with SDK8.06

Tony Tang

Part Number: AM625

Today I deleted SDK8.6 and reinstalled , build on top level folder failed. it was OK on previous installation. I deleted again and restart computer to install and build again, still fail.

Yesterday a customer also reported the same issue.

while the SDK8.6 RT Linux can build success with same command.

over 2 years ago

0 Prashant Shivhare over 2 years ago

TI__Guru 69061 points

Hi Tony,

Please note the new SDKs work out-of-the box with HS-FS boards. For HS-FS boards, the bootable binaries generated needs to be signed and the SDK expects the environment variable named TI_SECURE_DEV_PKG to point to the path containing Security Development tools which will be used for signing the images. So, the error came because the SDK by default is building for HS-FS and the environment variable TI_SECURE_DEV_PKG is not setup.

Please refer to the below link for more information and setting up the required environment variable

https://software-dl.ti.com/processor-sdk-linux/esd/AM62X/08_06_00_42/exports/docs/linux/Foundational_Components_Migration_Guide.html#k3-image-gen

Regards,

Prashant

0 Tony Tang over 2 years ago in reply to Prashant Shivhare

TI__Mastermind 28922 points

Prashant,

Thanks, so no matter from SDK Top level makefile or UBOOT Top level makefile, all need to set TI_SECURE_DEV_PKG? if so, would suggest update acedemy user guide also.

https://dev.ti.com/tirex/explore/node?node=A__ACXcm3u9E-Vc3nFNuRrWow__linux_academy_am62x__XaWts8R__LATEST

0 Prashant Shivhare over 2 years ago in reply to Tony Tang

TI__Guru 69061 points

Hi Tony,

Yes, for secure devices, the environment variable TI_SECURE_DEV_PKG must be defined. Also, I believe the Linux Academy page you shared already contains the instruction to set this variable.

Regards,

Prashant

0 Tony Tang over 2 years ago in reply to Prashant Shivhare

TI__Mastermind 28922 points

It is under U-Boot top level , should also highlight it under SDK top level.

And better to highlight use bl31.bin.unsigned and bl32.bin.unsigned for gp device in below command.

make ATF=../prebuilt-images/bl31.bin TEE=../prebuilt-images/bl32.bin DM=../prebuilt-images/ipc_echo_testb_mcu1_0_release_strip.xer5f O=build/arm64

0 Prashant Shivhare over 2 years ago in reply to Tony Tang

TI__Guru 69061 points

Hi Tony,

Tony Tang said:
It is under U-Boot top level , should also highlight it under SDK top level.

Thanks for the feedback. I will pass on the same to the concerned person.

Tony Tang said:
And better to highlight use bl31.bin.unsigned and bl32.bin.unsigned for gp device in below command.

This is not exactly mandatory. The prebuilt images bl31.bin & bl32.bin though signed images will work on GP devices also. The SDK gracefully skips the certificate on GP devices. The SDK also reports a warning if it skips the certificate as shown

Regards,

Prashant

Processors

Processors forum

AM625: top level make uboot fail with SDK8.06