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: Warm RST in SPL does not work with eMMC on custom board

Part Number: AM6442
Other Parts Discussed in Thread: SK-AM64B

Hi,

our custom board does not load the SPL the second time. 

Due to the ErrataID i2331 there is a fix in the SPL which does a warm RST when detecting a cold RST:

Fullscreen
1
2
3
4
5
rst_src = readl(CTRLMMR_MCU_RST_SRC);
if (rst_src == COLD_BOOT || rst_src & (SW_POR_MCU | SW_POR_MAIN)) {
printf("Resetting on cold boot to workaround ErrataID:i2331\n");
do_reset(NULL, 0, 0, NULL);
}
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
cc

We get the SPL promt:
U-Boot SPL 2021.01-00012-g51cf5d0f1c-dirty (Mar 14 2024 - 09:30:41 +0100)
Resetting on cold boot to workaround ErrataID:i2331
resetting ...

but then it doesn't get further. 

This only happens when booting from eMMC. SD and USB boot works.

What is different between cold RST and warm RST?

We currently have problems with the speed of 200MHz, but I already added max-frequency = <100000000>; in the r5 devicetree.

BR

Artur

  • I'm having similar issues on a PROC100A board (SK-AM64B) using ti-processor-sdk-linux-am64xx-evm-09.02.00.08  SDK.

    I rebuilt the u-boot-r5 and get the following on the console :

    U-Boot SPL 2023.04-svn2 (Mar 20 2024 - 13:49:17 +0100)
    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 ...

    (the eeprom was probably overwritten in earlier developments using this board)

    When using the prebuilt image, I get the same result :

    U-Boot SPL 2023.04-ga97ca328b3 (Jan 08 2024 - 08:11:13 +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 ...

    Is this related to eMMC boot issue mentioned above?

  • The issue in the original e2e post was observed when booting from eMMC on the customer board. The original e2e submitter moved the original e2e post to "RESOLVED".

    You mentioned you were booting on PROC100A board (SK-AM64B) where there's NO eMMC. So it is a different issue.
    I'll recommend reposting your question to a new e2e post with all the details.
    Best,
    -Hong