UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Participant deritha-06
Participant
9,358 Views
Registered: ‎04-15-2010

change fifo depth problem(cont)

Hi,

 

Still the map problem..........

 

Updating timing models...
ERROR:Pack:2310 - Too many comps of type "RAMB36_EXP" found to fit this device.
ERROR:Map:237 - The design is too large to fit the device.  Please check the Design Summary section to see which resource requirement for your design exceeds the resources available in the device. Note that the number of slices reported may not be reflected accurately as their packing might not have been completed.

   NOTE:  An NCD file will still be generated to allow you to examine the mapped
   design.  This file is intended for evaluation use only, and will not process
   successfully through PAR.

 

 

How to solve this problem?

 

 

0 Kudos
11 Replies
Participant deritha-06
Participant
9,356 Views
Registered: ‎04-15-2010

Re: change fifo depth problem(cont)

I'm using FIFO Generator v5.1 in the design part.

 

As the datasheet's introduction, FIFO depths could up to 4,194,304.

 

Now I change the FIFO depth from 65536 to 262144. I don't know why these kind of errors output.........

 

Any suggestion?

0 Kudos
Participant deritha-06
Participant
9,346 Views
Registered: ‎04-15-2010

Re: change fifo depth problem(cont)

The parameters used in the fifo generator:

 

 

fifo-generator1.PNG
0 Kudos
Participant deritha-06
Participant
9,345 Views
Registered: ‎04-15-2010

Re: change fifo depth problem(cont)

 
fifo-generator2.PNG
0 Kudos
Participant deritha-06
Participant
9,344 Views
Registered: ‎04-15-2010

Re: change fifo depth problem(cont)

 
0 Kudos
Participant deritha-06
Participant
9,343 Views
Registered: ‎04-15-2010

Re: change fifo depth problem(cont)

 
fifo-generator3.PNG
0 Kudos
Participant deritha-06
Participant
9,342 Views
Registered: ‎04-15-2010

Re: change fifo depth problem(cont)

 
fifo-generator4.PNG
0 Kudos
Participant deritha-06
Participant
9,341 Views
Registered: ‎04-15-2010

Re: change fifo depth problem(cont)

 
fifo-generator5.PNG
0 Kudos
Participant deritha-06
Participant
9,340 Views
Registered: ‎04-15-2010

Re: change fifo depth problem(cont)

 
fifo-generator6.PNG
0 Kudos
Instructor
Instructor
9,326 Views
Registered: ‎08-14-2007

Re: change fifo depth problem(cont)

The error message seemed pretty clear to me.  The device you are using does not

have enough block RAM bits to implement the FIFOs you have generated.  Even one

of these FIFOs would require 4,194,304 bits.  That would mean 128 36K block RAM's.

 

Does your part have 128 36K block RAMs?

-- Gabor
0 Kudos
Participant deritha-06
Participant
3,601 Views
Registered: ‎04-15-2010

Re: change fifo depth problem(cont)

Sorry. I'm trying to modify the design made by other guys.

 

1. Any way to check the block RAM's number?

 

2. Any other way to solve the problem? Such as using the Distributed RAM?

0 Kudos
Instructor
Instructor
3,596 Views
Registered: ‎08-14-2007

Re: change fifo depth problem(cont)

If you use the ISE Navigator, you can find the map report via "Design Summary/Reports" which looks

like a green greek letter sigma in the tool bar.  Otherwise open up your map report file, which will

have a .mrp suffix.  This should list all of the resources used in the design as well as how many

are available in the device.  In the case of your block RAMs it should indicate that they are

"overmapped" and you can see by how much.  Generally speaking, unless you are using

a very large device with a lot of the fabric unused, you won't be able to make up the difference

in RAM bits using distributed memory.  Also note that very large distributed memories will

use a lot of routing resources and run very slow.

 

Regards,

Gabor

-- Gabor
0 Kudos