[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [partial-reconfig] Problems with MAP in Active phase



Thanks Umar for your suggestions. I will try to place the bus macros on even
rows and see if it helps.

Another point I notice is that my design has Pseduo logic (when I see the
floorplan) as follows:
1. The module (admxrcif) drives a 32 bit (inout) signal,  which is also 
   driven out of the top level entity onto to the pins of the FPGA. 
   The pin locations are fixed by the UCF file. There is a PSUEDO TBUF 
   inserted for each of these signals. Is this a problem ? If so, how can I
   prevent this?

2. In both the modules, all the input signals have a PSUEDO DRIVER. These
   nets are between the bus macro and the in port of the module. I remember
   reading that pseudo drivers need to be removed, does it apply to this case?
   How can I remove this insertion? 

   Thank you very much.

Best Regards,
Devadutt

Master's student
Computer Science and Engineering
Indian Institute of Technology - Delhi




On Sun, May 08, 2005 at 10:46:53AM +0500, Umar Mushtaq wrote:
> The following *might* help... you might call it nitpicking, and I might
> have been unable to see the real reason for the errors you are getting,
> but here goes:
> 
> 1). Try placing the BMs on even-numbered rows... for some reason designs
> fail when BMs are placed on odd-numbered rows... While I do recall
> reading something about this somewhere, it might just be a rule of
> thumb, but you never know if this is what is causing the problems...
> 
> 2). Use the MODE = RECONFIG for all modules, whether reconfigurable or
> not... I didn't find the constraint for the "admxrcif" module... 
> 
> 3). PACE usually messes up the resource assignment for BRAMs and
> MULTs... for a BRAM column for instance, it repeats the assignment of
> that column over and over again... in your case this isn't so, because
> each BRAM and MULT column is assigned once, but it would be so much more
> simpler if for the larger module you had the following:
> 
> RAMB16_X1Y0:RAMB16_X5Y15,
> MULT18X18_X1Y0:MULT18X18_X5Y15 ;
> 
> This of course isn't an error, and the constraints would work the way
> they are in your .ucf file, but it is always good to keep things
> simple... also, I have found it a good idea to copy the constraints into
> a text file before modifying the .ucf file in PACE, for the reason I
> mentioned earlier...
> 
> :)
> 
> Sincerely,
> Umar
> ___________________________
> partial-reconfig mailing list
> partial-reconfig@itee.uq.edu.au
> Mailing List Archive : http://www.itee.uq.edu.au/~listarch/partial-reconfig/
___________________________
partial-reconfig mailing list
partial-reconfig@itee.uq.edu.au
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/partial-reconfig/