Answers Database


Map 1.5i, 2.1i Map - FATAL_ERROR:basut:basutcname.c:410:1.8; Utilities:UtilCname.imp.c:400:1.1.2.2: Maximum name length exceeded


Record #6229

Product Family: Software

Product Line: FPGA Implementation

Product Part: map

Product Version: 2.1i

Problem Title:
Map 1.5i, 2.1i Map - FATAL_ERROR:basut:basutcname.c:410:1.8;
Utilities:UtilCname.imp.c:400:1.1.2.2: Maximum name length exceeded



Problem Description:
Urgency: standard

General description: Cases have been seen where map will fail due to unusually
long (2047 characters) component names with the following errors:

Map1.5i: FATAL_ERROR:basut:basutcname.c:410:1.8 - maximum name length
exceeded

or

Map2.1i: Fatal_Error:Utilities:UtilCname.imp.c:400:1.1.2.2 - Maximum
name length exceeded.


Solution 1:

Excessively long component names will exceed the maximum name length
allowed in map. This lenth differs from the length allowed in ngdbuild.
This could be caused by an unusually large amount of heirarchy, but is typically a problem with synthesis tools which sometimes create long, non-sensical
names where a particular string is repeated many times.




End of Record #6229 - Last Modified: 06/08/99 12:33

For the latest news, design tips, and patch information on the Xilinx design environment, check out the Technical Tips!