Dear,
I have just started working on a T2080QDS-PA board. the board failing in the U-boot sequence immediately after detecting the DDR3 ram ("Waiting for D_INIT timeout. Memory may not work."). and all configuration switches and jump as default reference QorIQ T2080 Development SystemQuick Start Guide,I replaced the new T2080 CPU and DDR Moduler,but the issue same before,and used the Flash Programmer(Superpro6100) to program the orignal image (from QorIQ SDK2.0/SDK1.9/SDK1.8/SDK1.7) to NorFlash,but can't close the issue,Would you give me some suggestions?thanks!
lzh
======================================================
U-Boot 2016.012.0+ga9b437f (May 15 2016 - 18:12:07 +0800)
CPU0: T2080, Version: 1.1, (0x85300011)
Core: e6500, Version: 2.0, (0x80400120)
Clock Configuration:
CPU0:1800 MHz, CPU1:1800 MHz, CPU2:1800 MHz, CPU3:1800 MHz,
CCB:600 MHz,
DDR:933.333 MHz (1866.667 MT/s data rate) (Asynchronous), IFC:150 MHz
FMAN1: 700 MHz
QMAN: 300 MHz
PME: 600 MHz
L1: D-cache 32 KiB enabled
I-cache 32 KiB enabled
Reset Configuration Word (RCW):
00000000: 0c070012 0e000000 00000000 00000000
00000010: 66150002 00000000 ec027000 c1000000
00000020: 00000000 00000000 00000000 000307fc
00000030: 00000000 00000000 00000000 00000004
I2C: ready
Board: T2080QDS, Sys ID: 0x28, Board Arch: V1, Board Version: A, boot from vBank0
FPGA: v7 (T1040QDS_2013_1120_1155), build 243 on Wed Nov 20 17:55:56 2013
SERDES Reference Clocks:
SD1_CLK1=156.25MHZ, SD1_CLK2=100.00MHz
SD2_CLK1=100.00MHz, SD2_CLK2=100.00MHz
SPI: ready
DRAM: Initializing....using SPD
Detected UDIMM 9JSF25672AZ-2G1K1
Waiting for D_INIT timeout. Memory may not work.
===================================================================
Hi all
Have you been resolve this problem. I had the trouble the same as you with custom board use b4860
Thanks and brgs
Hello leizhihualqytvw!
You have to set the Linux SDK step by step.
For your board you can see the steps following the link.
The Ram timings are off. I have the same issue with T2080-QDS 1U board. Doing a reset seems to get you past the issue but it is not a good solution. check your ram timings..