TDA4VP-Q1: Creating U-boot binaries files for GP J784S4 device by Yocto compilation

Can you tell us why you need tispl.bin_unsigned & u-boot.img_unsigned files? Can't you use the generated tispl.bin, & u-boot.img?

Thanks.

Hi,

When I try to load the tispl.bin file, it seems the TDA stuck,
I don't see the cc.. print for the u-boot.img loading

Is it can be related that the tispl.bin file isn't unsigned

TDA log:

U-Boot SPL 2024.04-ti-g818c76aed67f (Aug 01 2024 - 19:19:47 +0000)
SYSFW ABI: 4.0 (firmware rev 0x000a '10.0.8--v10.00.08 (Fiery Fox)')
Initialized 3 DRAM controllers
i2c_write: error waiting for data ACK (status=0x116)
tps6287x_regulator regulator@40: CTRL2 reg read failed: -121
SPL initial stack usage: 13456 bytes
Trying to boot from UART
CCWarning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Loaded 1087031 bytes
i2c_write: error waiting for data ACK (status=0x116)
tps6287x_regulator regulator@40: CTRL2 reg read failed: -121
Loading Environment from nowhere... OK
init_env from device 7 not supported!
Starting ATF on ARM64 core...

Thanks,
Rachel

Hi Rachel,

The log:

Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted

shouldn't be an issue. I see it when booting my GP device as well.

Since you're using a custom board, have you followed the: custom board bring up guide?

Additionally, what MACHINE are you building when running the bitbake command?

Best,
Jared

Hi Jared,

In our board, we changed the UART port, I used https://www.ti.com/lit/an/spradg5/spradg5.pdf?ts=1723883607340 guide for do these changes.
Maybe I need to add more changes for it, I will debug it.

The machine for building is Ubuntu 22.04.

Thanks,
Rachel

Hi Rachel,

Let me know the results of your debugging. If there's an issue with the UART port, then you won't see any boot logs (as expected).

Additionally, when I said MACHINE, I meant the bitbake variable. For example, j784s4-evm

Best,
Jared

Hi Jared,

I succeeded to load the tiboot3.bin, tispl.bin_unsigned, u-boot.img_unsigned files of ti-processor-sdk-linux-adas-j784s4-evm-10_00_00_08 SDK on our custom board (After I changed the UART port according to https://www.ti.com/lit/an/spradg5/spradg5.pdf?ts=1723883607340 guide.

But I still not succeed to load the tispl.bin file of Yocto compilation, it stuck on "Starting ATF on ARM64 core..."
Maybe I didn't change the UART port correctly in OPTEE?
In SDK I used "export CFG_CONSOLE_UART=0x8" command but in the Yocto compilation I changed in the core/arch/arm/plat-k3/conf.mk
+#CFG_CONSOLE_UART ?= 0
+CFG_CONSOLE_UART = 2

Can you help me please?

I used MACHINE=j784s4-evm.

Thanks,
Rachel

Hi Rachel,

Have you looked at the TDA4: Custom Board Bring Up Guide?

It contains instructions on switching the UART console.

Best,
Jared

Hi Jared,

yes, I changed in the SDK and it worked me.

My question is how can I do the  "CFG_CONSOLE_UART=0x8" change in the bitbake command?

I use in the "MACHINE=j784s4-evm bitbake -f -c compile  trusted-firmware-a" command.

Thanks,
Rachel

Hi Rachel,

Looking within meta-ti, it looks like CFG_CONSOLE_UART is set by optee-os-ti-overrides.inc:

$ grep CFG_CONSOLE_UART -r ./*
./meta-ti/meta-ti-bsp/recipes-security/optee/optee-os-ti-overrides.inc:EXTRA_OEMAKE:append:k3 = "${@ ' CFG_CONSOLE_UART='+ d.getVar('OPTEE_K3_USART') if d.getVar('OPTEE_K3_USART') else ''}"

From there, it looks like OPTEE_K3_USART is set within the j784s4-evm.conf:

$ grep OPTEE_K3_USART -r ./*
...
./meta-ti/meta-ti-bsp/conf/machine/j784s4-evm.conf:OPTEE_K3_USART = "0x8"
...
./meta-ti/meta-ti-bsp/recipes-security/optee/optee-os-ti-overrides.inc:EXTRA_OEMAKE:append:k3 = "${@ ' CFG_CONSOLE_UART='+ d.getVar('OPTEE_K3_USART') if d.getVar('OPTEE_K3_USART') else ''}"

Can you try setting the value there?

Best,
Jared

Hi Rachel,

Glad to hear it works. Please mark your thread as resolved to close it.

Best,
Jared