Sign in

username:

password:



Not a member?

Search Comp.Arch.FPGA



Search tips

fpga by Keywords

Altera | ASIC | CPLD | Cyclone | DCM | DDR | DSP | Ethernet | ISE | JTAG | Linux | LVDS | Microblaze | ML310 | Modelsim | NIOS | OPB | PCI | Quartus | RocketIO | SDRAM | Spartan | Spartan3 | SRAM | Stratix | Verilog | VHDL | Virtex | Virtex-4 | Virtex-II | Xilinx | XST

Ads

See Also

DSPEmbedded SystemsElectronics

Comp.Arch.FPGA | Xilinx' partition flow in ISE12.1

There are 2 messages in this thread.

You are currently looking at messages 0 to 2.

Xilinx' partition flow in ISE12.1 - Sean Durkin - 2010-05-27 03:44:00

Hi *,

has anyone had any success with the "new" partion flow in ISE12.1?

I've been fiddling around with this for a few hours, but whatever I try,
the design fails to even finish routing on the first pass as soon as I
enable partitions.

The error messages vary, mostly it's complaining about hundreds of
unroutable nets and just quits.

I've read ug748, which mentions several prerequisites that need to be
met, all of which I believe I do meet. One that is not mentioned in the
documentation is that you need to set "keep_hierarchy" to YES during
synthesis, or it won't even find the modules you want to declare as
partitions. This at least seems kind of "logical", but still it should
be in the documentation...

I remember in earlier ISE versions they mentioned that the partition
flow had problems with GENERATE statements and GENERICs, both of which I
do use extensively. Could that be the problem?

Success or failure stories, anyone? :)

cu,
Sean

-- 
Replace "MONTH" with the three-letter abbreviation of the current month
and the two-digit code for the current year (simple, eh?).
______________________________
Join the blogging team on FPGARelated.com and earn rewards! Details Here.



Re: Xilinx' partition flow in ISE12.1 - Kate Kelley - 2010-07-20 14:00:00

Hey Sean,

Sorry for the late post and my guess is you have either given up or figuredout how to do this.  Unroutes should not be happening by just addingPartitions.  If you want to try again, you might want to look at the numberof INFO and WARNING messages about constants on inputs and/or outputs andalso the number of unconnected outputs.

The goal for Partitions is to keep the implementation results regardless ofchanges outside of the Partition. For that reason, we do not optimize anyconstants or unusued outputs across the Partition boundary. Often, this cancause more logic resulting in lower QoR.  Sometimes this can causeunroutes. We are looking at changing this in the future.  

If you don't think this is the issue, I would really like to see the designso we can improve our flow.  The best way to do this is to file a webcaseso we can look at it.

The best documentation for the 12.1 flow is the HD Methodology Guide.  Itis located athttp://www.xilinx.com/support/documentation/sw_manuals/xilinx12_1/Hierarchical_Design_Meth
odology_Guide.pdf.

Thanks,
Kate

	   
					
---------------------------------------		
Posted through http://www.FPGARelated.com
______________________________
Join the blogging team on FPGARelated.com and earn rewards! Details Here.