• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 99 subscribers
  • Views 288 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM6442: HS device, building with MACHINE=am64xx-hs-evm errors

Gunter Schmer
Genius 14212 points
Part Number: AM6442

Hi,

I am currently trying to build u-boot artifacts with Yocto and the latest config file processor-sdk-08.02.00.24-config.txt

Building for a GP device works fine

omen-rtx2080ti:~/oe/tisdk/build$ MACHINE=am64xx-evm bitbake tisdk-base-image

However when building for an HS device, I am getting an error

omen-rtx2080ti:~/oe/tisdk/build$ MACHINE=am64xx-hs-evm bitbake tisdk-base-image

...

| aarch64-none-linux-gnu-objcopy -O binary /home/gunter/oe/tisdk/build/arago-tmp-external-arm-glibc/work/am64xx_hs_evm-linux/trusted-firmware-a/2.5-r0/build/k3/lite/release/bl31/bl31.elf /home/gunter/oe/tisdk/build/arago-tmp-external-arm-glibc/work/am64xx_hs_evm-linux/trusted-firmware-a/2.5-r0/build/k3/lite/release/bl31.bin
| aarch64-none-linux-gnu-objdump -dx /home/gunter/oe/tisdk/build/arago-tmp-external-arm-glibc/work/am64xx_hs_evm-linux/trusted-firmware-a/2.5-r0/build/k3/lite/release/bl31/bl31.elf > /home/gunter/oe/tisdk/build/arago-tmp-external-arm-glibc/work/am64xx_hs_evm-linux/trusted-firmware-a/2.5-r0/build/k3/lite/release/bl31/bl31.dump
|
| Built /home/gunter/oe/tisdk/build/arago-tmp-external-arm-glibc/work/am64xx_hs_evm-linux/trusted-firmware-a/2.5-r0/build/k3/lite/release/bl31.bin successfully
|
| /home/gunter/oe/tisdk/build/arago-tmp-external-arm-glibc/work/am64xx_hs_evm-linux/trusted-firmware-a/2.5-r0/temp/run.do_compile.3037533: line 115: /scripts/secure-binary-image.sh: No such file or directory
| WARNING: /home/gunter/oe/tisdk/build/arago-tmp-external-arm-glibc/work/am64xx_hs_evm-linux/trusted-firmware-a/2.5-r0/temp/run.do_compile.3037533:1 exit 127 from 'export TI_SECURE_DEV_PKG=${TI_SECURE_DEV_PKG_K3}'
| ERROR: Execution of '/home/gunter/oe/tisdk/build/arago-tmp-external-arm-glibc/work/am64xx_hs_evm-linux/trusted-firmware-a/2.5-r0/temp/run.do_compile.3037533' failed with exit code 127
ERROR: Task (/home/gunter/oe/tisdk/sources/meta-arm/meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a_2.1.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1727 tasks of which 21 didn't need to be rerun and 1 failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 1 seconds
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 1 seconds

Summary: 1 task failed:
/home/gunter/oe/tisdk/sources/meta-arm/meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a_2.1.bb:do_compile
Summary: There were 4 WARNING messages shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

Have we validated the machine am64xx-hs-evm?

Thanks,

--Gunter

Thanks!

--Gunter

  • 0
    TI__Guru 69602 points

    Hi Gunter,

    I've not tried the AM64 HS build myself yet but since we are building our SDKs and filesystem images from the very same sources that are publicly available and that you are using yes it has been validated. The error message points to a script that is publicly available so I'm not sure what is missing there but I'd guess some setup step.

    Just to verify the basics:

    1. AFAIK building for HS devices requires a "SECDEV" package to be installed locally. I assume this is being done, right?
    2. Was the build performed from a completely clean state (right after setting up the Yocto environment)? If not, can you delete all folders inside build/ except the conf/ folder and try again?

    Also I'm checking with our HS expert to see if anything spikes out and will report back here.

    Regards, Andreas

  • 0 in reply to Andreas Dannenberg
    TI__Guru 69602 points

    Hi Gunter,

    as hinted at earlier building for HS device requires a special package. It's actually documented in the SDK guide but just not under the Yocto section. I'll file a ticket to get that information added there, otherwise it's too hard to find for somebody new to this. Ideally, it should be part of the Yocto build itself.

    https://software-dl.ti.com/processor-sdk-linux/esd/AM64X/08_02_00_23/exports/docs/linux/Foundational_Components/U-Boot/UG-General-Info.html#build-u-boot

    Getting Security Dev Tool

    $ git clone git://git.ti.com/security-development-tools/core-secdev-k3.git -b master
$ export TI_SECURE_DEV_PKG=`pwd`/core-secdev-k3

    With this your build should work as expected.

    Regards, Andreas

  • 0 in reply to Andreas Dannenberg
    TI__Intellectual 770 points

    Andreas, Gunter, Yocto uses a slightly different environment variable (than KIG) to find the location of the secdev package.  Follow Andreas' instructions above to download the secdev repo, then add the following to the environment variables listed before the bitbake command:

       TI_SECURE_DEV_PKG_K3=$TI_SECURE_DEV_PKG

    I have updated our documentation to include this.