![]() |
|
![]() |
|
Answers Database
M1.4 MAP/PAR: PAR ERROR:baspr - SSLex0105e: Invalid token, Line 13, Offset 38, ,
Record #2915
Product Family: Software M1.4 MAP/PAR: PAR ERROR:baspr - SSLex0105e: Invalid token, Line 13, Offset 38, , Problem Description: Urgency: Standard Reference #: 100701 General Description: When the Config symbol has a UserString containing a comma character, the parser fails with the error: ERROR:baspr - SSLex0105e: Invalid token, Line 13, Offset 38, , The following errors are also issued: ERROR:baspr:40 - Failed to parse Preference file. RROR:bastw:69 - The PCF file could not be loaded Solution 1: This type of error usually indicates a syntax error of some sort in the PCF file. In this case, the invalid token is a misplaced comma on the line indicated in the .pcf file. The only way to determine the specific cause of the problem is to submit the input design files, including schematics and .UCF constraint files, so that it can be verified that constraints are being translated correctly at every step of the flow. End of Record #2915 - Last Modified: 07/01/99 08:25 |
| For the latest news, design tips, and patch information on the Xilinx design environment, check out the Technical Tips! |