[SI-LIST] Re: source synchronous constraint

  • From: "Keven Hui" <khui@xxxxxxxx>
  • To: <zanglinyuan@xxxxxxxxxx>, "Scott McMorrow" <scott@xxxxxxxxxxxxx>
  • Date: Mon, 26 Aug 2002 23:28:35 -0700

Zanglinyuan,
You're missing two very important pieces of information of the
interface.
One is the clk/strobe relationship to the data.
If they are 90 degrees apart, then all that means is the data
can be 90 degrees +/- 1ns from the clk/strobe at the driving end.
At the receiving end, you'll need 2.5ns setup and 0.5ns hold time
at the pin level (It seems strange that setup and hold time requirement
are so different). Total required timing budget for the driving and
receiving chips including packages is 5ns.

The other important information is the data rate. If you are running at
100Mb/s, the bit width is 10ns. The driving and receiving circuits take
5ns of it and you have 5ns left for the board routing. In this case, you
have
plenty of margin and should have no problem routing them.

You'll need to figure out what the total timing budget that is available for
the board/off-chip before you can decide what the routing requirements are.
Hope this helps.
Kevin

----- Original Message -----
From: "zanglinyuan" <zanglinyuan@xxxxxxxxxx>
To: "Scott McMorrow" <scott@xxxxxxxxxxxxx>
Cc: <si-list@xxxxxxxxxxxxx>
Sent: Monday, August 26, 2002 8:20 PM
Subject: [SI-LIST] Re: source synchronous constraint


>
>
> Hi. Scott
> It is a typical source synchronous system .
>
> as follows:
> ____                  _____
> |       |  strobe     |          |
> |       |------------|          |
> |TX  |                 |  RX  |
> |       | data         |          |
> |___ |----------- |_____|
>
> TX----transceiver
> RX----recevier
>
> The TX parameter is the transceiver ouput  data relative to strobe.
> The  RX parameter is the receiver input requirement for data relative to
strobe.
> The strobe's active edge is rising edge.
>
> The key problem is the tranceiver ouput parameter does't match the
receiver's input requirement ,
> how to deal with  PCB'S routing ?
>
> (TX:setuptime=1ns,holdtime=1ns
> RX:setuptime=2.5ns,holdtime=0.5ns )
>
>
> thanks
>
>
> ----- Original Message -----
> From: Scott McMorrow <scott@xxxxxxxxxxxxx>
> To: <zanglinyuan@xxxxxxxxxx>
> Sent: Tuesday, August 27, 2002 12:23 PM
> Subject: Re: [SI-LIST] source synchronous constraint
>
>
> > Zanglingyuan,
> >
> > It is not clear what your Tx parameters are.  Is this a double data rate
> > source synchronous system where the setup and hold times are relative to
> > the Tx strobe/clock?  If so, what edge of the strobe is the active edge.
> >  Are the Rx setup and hold parameters relative to the same strobe/clock
> > edge?
> >
> > regards,
> >
> > scott
> >
> >
> > --
> > Scott McMorrow
> > Teraspeed Consulting Group LLC
> > 2926 SE Yamhill St.
> > Portland, OR 97214
> > (503) 239-5536
> > http://www.teraspeed.com
> >
> >
> > zanglinyuan wrote:
> >
> > >Hi:
> > >I am designing some source synchronous system,and need to make PCB
routing constraint.
> > >However,the timing parameter for tranceiver and reciever does not match
each other,
> > >for example :
> > >TX:setuptime=1ns,holdtime=1ns
> > >RX:setuptime=2.5ns,holdtime=0.5ns
> > >
> > >even so,I don't think the system won't work if we just route the
clk/data's PCB length within
> > >some tolerance,because the datasheet does't give the valid data time
which is very important for
> > >the PCB constraint to be made.
> > >
> > >what's the right way  to deal with such case? that's how to make the
PCB routing constraint for this case?
> > >
> > >Thanks a lot in advance.
> > >
> > >
> > >
> > >------------------------------------------------------------------
> > >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
> > >
> > >
> > >
> > >
> > >
> >
> >
> ------------------------------------------------------------------
> 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
>
>

------------------------------------------------------------------
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
  

Other related posts: