2. 技术支持
  3. AR# 6314: 3.1i Virtex MAP - FATAL_ERROR:basmm:basmmfact.c:1349:1.84 - Unknown pad pin type

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

解决方案

1

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:

SYM,N00674_PAD,UPAD
PIN,UPAD,I,N00674
END

for every unbonded EXT statement:

EXT,N00674,U

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.


#!/usr/local/bin/perl5
while (<>){
chomp;
@fields =split(/,/);
if ($fields[0] eq "EXT" && $fields[2] eq "U^M") {
$net="$fields[1]";
$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

2

This problem is scheduled to be fixed in the 3.1i release, which
is scheduled for May, 2000.
AR# 6314
日期 06/13/2002
状态 Archive
Type 综合文章