cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Explorer
Explorer
5,957 Views
Registered: ‎10-29-2008

Map failed with Pack:2811 error after enabling Global Optimization

I am using ISE/EDK 14.2 with a Spartan-6

 

My project has been building fine and I had just completed a successful build and the code runs fine in the Spartan-6.

 

Without making any other changes I turned on "Global Optimization"  for Map and did a "Rerun All".

 

Map failed with Pack:2811 error.

 

It complained about several of my signals one example is below.

 

ERROR:Pack:2811 - Directed packing was unable to obey the user design
   constraints (LOC=V17) which requires the combination of the symbols listed
   below to be packed into a single IOB component.

   The directed pack was not possible because: More than one pad symbol.
   The symbols involved are:
   	BUF symbol "o_DBG_0_OBUF" (Output Signal = o_DBG<0>)
   	PAD symbol "o_DBG<0>" (Pad Signal = o_DBG<0>)
   	PAD symbol "o_DBG<1>" (Pad Signal = o_DBG<1>)
   	PAD symbol "o_DBG<2>" (Pad Signal = o_DBG<2>)
   	PAD symbol "o_DBG<3>" (Pad Signal = o_DBG<3>)
   	PAD symbol "o_DBG<4>" (Pad Signal = o_DBG<4>)
   	PAD symbol "o_DBG<5>" (Pad Signal = o_DBG<5>)
   	PAD symbol "o_DBG<6>" (Pad Signal = o_DBG<6>)
   	PAD symbol "o_DBG<7>" (Pad Signal = o_DBG<7>)
   	PAD symbol "o_DBG<8>" (Pad Signal = o_DBG<8>)
   	PAD symbol "o_DBG<9>" (Pad Signal = o_DBG<9>)
   	PAD symbol "o_DBG<10>" (Pad Signal = o_DBG<10>)
   	PAD symbol "o_DBG<11>" (Pad Signal = o_DBG<11>)
   	PAD symbol "o_DBG<12>" (Pad Signal = o_DBG<12>)
   	PAD symbol "o_DBG<13>" (Pad Signal = o_DBG<13>)
   	PAD symbol "o_DBG<14>" (Pad Signal = o_DBG<14>)
   	PAD symbol "o_DBG<15>" (Pad Signal = o_DBG<15>)

 My design runs just fine, why does turning on this optimization cause an issue?

 

I would like to enable the optimization if possible.

 

Any suggestions?

 

Thanks.

0 Kudos
6 Replies
Highlighted
Professor
Professor
5,954 Views
Registered: ‎08-14-2007

Re: Map failed with Pack:2811 error after enabling Global Optimization

This looks like an error I've seen before.  It happens when you have multiple output ports

driven by the same logical signal.  Somehow with global optimization turned on, the

output buffers get merged into one and then can't be placed into multiple IOB's.  One

workaround is to make sure that each bit of your o_DBG vector has a different function

so optimization cannot merge them.

 

-- Gabor

-- Gabor
0 Kudos
Highlighted
Explorer
Explorer
5,950 Views
Registered: ‎10-29-2008

Re: Map failed with Pack:2811 error after enabling Global Optimization

Ok, this is starting to sound related to the LOC and UCF bug workaround I had to do a while back.

0 Kudos
Highlighted
Visitor
Visitor
5,925 Views
Registered: ‎10-26-2012

Re: Map failed with Pack:2811 error after enabling Global Optimization

Check there any BEL constraints on the LUTs. if there any then Remove these allowed it to go through the tool.

 
An alternative workaround would be to use LUT5 and LUT6 instead of LUT6_2.
0 Kudos
Highlighted
Xilinx Employee
Xilinx Employee
5,768 Views
Registered: ‎08-14-2012

Re: Map failed with Pack:2811 error after enabling Global Optimization

hi,

 

check whether two pins are locked at the same location.

 

 

 

0 Kudos
Highlighted
Newbie
Newbie
5,269 Views
Registered: ‎09-28-2013

Re: Map failed with Pack:2811 error after enabling Global Optimization

Duplicate LOC assignments in the UCF file.  Turned out to be the cause of Pack:2811 error in my case.  Thanks for the tip!

 

Len

Highlighted
Newbie
Newbie
781 Views
Registered: ‎09-24-2018

Re: Map failed with Pack:2811 error after enabling Global Optimization

Same here -  cause was duplicate pin assignments in UCF. Whoops. Too bad there wasn't a LINT for UCF's.

0 Kudos