Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Message

[lpc2000] 100 MHz clock using LPC2138

2005-06-14 by sudip nag

Hi,
My requirement is to interface Gigabit ethernet transceiver (>=500Mbps or >=64 mega bytes per second). The data feeding technique is to supply 8 bit parallel data along with a clock that must exceed 64 MHz (64 mega bytes per second). Here I must synchronize each cycle of clock with data byte.  So I need to generate such high clock frequency.
Please suggest.
 
Sudip

Bruce Paterson <bruce@...> wrote:

Without knowing your exact requirements, or whether a common multiple 
can be found which lets you do all you need, why not run both chips from 
the same crystal clock circuit ?
I'm assuming here you mean the data carrier is 100MHz, not the actual 
data rate (which of course would not be possible from a slower LPC 
unless you have external FIFO's or something).
-- 
Cheers,
Bruce
-------------------------------------------------------------------
     /\\\/\\\/\\\    /   /      Bruce Paterson
    /  \\\ \\\ \\\  /   /    Senior Design Engineer
   /   /\\\/\\\/\\\/   /   8 Anzed Court, Mulgrave, Vic, 3170
  /   /  \\\ \\\ \\\  /  PO Box 4112, Mulgrave, Vic, 3170, Australia
/   /    \\\/\\\ \\\/   Ph: +61 3 8561 4232   Fax: +61 3 9560 9055
       Tele-IP Ltd.      Email: bruce@...    Icq: #32015991
                         WWW:   http://www.tele-ip.com       VK3TJN
-------------------------------------------------------------------



---------------------------------
Yahoo! Groups Links

   To visit your group on the web, go to:
http://groups.yahoo.com/group/lpc2000/
  
   To unsubscribe from this group, send an email to:
lpc2000-unsubscribe@yahoogroups.com
  
   Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. 


		
---------------------------------
 Too much spam in your inbox? Yahoo! Mail gives you the best spam protection for FREE!
http://in.mail.yahoo.com

[Non-text portions of this message have been removed]

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.