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.

DM355 Mobile DDR interface



Team,

 

Can you please help customer address below inquiry (Thanks):

We are working on the mobile DDR interface and I have a few questions. First, the interface appears to work with the 133MHz mDDR setup in a gel file that Rich has. We are trying to get it to work at 171MHz max rate which we need for our thruput. We have 200MHz Micron parts on the board MT46H64M16LFCK-5L_IT. Following SPRUEH7D which describes the Memory Controller for the mDDR/DDR2, I altered the following registers: PLL2CTRL, DDRPHYCTL1, SDCR,SDCR2,SDTIMR,SDTIMR2 and SDRCR.  After altering these registers, the memory tests no longer passes, but I did see the clock running at 171MHz from the memory controller. On the descriptions of these registers some parameters do not seem to be directly applicable to the Micron mDDR that we are using, so here are the questions:

 

1)      SDTIMR2 uses timing parameters tXSNR and tXSRD which the  MT46H64M16LFCK-5L_IT does not have. It does have tXSR which is “Exit self refresh to first valid command”, so I used this parameter for both tXSNR and XSRD??

2)      tRTP, also, is not in the Micron data sheets.

3)      tCKE = 1, equation says to use value tCKE -1 which would = 0, is this valid?

  • name update, sorry Oscar.

    Oscar,

    You seem to already have an example gel file with the 133mhz mobile ddr setup example as a reference.  I'll add an example gel file with this code  below as starting point in case you want to compare it and so here for others to benefit in the Forum community.  I am investigating internally on the maximum speed supported speed for mobile DDR and looking into this issue for you.  I will post more information as soon as I have it available.

    regards,

    miguel

     

    DM355_mobileDDRInitOnly.gel
  • Miguel,

    Thanks!  The customer had some follow up questions:

    What is the clock period that the following is running at (-6 is a 166mhz part)?  According to the spec for the -6 (166 mhz part):

    1)      tRFC should be 110ns (not 125 ns)

    2)      tXP should be 2 clock cycles at 166 MHz which is 12 ns (not 25 ns unless they are running at 80 MHz)

    3)      tRTP is not in the spec

    4)      READ LATENCY is defined as : CAS LATENCY + Round Trip Delay (RTD) -1, so in the following you are using READ_LATENCY => ( CAS_LATENCY + 3 ) which means that RTD = 4 clocks! I had used 1 per an example in the SPRUEH7D, but 4 sounds excessive.

    5)      SDTIM1, bits 26-25 are defined below as:            | ( ( ( tXP   / clkPeriod ) - 1 ) << 25 ) // T_XP
    but the spec defines it as “If tXP > tCKE, (which is true) then t_XP = tXP -1”

    6)      SDTIM1, bits 4-0, is tCKE-1 but tCKE = 1 can I use 0 as a register value?

  • Oscar,

    I have obtained confirmation from our design team and the maximum supported speed that we guarantee for Mobile DDR on DM355 is 133Mhz.

    We will be adding a note to the Datasheet to explicitly mention this.

    Thanks for the patience and let me know if there are any other questions.

    regards,

    miguel