Answers Database
1.5i, 2.1i Virtex Map - FATAL_ERROR:basmm:basmmfact.c:1349:1.84 - Unknown pad pin type
Record #6314
Product Family: Software
Product Line: FPGA Implementation
Product Part: map
Product Version: 1.5i
Problem Title:
1.5i, 2.1i Virtex Map - FATAL_ERROR:basmm:basmmfact.c:1349:1.84 - Unknown pad pin type
Problem Description:
The error will occur when an .xnf based design contains unbonded pads
and is re-targetted to a Virtex device.
The work around is replace all unbonded EXT records with a UPAD symbol.
Solution 1:
A work around is available for this problem. It 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 charachters will be corrupted by cut and past
and should be re-entered. The path to the perl exec will need to be modified
for the user's environment. Work Station users should remove the Cntl-M (^M)
from the string matching test in line 5 because the Cntl-M's only appear iin
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
Solution 2:
This bug has been assigned to be fixed inthe next (as yet unnamed) release following 2.1i.
End of Record #6314 - Last Modified: 06/26/99 14:17 |
