T2080 DDR3L configuration in QCVS tool

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

T2080 DDR3L configuration in QCVS tool

586 Views
KL8
Contributor I

Hello NXP team,

 

We have a custom T2080 board integrated with DDR3L (part no: IS43TR16K01S2AL-125KBLI) - Discrete DRAM(8GB: 2GBx4)

 

While performing DDR validation in the CodeWarrior QCVS tool, getting an error as

 

"Error configuring the target! - DDR initialization failed: D_INIT was not cleared by hardware!"

 

Kindly anyone confirm the DDR configuration settings done as below is valid or not

  1. Selected "Auto configuration" and "Discrete DRAM"
  2. Type = DDR3L
  3. DRAM speed Rating = 1600 MT/s
  4. Output Data rate = 1600 MT/s
  5. Rank/Chip select = 2
  6. tCL = 11 clocks (13.8ns)
  7. Data bus width = 64 bits
  8. DRAM configuration per device = 8Gb: 512Mbx16 (according to our DDR the configuration given in datasheet is 1Gx16 but in QCVS tool there is no option available to configure it to 1Gx16 so we chosen it to 512Mbx16 )

Can we use the 512Mbx16 configuration for 1Gx16 configured DDR??

 

 

Thanks & Regards

Kareem

Labels (1)
0 Kudos
Reply
1 Reply

502 Views
yipingwang
NXP TechSupport
NXP TechSupport

the configuration is correct.

Selected "Auto configuration" and "Discrete DRAM"
Type = DDR3
DRAM speed Rating = 1600 MT/s
Output Data rate = 1600 MT/s
Rank/Chip select = 2
tCL = 11 clocks (13.8ns)
Data bus width = 64 bits
DRAM configuration per device = 8Gb: 512Mbx16 (the part is a dual-die chip, 512Mbx16 x 2 = 1Gx16)

user should properly configure the "Start Address" and "Size" for CS0 and CS1 respectively in QCVS.


The error “DDR initialization failed: D_INIT was not cleared by hardware” during QCVS validation typically means the DDR controller never completed its initialization sequence.
the possible causes include:

1. Clock or reset issues
DDR initialization requires stable clocks and proper reset sequencing. If SYSCLK or DDRCLK is unstable or incorrectly strapped, D_INIT will not clear.
Check that DIFF_SYSCLK and PLL ratios match T2080 datasheet requirements.

If DRAM device is held in reset or not properly released, D_INIT will never clear, check DRAM reset signal, user can refer to AN5097 as below:

JEDEC specifications for DDR3/3L/4 UDIMM or discrete DRAM require:
1. DRAM reset signal is asserted for a minimum of 200 μs 2. CKE signal is in logic level low for a minimum of 10 ns before the DRAM reset signal is deasserted 3. CKE signal remains low for a minimum of 500 μs after the DRAM reset signal is deasserted, Figure 18(see AN5097) illustrates these signal timing requirements.

2. Power Rail Sequencing
If DDR power rails or VDD_SOC are not within spec during initialization, the controller cannot complete training.
Ensure all voltages meet T2080 specs before DDR_RESET is released.

