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.

AM625: DDR doesn't work with CL=13

Part Number: AM625

On customer AM62x board, DDR4 is -075E Micron, it should be OK to work at 1600 -125E which CL=13. but can only work with CL=14, hang with CL=13 after tiboot3. 

I reproduced it on AM62-SK: With CL=13, stopped after tiboot3: 


U-Boot SPL 2021.01-00002-g77bcc61275-dirty (Aug 29 2022 - 15:14:49 +0800)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.3.2--v08.03.02 (Jolly Jellyfi')
spl_board_init() in evm.c done.
Trying to boot from MMC2

/* no more output */

Below is CL=14 log:

U-Boot SPL 2021.01-00002-g77bcc61275-dirty (Aug 29 2022 - 15:07:29 +0800)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.3.2--v08.03.02 (Jolly Jellyfi')
spl_board_init() in evm.c done.
Trying to boot from MMC2
Loading Environment from MMC... *** Warning - No MMC card found, using default environment

Starting ATF on ARM64 core...

NOTICE: BL31: v2.6(release):08.03.00.003-dirty
NOTICE: BL31: Built : 16:35:46, May 30 2022

U-Boot SPL 2021.01-00002-g77bcc61275-dirty (Aug 29 2022 - 14:46:41 +0800)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.3.2--v08.03.02 (Jolly Jellyfi')
spl_board_init() in evm.c done.
Trying to boot from MMC2


U-Boot 2021.01-00002-g77bcc61275-dirty (Aug 29 2022 - 14:46:41 +0800)

SoC: AM62X SR1.0
Model: Texas Instruments AM625 SK
EEPROM not available at 0x50, trying to read at 0x51
Tony Board: AM62-SKEVM rev E2
DRAM: DDR size 0x40000000
1 GiB
MMC: mmc@fa10000: 0, mmc@fa00000: 1, mmc@fa20000: 2
Loading Environment from MMC... OK
In: serial@2800000
Out: serial@2800000
Err: serial@2800000
Net: eth0: ethernet@8000000port@1
Hit any key to stop autoboot: 0
=>

  • Tony, i will reproduce on EVM and get back to you

    James

  • Tony, i also got it to fail on EVM, however, the EVM device is a -062E, and according to the table below from the memory datasheet, a -062E will not work at -125E conditions, only at  -125, which means it will only work with CL=14 with Read DBI enabled.  So i think the failures on the EVM may be expected.

    However, if the customer truly is using -075E, then it should be compatible with -125E operation.  I'm not sure what could be going wrong.  Can you confirm they have a -075E device?  

    Regards,

    James