Error Messages:
ERROR #8003 More than one page is numbered 1.
Solution:
You can modify the title block by double-clicking it in the lower right corner of the schematic.
The title block of the schematic can be modified by double-clicking on the title block in the right corner of the schematic, and modifying its properties, mainly the page count and page number.
An error is reported in the schematic diagram of cadence when running DRC, and the error information is as follows.
[cadence-DRC]error: Possible pin type conflict GND/VCC Power Connected to OutputSolution:
Step 1: run DRC to find and analyze the error source
Run DRC. After the above error is output, the green circle is error. Click it to display the error message. We can see the green error reporting circle page. Clicking on the pin attribute is connected to the pin attribute output (the output attribute will generate the VCC on the previous page, resulting in the device sharing a VCC network), but normally, the pin attribute is passive/power. Therefore, we manually change the properties of the device pin to normal.
Step 2: Change [edit part] to power attribute
Select the power component, right-click and select [edit part] to enter pin modification in schematic library mode (it is impossible to change pin attribute in this mode), and change output to power attribute (or passive)
Step 3: run DRC again to solve the problem~
Why is it called the ultimate solution?Not to boast, this list is more complete than the current Synopsys, Cadence, support documentation, and FLEXnet’s help documentation.
these moves most of the eda vendor’s engineers are not plenary, the true conclusion is not nonsense. This thing toss about for a long time, spent a lot of energy, let me blow brag, ha ha.
in addition, if the following problems are excluded and the license is reported incorrectly, do not suspect that the list is incomplete, 99% of the time it may be that one of the steps is not done completely. Get a new check.
is limited to the legal license, crack is a weird problem, not to be discussed
start of text:
1, ensure that the LMGRD process has been completely killed;
# killall LMGRD
2, make sure the tool processes in the license, like synopsys SNPSLMD, cadence CDSLMD, are also completely killed
# killall XXXX
above two steps than lmdown-c license.lic insurance, also can be used cross-over
3, check whether the license port is used, if this is the case, you can temporarily change the port to try to start it once, if it is successful to explain the problem, follow the steps below to change back to the actual use of port
# netstat -pan | grep port_number
gets the process that is using the port, kill it, if not, wait for the port to be released, which may take a few minutes.
4, make sure the TCP protocol is started
can ping the host name view, can ping no problem
5, make sure the firewall does not block this port or turn off iptables
#service iptables stop
6, view seLinux or close
#setenforce 0
7, check /etc/hosts to make sure you have this line
127.0.0.1 localhost
8, check to see if Telnet hostname can pass, if it can’t login, then change by the following way
1 & gt; Install Telnet, Telnet-Server, xinetd
2 & gt; Modify /etc/xinetd.d/ Telnet disable to no
3 & gt; /etc/init.d/xinetd restart
9, if you use nis, make sure that the first parameter of all items in /etc/nsswitch is files
For example, networks: nisplus [NOTFOUND=return] files should be changed to
networks: files [NOTFOUND=return] nisplus
more than one problem usually do not encounter all at once, from front to back to find which solution to the problem can be.
is limited to the legal license, crack is a weird problem, not to be discussed