3. Incorrect DDR Configuration parameters in QCVS If timing parameters or memory topology settings do not match the DDR device’s datasheet, the controller cannot finish initialization.

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2248880%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3ET2080%20DDR3L%20configuration%20in%20QCVS%20tool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2248880%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CDIV%3E%3CP%3EHello%20NXP%20team%2C%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EWe%20have%20a%20custom%20T2080%20board%20integrated%20with%20DDR3L%20(part%20no%3A%20IS43TR16K01S2AL-125KBLI)%20-%20Discrete%20DRAM(8GB%3A%202GBx4)%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EWhile%20performing%20DDR%20validation%20in%20the%20CodeWarrior%20QCVS%20tool%2C%20getting%20an%20error%20as%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3CSTRONG%3E%22Error%20configuring%20the%20target!%20-%20DDR%20initialization%20failed%3A%20D_INIT%20was%20not%20cleared%20by%20hardware!%22%3C%2FSTRONG%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EKindly%20anyone%20confirm%20the%20DDR%20configuration%20settings%20done%20as%20below%20is%20valid%20or%20not%3C%2FP%3E%3COL%3E%3CLI%3E%3CSPAN%20class%3D%22%22%3ESelected%20%22Auto%20configuration%22%20and%20%22Discrete%20DRAM%22%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%20class%3D%22%22%3EType%20%3D%20DDR3L%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%20class%3D%22%22%3EDRAM%20speed%20Rating%20%3D%201600%20MT%2Fs%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%20class%3D%22%22%3EOutput%20Data%20rate%20%3D%201600%20MT%2Fs%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%20class%3D%22%22%3ERank%2FChip%20select%20%3D%202%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%20class%3D%22%22%3EtCL%20%3D%2011%20clocks%20(13.8ns)%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%20class%3D%22%22%3EData%20bus%20width%20%3D%2064%20bits%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSTRONG%3E%3CSPAN%20class%3D%22%22%3EDRAM%20configuration%20per%20device%20%3D%208Gb%3A%20512Mbx16%20(according%20to%20our%20DDR%20the%20configuration%20given%20in%20datasheet%20is%201Gx16%20but%20in%20QCVS%20tool%20there%20is%20no%20option%20available%20to%20configure%20it%20to%201Gx16%20so%20we%20chosen%20it%20to%20512Mbx16%20)%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FLI%3E%3C%2FOL%3E%3CP%3E%3CSTRONG%3E%3CSPAN%20class%3D%22%22%3ECan%20we%20use%20the%20512Mbx16%20configuration%20for%201Gx16%20configured%20DDR%3F%3F%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CP%3E%3CSPAN%20class%3D%22%22%3EThanks%20%26amp%3B%20Regards%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22%22%3EKareem%3C%2FSPAN%3E%3C%2FP%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2248880%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CLINGO-LABEL%3EQorIQ%20T2%20Devices%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2251621%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20T2080%20DDR3L%20configuration%20in%20QCVS%20tool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2251621%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3E%3CSPAN%3Ethe%20configuration%20is%20correct.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3ESelected%20%22Auto%20configuration%22%20and%20%22Discrete%20DRAM%22%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3EType%20%3D%20DDR3%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3EDRAM%20speed%20Rating%20%3D%201600%20MT%2Fs%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3EOutput%20Data%20rate%20%3D%201600%20MT%2Fs%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3ERank%2FChip%20select%20%3D%202%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3EtCL%20%3D%2011%20clocks%20(13.8ns)%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3EData%20bus%20width%20%3D%2064%20bits%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3EDRAM%20configuration%20per%20device%20%3D%208Gb%3A%20512Mbx16%20(the%20part%20is%20a%20dual-die%20chip%2C%20512Mbx16%20x%202%20%3D%201Gx16)%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3Euser%20should%20properly%20configure%20the%20%22Start%20Address%22%20and%20%22Size%22%20for%20CS0%20and%20CS1%20respectively%20in%20QCVS.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3EThe%20error%20%E2%80%9CDDR%20initialization%20failed%3A%20D_INIT%20was%20not%20cleared%20by%20hardware%E2%80%9D%20during%20QCVS%20validation%20typically%20means%20the%20DDR%20controller%20never%20completed%20its%20initialization%20sequence.%20%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3Ethe%20possible%20causes%20include%3A%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3E1.%20Clock%20or%20reset%20issues%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3EDDR%20initialization%20requires%20stable%20clocks%20and%20proper%20reset%20sequencing.%20If%20SYSCLK%20or%20DDRCLK%20is%20unstable%20or%20incorrectly%20strapped%2C%20D_INIT%20will%20not%20clear.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3ECheck%20that%20DIFF_SYSCLK%20and%20PLL%20ratios%20match%20T2080%20datasheet%20requirements.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3EIf%20DRAM%20device%20is%20held%20in%20reset%20or%20not%20properly%20released%2C%20D_INIT%20will%20never%20clear%2C%20check%20DRAM%20reset%20signal%2C%20user%20can%20refer%20to%20AN5097%20as%20below%3A%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3EJEDEC%20specifications%20for%20DDR3%2F3L%2F4%20UDIMM%20or%20discrete%20DRAM%20require%3A%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E1.%20DRAM%20reset%20signal%20is%20asserted%20for%20a%20minimum%20of%20200%20%CE%BCs%202.%20CKE%20signal%20is%20in%20logic%20level%20low%20for%20a%20minimum%20of%2010%20ns%20before%20the%20DRAM%20reset%20signal%20is%20deasserted%203.%20CKE%20signal%20remains%20low%20for%20a%20minimum%20of%20500%20%CE%BCs%20after%20the%20DRAM%20reset%20signal%20is%20deasserted%2C%20Figure%2018(see%20AN5097)%20illustrates%20these%20signal%20timing%20requirements.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3E2.%20Power%20Rail%20Sequencing%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3EIf%20DDR%20power%20rails%20or%20VDD_SOC%20are%20not%20within%20spec%20during%20initialization%2C%20the%20controller%20cannot%20complete%20training.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3EEnsure%20all%20voltages%20meet%20T2080%20specs%20before%20DDR_RESET%20is%20released.%20%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3E3.%20Incorrect%20DDR%20Configuration%20parameters%20in%20QCVS%20If%20timing%20parameters%20or%20memory%20topology%20settings%20do%20not%20match%20the%20DDR%20device%E2%80%99s%20datasheet%2C%20the%20controller%20cannot%20finish%20initialization.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E