How to get Help?
GUI mode
Just press "F1" key in main window to pop up the XTop manual.Or, press "F2" key in configure parameters window to pop up the manual page.
Shell mode
Type "help" command to display the detail explanation of command.Or, type "help_parameter" command to display the detail explanation of parameter.
In the search window, after selecting Cell/Pin/Net, search for *, can only find the objectsm at the top level?
The search matches the cross-layer, but the performance is currently limited to the first 30,000 matching results. When the case is large, the top level objects may exceed 30,000. The results are all top level.
If you want to search for a certain piece of pin/cell/net, please specify the search keywords.
Why in the search window, after searching for A/clk or A/* after selecting Pin, it can't be found?
In the search window, search for A after selecting Cell can be found; but after searching for A/clk or A/* after selecting Pin, it can't be found. In fact, not all can not be found, some cells have special characters, Cell type and Pin type are not the same:
For example, the cell name is similar to xxxx/xxxx[0]_aaa/bbb[1][2], with Cell type Should be automatically added before the [] backslash, you can search to, can not be used with Pin type, manually add a backslash before [], you can find. This shows that Pin type does not have automatic fault tolerance processing for the name; there is also a cell name of xxx/xxx/xxx\/latch, which can be found by using Cell type to check xxx/xxx/xxx/latch, but use Pin type to check xxx/ Xxx/xxx\/latch/* or xxx/xxx/xxx\\\/latch/* or xxx/xxx/xxx/latch/*, can not find.
Moved the working directory, and then gave an error when it was opened
The error message is as follows:
Error: Something mismatch while recovering, please check all the messages
Reason: View the information in the log, found that the idb file can not be found, and previously moved the idb path, and the workspace saves the path of the idb, and does not store the idb information, so can not find.
Solution: Reload the idb file into the idb path information saved in the workspace.
Expand: I tried the lef file, and so on. Other sta data and design information do not have this problem.
What is the characteristic of XTop inthe advanced sensitive (12nm) routing sensitive case?
1) SI cannot be well evaluated;
2) weak drive + SI is not well evaluated;
3) Winding effects are difficult to assess;
4) The cost of DRC keep can't be repaired;
5) The influence of SI + routing causes the timing to be basically inaccurate.
How to redirect outputs to file?
Use redirect command to write the command output into file:
xtop> redirect -file fileName {cmd}
Note, for none TCL command, it cannot redirect its output, unless modifying TCL.
For work-around, use exec Instead:
xtop> redirect -file fileName {exec cmd}
What is the flow of XTop top flatten session writing sub design data?
The specific process is as follows:
1) First set the environment variable to the newly updated XTop
2) Dump data from the PT, using dumpPtTimingFiles.tcl,
a) Comment out the line report_pba_data_for_icexplorer
b) report_scenario_data_for_icexplorer, adds option: -only_hier_path $sub_sys_hier_path.
Here hier path refers to the instance hier path of this subsystem in top design.
xtop> report_scenario_data_for_icexplorer -scenario_name func_slow \
-dir ./timing_files_top -only_hier_path U_TEMO_TOP
3) Normal operation of XTop
Note: that this process has the following risks: 1) Timing data on the port of the subsystem will be lost; 2) The settings of skip iocannot be supported; 3) XTopcan't read pbatiming report; 4) Because there is no way to directly compare with PT data, it needs to be transferred, so debugging may be difficult.
====== 返回目录 ======
<<< 上一章：Reports & Debugging