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!

Page Bookmarked

AR# 6314

3.1i Virtex MAP - FATAL_ERROR:basmm:basmmfact.c:1349:1.84 - Unknown pad pin type


Keywords: fatal error, Virtex, MAP, unknown pad pin,

Urgency: Standard

General Description:
The following error occurs when an .xnf-based design contains unbonded pads
and is re-targeted to a Virtex device:

FATAL_ERROR:basmm:basmmfact.c:1349:1.84 - Unknown pad pin type



The solution is to replace all unbonded EXT records with a UPAD symbol.

The workaround involves modifying the .xnf file by substituting an
unbonded pad symbol:


for every unbonded EXT statement:


The following Perl script upad.pl can be used to make the substitutions.
Keep in mind that the Cntl-M characters will be corrupted by the cut and paste
and should be re-entered. The path to the Perl exec will need to be modified
for the user's environment. WorkStation users should remove the Cntl-M (^M)
from the string matching test in line 5, as the Cntl-Ms only appear in PC-generated
.xnf files.

while (<>){
@fields =split(/,/);
if ($fields[0] eq "EXT" && $fields[2] eq "U^M") {
$pad="${net}_PAD" ;
print "SYM,$pad,UPAD^M\n";
print "PIN,UPAD,I,$net^M\n";
print "END^M\n";
else {
print "$_\n" ;

The command to run this script is:

upad.pl orig.xnf > hacked.xnf


This problem is scheduled to be fixed in the 3.1i release, which
is scheduled for May, 2000.
AR# 6314
Date 06/13/2002
Status Archive
Type General Article