Hi the write leveling compensates for fly-by skew and memory chip ck-dqs timing, while the read leveling calibrates for dq-dqs skew in read transactions. jesd79-3x mentiones it in the multi purpose register description, protocol example, since it is a feature of the memory controller, not really the memory chip. regards, Istvan Nagy CCT ----- Original Message ----- From: Qu, Pingyu (Perry) To: hermann.ruckerbauer@xxxxxxxxxxxxx ; Istvan Nagy Cc: si-list@xxxxxxxxxxxxx Sent: Friday, April 16, 2010 2:51 PM Subject: RE: [SI-LIST] Re: unbalanced setup/hold for DDR3 read Thanks, Istvan, Hermann. From what I read, read leveling is used to adjust skew caused by fly-by topology between different byte lanes. From what you mentioned below, it appears that the granularity of phase shift can be quite small to be used to adjust skew within byte lane ? For those controllers that do not have read leveling, it gets a bit tricky. Regards Perry ======================================= Perry Qu IPD Design & Qualification, Alcatel-Lucent Canada Inc. 600 March Road, Ottawa ON, K2K 2E6, Canada Phone: 613-7846720 Fax: 613-5993642 Email: perry.qu@xxxxxxxxxxxxxxxxxx ======================================= ------------------------------------------------------------------------------ From: Hermann Ruckerbauer [mailto:hermann.ruckerbauer@xxxxxxxxxxxxx] Sent: Friday, April 16, 2010 2:30 AM To: Istvan Nagy Cc: Qu, Pingyu (Perry); si-list@xxxxxxxxxxxxx Subject: Re: [SI-LIST] Re: unbalanced setup/hold for DDR3 read Hello, this was already given for DDR2. Also here a training scheme could give the ideal position of the Strobe what is usually different from a 90 degree phase shift. When setting up I timing budget I usually split up setup and hold which often gives a negative number on one side for an ideal 90 degree shift. But when adding up the two numbers there is still positive margin left. and btw: this numbers are for AC/DC levels. when calculating back to Vref this will be not that asymetric any more (if it is at all...). Hermann EKH - EyeKnowHowHermann Ruckerbauerwww.EyeKnowHow.deHermann.Ruckerbauer@xxxxxxxxxxxxxxxxxxxxxxxxxxxx 194554 MoosTel.: +49 (0)9938 / 902 083Mobile: +49 (0)176 / 787 787 77Fax: +49 (0)3212 / 121 9008 schrieb Istvan Nagy: Hello, the answer is the read levelling feature in the DDR3 systems. check the JESD79-3x spec at jedec.org .This adjusts the read DLL on the DQS to balance the setup and hold margins. regards,Istvan NagyCCT ----- Original Message ----- From: "Qu, Pingyu (Perry)" <perry.qu@xxxxxxxxxxxxxxxxxx>To: <si-list@xxxxxxxxxxxxx>Sent: Thursday, April 15, 2010 7:54 PMSubject: [SI-LIST] unbalanced setup/hold for DDR3 read Hi, I made a small spreadsheet to help my understanding on DDR3 read timing for DQ/DQs. Data are extracted from JEDEC spec: DRAM speed period (ps) bit time (ps) tDQSQ(ps) tQH(ps) setup (ps) hold (ps)800 2500 1250 200 950 425 3251066 1875 937.5 150 712.5 318.75 243.751333 1500 750 125 570 250 1951600 1250 625 100 475 212.5 162.5 tQH = 0.38*Tck (avg) according to the spec. Setup/hold refers to the time window between DQ and DQs when they arrive at controller after a 90 degree phase shift (1/4 clock cycle), and calculated as: Setup = 0.25*Tck - tDQSQHold = tQH - 0.25*Tck This is purely static timing with no SI effect taken into account. From above, we can see there is significant unbalance between setup and hold requirement. If we take into account clock jitter and duty cycle distortion from controller clock output, it will be worse for the hold side, as they directly eats into hold margin. How does one balance the setup and hold so that we don't end up with lots of setup margin but no margin or negative margin for hold ? Wonder where this magic 0.38 number comes from ? Regards Perry------------------------------------------------------------------To unsubscribe from si-list:si-list-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field or to administer your membership from a web page, go to://www.freelists.org/webpage/si-list For help:si-list-request@xxxxxxxxxxxxx with 'help' in the Subject field List technical documents are available at: http://www.si-list.net List archives are viewable at://www.freelists.org/archives/si-list Old (prior to June 6, 2001) list archives are viewable at: http://www.qsl.net/wb6tpu ------------------------------------------------------------------To unsubscribe from si-list:si-list-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field or to administer your membership from a web page, go to://www.freelists.org/webpage/si-list For help:si-list-request@xxxxxxxxxxxxx with 'help' in the Subject field List technical documents are available at: http://www.si-list.net List archives are viewable at: //www.freelists.org/archives/si-list Old (prior to June 6, 2001) list archives are viewable at: http://www.qsl.net/wb6tpu No virus found in this incoming message.Checked by AVG - www.avg.com Version: 9.0.801 / Virus Database: 271.1.1/2812 - Release Date: 04/15/10 08:31:00 ------------------------------------------------------------------ To unsubscribe from si-list: si-list-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field or to administer your membership from a web page, go to: //www.freelists.org/webpage/si-list For help: si-list-request@xxxxxxxxxxxxx with 'help' in the Subject field List technical documents are available at: http://www.si-list.net List archives are viewable at: //www.freelists.org/archives/si-list Old (prior to June 6, 2001) list archives are viewable at: http://www.qsl.net/wb6tpu