AR# 23469: 10.1 ISE - Project Navigator does not show a VHDL package or module added to the project in the hierarchy or sources window
10.1 ISE - Project Navigator does not show a VHDL package or module added to the project in the hierarchy or sources window
When an HDL file is added to the project, the sources window for the project does not show the package file. The file is accepted and shows the proper associations (e.g., Synthesis/Imp + Simulation). However, the source does not appear in the source hierarchy. If the added file is instantiated in another file, a "?" appears in the hierarchy for the file indicating that the module is undefined. In some cases, the user receives an error message stating there is no design unit in the file. The file is treated as a black box in synthesis.
Syntax errors in the instantiation or declaration of entities and modules can cause this issue. Make sure your entity/module declarations and instantiations are properly written. Check for missing parenthesis, commas, semi-colons, or other syntax erros that will inhibit Project Navigator from correctly reading through the entity/module instantiations and declarations.
This problem will occur if a commented section of the source file has the text "synopsys translate_off." When the text "synopsys translate_off" immediately follows a comment, it is considered a meta comment command, which switches off parsing for the rest of the file (or until a corresponding "synopsys translate_on" command is found).
The HDL parser incorrectly recognizes "synopsys translate_off" as a meta comment when it appears in a commented section of text other than directly after a comment. This problem can cause an entire design or a significant portion of a design to be ignored by the parser.
This issue also affects the "synopsys translate_on" text.
To work around this issue, either change the text comment to avoid the meta comment syntax or use the custom compile file. A custom compile file will not make the source show up in the hierarchy but will pass the correct file to the synthesis process if it is not the top-level source.
This problem has been fixed in the latest 10.1 Service Pack available at: