DRA821U-Q1: tiboot3.bin is not generated when using a custom machine in Yocto.

Part Number: DRA821U-Q1
Other Parts Discussed in Thread: J7200XSOMXEVM

Hi Team,

We are currently setting up a Yocto environment for a custom board based on the J7200XSOMXEVM reference design.
We are using version 10.01.08.01 (processor-sdk-linux-10_01_08_01.txt).

We created a custom layer and implemented the following settings.

$ tree ../sources/meta-custom
../sources/meta-custom
¦-- COPYING.MIT
¦-- README
¦-- conf
¦   ¦-- layer.conf
¦   ¦-- machine
¦       ¦-- custom-board-k3r5.conf
¦       ¦-- custom-board.conf
¦-- recipes-bsp
¦   ¦-- u-boot
¦       ¦-- u-boot-ti-staging
¦       ¦   ¦-- 0001-AAA.patch
¦       ¦   ¦-- 0002-BBB.patch
¦       ¦-- u-boot-ti-staging_%.bbappend
¦-- recipes-kernel
    ¦-- linux
        ¦-- linux-ti-staging-rt
        ¦   ¦-- 0001-AAA.patch
        ¦   ¦-- 0002-BBB.patch
        ¦-- linux-ti-staging-rt_%.bbappend

 

Contents of custom-board.conf

require conf/machine/include/j7200.inc

KERNEL_DEVICETREE_PREFIX = "custom/custom-board"

KERNEL_DEVICETREE = " \
    custom/custom-board.dtb \
"

UBOOT_MACHINE = "custom_board_a72_config"

 

Contents of custom-board-k3r5.conf

require conf/machine/include/k3r5.inc

SYSFW_SOC = "j7200_sr2"
SYSFW_CONFIG = "evm"
SYSFW_SUFFIX = "hs"

UBOOT_MACHINE = "custom_board_r5_config"

 

Executing the following steps creates "tispl.bin" and "u-boot.img" in "build/deploy-ti/images/custom-board", but "tiboot3.bin" is not generated.

MACHINE=custom-board bitbake u-boot-ti-staging

 

Executing the following generates "tiboot3.bin", but Secure Boot fails.

MACHINE=custom-board bitbake mc:k3r5:u-boot-ti-staging

 

What must be done to ensure that "tiboot3.bin" is generated when running "MACHINE=custom-board bitbake u-boot-ti-staging"?

Regards
mizutani

  • Hi ,

    What must be done to ensure that "tiboot3.bin" is generated when running "MACHINE=custom-board bitbake u-boot-ti-staging"?

    tiboot3.bin is not built when running that command. It is built when running with mc:k3r5.

    As a side note, by default, all soc types are built when running with MACHINE=j7200-evm

    Executing the following generates "tiboot3.bin", but Secure Boot fails.

    Which is correct for you: tiboot3-j7200-hs-evm.bin or tiboot3-j7200_sr2-hs-evm.bin?

    If you just want to test tiboo3.bin, you can try one of the evm specific tiboo3.bins. It should make it through.

    Best,
    Jared