>20mm is less than 140ps Tflight. That's awfully short as a maximum allowable trace length for 100MHz parts. I think you are >misinterpreting a value. I`m not sure if I got you right but that`s not the whole length (the whole length is between 60mm and 95mm) - it`s only the difference between e.g. D0 and D1... Bernd 2008/8/13 steve weir <weirsi@xxxxxxxxxx> > Bernd, at the speeds you are running you can do the timing analysis by > hand. If you are going to roughly estimate flight time for worst-case > delay, use 175ps / inch. This is a conservative value based on stripline > with an eR of 4.4. > > 20mm is less than 140ps Tflight. That's awfully short as a maximum > allowable trace length for 100MHz parts. I think you are misinterpreting a > value. > If you don't have the tools or expertise needed, you might think about > hiring someone who does. Your design sounds undemanding. A good consultant > shouldn't charge you too much to review your design and give you > bullet-proof constraints. > > Steve. > > bernd schuster wrote: > >> Hi, >> Unfortunately, I`ve no simulation tools... and therefore I read a lot of >> datasheets and application notes from different manufacutres. Their >> recommendation about different trace lengths are very often between 10mm >> and >> 20mm. Maybe that`s the best conditions on the one hand to be routable and >> on >> the other hand.... >> >> What about the skew and jitter calculation? I`m working with an ARM9 >> microcontroller with internal sdram controller and an external sdram. Is >> it >> correct that the clock length have to be as long as the longest databus >> length to get small skew >> >> >> >>> Of course, if you mean a synchronous interface, you may need a simulation >>> >>> >> and timing calculation to determine the trace lengths. >> The pcb layout software is able to calculate the normal length of a trace >> / >> not the manhatten length - but it should be enough >> >> best regards >> Bernd >> >> >> 2008/8/13 Benny Yan <zyan@xxxxxxxxxx> >> >> >> >>> Bernd, >>> Setup and hold margin are the results from the layout length, output >>> delay >>> and input setup and hold time requirements. >>> I think that you mean a source synchronous interface. In this case, the >>> absolute trace lengths are not the main constraint. >>> The setup margin 2ns and hold margin 0.8ns gives you a chance to tune the >>> length matching between clock and data traces. >>> Of course, if you mean a synchronous interface, you may need a simulation >>> and timing calculation to determine the trace lengths. >>> Or simply, you may use 1ns per 6inch to do a rough estimation, but don't >>> forget to reserve enough margin. >>> >>> Benny Yan >>> www.iometh.com >>> >>> -----Original Message----- >>> From: si-list-bounce@xxxxxxxxxxxxx [mailto:si-list-bounce@xxxxxxxxxxxxx] >>> On Behalf Of bernd schuster >>> Sent: Wednesday, August 13, 2008 5:13 PM >>> To: si-list@xxxxxxxxxxxxx >>> Subject: [SI-LIST] min/max trace length >>> >>> Hi, >>> I often read minimum and maximum trace lengths in datasheets of sdram >>> chips >>> (for example). As I figured out the length depends on the setup margin >>> and >>> hold margin. >>> >>> If I have a setup margin of 2ns and hold margin of 0.8ns (e.g.) - which >>> formulas will tell me the min. and max. trace length? The system is >>> working >>> at 100MHz with a fall time / rise tim of 2ns. >>> >>> How do I have to modify the formula when I want to calculate the timing >>> for >>> an external flash memory (without clock traces)? >>> >>> best regards >>> Bernd >>> >>> >>> ------------------------------------------------------------------ >>> 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 >>> or at our remote archives: >>> http://groups.yahoo.com/group/si-list/messages >>> 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 >> or at our remote archives: >> http://groups.yahoo.com/group/si-list/messages >> Old (prior to June 6, 2001) list archives are viewable at: >> http://www.qsl.net/wb6tpu >> >> >> >> > > > -- > Steve Weir > Teraspeed Consulting Group LLC 121 North River Drive Narragansett, RI 02882 > > California office > (866) 675-4630 Business > (707) 780-1951 Fax > > Main office > (401) 284-1827 Business (401) 284-1840 Fax > Oregon office > (503) 430-1065 Business > (503) 430-1285 Fax > > http://www.teraspeed.com > This e-mail contains proprietary and confidential intellectual property of > Teraspeed Consulting Group LLC > > ------------------------------------------------------------------------------------------------------ > Teraspeed(R) is the registered service mark of Teraspeed Consulting Group > LLC > > ------------------------------------------------------------------ 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 or at our remote archives: http://groups.yahoo.com/group/si-list/messages Old (prior to June 6, 2001) list archives are viewable at: http://www.qsl.net/wb6tpu