Question about boot failure of AM64-SK

[Masahiro Yamada]

On Mon, Sep 25, 2023 at 1:28 PM Vignesh Raghavendra <vigneshr at ti.com> wrote:
>
> Hi,
>
> On 21/09/23 21:52, Masahiro Yamada wrote:
> > On Fri, Sep 22, 2023 at 12:03 AM Masahiro Yamada <masahiroy at kernel.org> wrote:
> >>
> >> Hi.
> >>
> >> I am seeing a boot failure on AM64-SK.
> >>
> >>
> >> I got the following error in SPL of the main core.
> >> Do you have any clue?
> >
> >
> >
> > As a side-topic, I downloaded a prebuilt image
> > from https://www.ti.com/tool/SK-AM64
> >
> > It failed too (but in a different way).
> >
> > I flashed tisdk-debian-bookworm-am64xx-evm.wic
> > to a SD card by using the 'dd' command, then I got this:
> >
>
>
> Prebuilt images are targeted for High Secure (HS FS) devices. Looks like
> the board has a non HS Silicon (GP). Please overwrite the tiboot3.bin in
> boot partition with that of GP
>
> cp tiboot3-am64x-gp-evm.bin tiboot3.bin

Yeah, it made progress.

But, it failed in the same way as the latest U-Boot.






U-Boot SPL 2023.04 (Jul 14 2023 - 08:10:06 +0000)
EEPROM not available at 0x50, trying to read at 0x51
Resetting on cold boot to workaround ErrataID:i2331
Please resend tiboot3.bin in case of UART/DFU boot
resetting ...

U-Boot SPL 2023.04 (Jul 14 2023 - 08:10:06 +0000)
EEPROM not available at 0x50, trying to read at 0x51
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.5--v09.00.05 (Kool Koala)')
SPL initial stack usage: 13376 bytes
Trying to boot from MMC2
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
Loading Environment from MMC... MMC Device 0 not found
*** Warning - No MMC card found, using default environment

Starting ATF on ARM64 core...

NOTICE:  BL31: v2.8(release):v2.8-226-g2fcd408bb
NOTICE:  BL31: Built : 08:09:13, Jul 14 2023
I/TC:
I/TC: OP-TEE version: 3.20.0 (gcc version 11.3.1 20220712 (Arm GNU
Toolchain 11.3.Rel1)) #1 Fri Jul 14 08:09:59 UTC 2023 aarch64
I/TC: WARNING: This OP-TEE configuration might be insecure!
I/TC: WARNING: Please check
https://optee.readthedocs.io/en/latest/architecture/porting_guidelines.html
I/TC: Primary CPU initializing
I/TC: SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.5--v09.00.05 (Kool Koala)')
I/TC: HUK Initialized
I/TC: Activated SA2UL device
I/TC: Fixing SA2UL firewall owner for GP device
I/TC: Enabled firewalls for SA2UL TRNG device
I/TC: SA2UL TRNG initialized
I/TC: SA2UL Drivers initialized
I/TC: Primary CPU switching to normal world boot

U-Boot SPL 2023.04 (Jul 14 2023 - 08:11:18 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.5--v09.00.05 (Kool Koala)')
Trying to boot from MMC2
Error reading cluster
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###








-- 
Best Regards
Masahiro Yamada