Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

Asynchronous FIFO vs Multi cycle path (MCP) clock domain crossing

Status
Not open for further replies.

abhinavpr

Junior Member level 2
Joined
Jun 19, 2013
Messages
21
Helped
0
Reputation
0
Reaction score
0
Trophy points
1
Activity points
205
Hi,
Can anybody tell me the advantages of using Asynchronous FIFO when we can do the clock domain crossing using multicycle path cdc (synchronizing control enable signal and holding the input data for mulitple cycles ). why go for the pains of creating a fifo and verifying it also adding significant gate count to the design.


-abhinavpr
 

In this case you need to make the source logic to wait and check till it gets synced into destination logic, if you are transferring data in bursts then its lot off overhead on Bandwidth requirements. Fifo does in burst and having an extra buffer depth will continue with write burst. Thus very limited back pressure.
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top