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!

Showing results for 
Search instead for 
Did you mean: 
Participant fhknapp44
Registered: ‎02-25-2015

ISE 14.7 Implementation, MAP function

OK, I have a problem with the Implementation phase. I was getting a conflict ERROR from MAP. Two different pads, A18, and H18 were conflicting for the same IOB. While this should not be possible, the provided details in the provided Summery just refereed to the H18 pad. For the first few tries to identify this problem this Summary was provided in the "following details". After about 5 iterations of the MAP function these details are no longer being provided.

The nature of this 'problem' suggests it is a installation problem but I had great troubles getting a license problem fixed and I do not want to deal with that landmine again.

Pad H18 is defined as an I/O, bi-directional data type IOB, and pad A18 is a input only IOB. Another impossible problem.

I also use 'Plan Ahead' and it took the database with no problem and no flags were raised.

This design does not have tight timing constrains. I have at least several micro-seconds timing margins.

Any suggestions?


0 Kudos