![]() |
|
![]() |
|
Answers Database
XSimMake, XDraw: "Could not access Sheet 1 of SCHEMATIC <top>." Powerview 5.3.2
Record #687
Product Family: Software ERROR MESSAGE: Writing new simulation schematic. Please wait.... LIST OF ERRORS FOUND for XDRAW -------------------------------- ERROR 5: Could not access Sheet 1 of SCHEMATIC <top>. 1 Errors and 0 Warnings occurred during processing. ERROR 7: Command [xdraw -i <top> -o s<top> -a s<top> ] failed to execute properly. When running XSimMake to create a functional simulation network, XDraw will be used to redraw the design schematics. In the case where the there are no special components, only the top level schematic will be redrawn. PROBLEM: When trying to run XSimMake functionally on a design created with Powerview V5.3.2 or V6.0, the version of the schematic is 5.1. XDraw thinks the schematic is corrupted. To verify this, look at the XDRAW.OUT file. The following is an example of what XDRAW will report: File <top> has been corrupted. ========> V 51 Line 1 *** Error #35 *** primary:<top>.1 read CAUSE: XDraw was compiled with older versions of the Viewlogic tool libraries which do not recognize version 5.1 schematics. Solution 1: Because the Powerview tools can use schematics created using previous versions, the V 51 line can be changed in the schematics and symbols for the design being processed. After copying all the schematics and symbols to a backup directory, modify the schematics and symbols in the sch and sym sub-directories in the following manner: --- first three lines of schematic before change --- V 51 K 165102488100 mytest Y 0 ---------------------------------------------------- --- first three lines of schematic after change ---- V 50 K 165102488100 mytest Y 0 ---------------------------------------------------- Then, to ensure that the changes will effect future processing, remove all the files located in the wir sub-directory and run the Viewlogic check program to recreate them. Example: check -p mytest End of Record #687 - Last Modified: 01/14/97 10:13 |
| For the latest news, design tips, and patch information on the Xilinx design environment, check out the Technical Tips! |