In most cases where there is a central clock distribution, there is no need to match trace lengths of address, data, and control signals. They just need to be long enough (no hold time violations) but not too long (no setup time violations); so you should be thinking about them that way, rather than with the objective to match lengths. (But you would want to match the clock trace lengths.) On the other hand, you might be concerned about matched lengths if the bus uses some sort of local strobes, where you need to match the address/data delays to those of the strobes. If everything is very well controlled, and you know you can count on incident wave switching, then it's possible to have very little delay difference between identical length traces on the same layer. But putting a limit on the delay difference is not so easy. I've seen guesstimates of 10% of the total flight time range. For example, if the board vendor says you'll see 140-190 ps/inch on some layer, that's 50 ps/inch total raw delay variation (incident wave, board to board); so one might estimate 5 ps/inch difference between IDENTICAL traces on the SAME layer of the SAME board. Regards, Andy ------------------------------------------------------------------ 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 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