In the process of learning digital IC, we inevitably need to use a series of tools from Synopsys. The performance of the virtual machine often cannot meet our needs. At this time, we can choose to install a dual system on our computer, which is also very convenient to use. If conditions permit, you can get a computer with better performance. After installing dual systems, configure the LINUX system as an intranet server. At this time, other members of the team can easily use the tool environment we have built. At the end of the article, I will attach the method of configuring Ubuntu as an intranet server.
1. Ubuntu and WIN10 dual system installation
1. System installation
The computer I use is DELL precision3660. I tried to install the centos system before, but in the end I felt that there were many things that were not easy to use, so I gave up. I happened to have the ISO image file of Ubuntu18.4.06 on hand, so I made one for WIN10 and Ubuntu18. 4 dual systems.
Step 1 Prepare U disk
It is recommended to find a USB flash drive that you don’t use very often, because in the process of making the boot disk, the USB flash drive needs to be formatted, so important data needs to be saved in advance. This USB flash drive generally does not need to be large, and 8G is completely sufficient. use.
Step 2: Determine the type of your computer
Category a: MBR bios + single hard drive
Category b: MBR bios + dual hard drives (SSD solid state + mechanical hard drive)
Category c: UEFI bios + single hard drive
Category d: UEFI bios + dual hard drives (SSD solid state + mechanical hard drive)
How can I check my computer type?
Press win+r on the keyboard (win: start key/the key that symbolizes Windows), enter msinfo32 in the input box , and press Enter to confirm.
You will then see the following information:
Next, determine the disk type of your computer. Enter disk management in the search bar in the lower left corner of WIN10 to get the following interface:
You can see that my computer has a 256 solid state drive and a 1T mechanical hard drive. If there is only disk 0, it is a single hard drive. Regarding the four situations a, b, c, and d mentioned before, the installation methods of each category are different. You must choose the corresponding installation method according to the type of your computer, otherwise it will cause failure.
Step 3 Install Ubuntu Image
Here is the address of Ubuntu official website:
https://ubuntu.com/download#download
Step 4: Allocate storage space for Ubuntu8.4
Again, as before, search for "Computer Management" in the search box at the bottom of the display, select "Disk Management"
and select the disk with the last disk space. For example, the last disk of the C disk is the C disk and the C and D disks. The last disk is the D disk (the last E disk of the CDE disk, the last disk F of the CDEF disk, and so on). Right-click the disk and select the compressed volume: Category a: MBR bios + single hard
disk
c Category: UEFI bios + single hard disk,
you can directly divide the disk according to the following method
And select the size of the hard disk that needs to be compressed/allocated to the new operating system as needed. Generally, at least 50 G is allocated ( 1G = 1024MB ). If the size is not enough, make some space and ensure that the last disk has 40~50G of free space. If there is enough space, it is recommended to allocate as much hard disk size as possible.
After setting the allocated hard disk size, click "Compress". After compression, you will find an extra unpartitioned disk (black partition). If the selected compression size is 50G, the black part is 50G available space.
Type b: MBR bios + dual hard drive (SSD solid state + mechanical hard drive)
Type d: UEFI bios + dual hard drive (SSD solid state + mechanical hard drive)
The partitioning method for Class A, Class C, and single hard disks is basically the same. The only difference is: when initially partitioning, 200M of space is allocated on the SSD (that is, the C drive of Windows) to install startup items, and about 50G is allocated on the mechanical hard disk ( It can be larger, as long as the disk capacity is sufficient), the 200M space allocated by the SSD will be placed in the efi, and the rest will be placed in the other 50G. Apart from the splits, everything else is exactly the same.
Step 5: Create system boot disk
There are many tools for making boot disks online, and you can basically use them all, so I won’t go into details here.
Step 6: Use the boot disk to install the Ubuntu system
Shut down the computer and restart it, press and hold F12 to enter the BIOS interface (I am using DELL, other computers can be searched on Baidu), then find the Boot Configuration option and disable it, select the storage mode as AHCI mode, and then pass Start the USB disk to install the system.
As shown in the picture, it is the safe boot configuration of my computer, and I have turned it off.
The picture below is the storage option. Select it to AHCI mode, but WIN10 uses RAID ON mode, so if you open WIN10 directly next time, a blue screen will appear. This is normal. Don’t panic. The solution will be discussed later. In the end, WIN10 and Ubuntu can be switched directly on the boot interface. In order for Ubuntu installation to proceed normally, select AHCI mode first.
Then change the first boot selection from Windows to USB , and then enter the unbuntu installation interface.
Select the language on the right and scroll down to find Chinese:
When installing unbuntu, you can disconnect from WiFi first and connect to the Internet when installing the system. Installing and uninstalling at the same time will affect the speed.
Next, it is recommended to select "Other Options" and you can divide the disks yourself. If you choose "direct installation", the previously allocated 50G space will be a single "large disk" by default.
Next, you will find a larger free partition, which is the partition we created before in the Windows system.
Regarding Linux partitions:
a. First of all, Linux partitions are different from Windows partitions. Linux is partitioned in the form of files.
b. So partitioning is just like dividing the disk size. Here, assume that the empty disk partition you divide is 60G. Click on the reserved free drive letter to partition. The partitioning method is:
Category a: MBR's bios + single hard drive
Category b: MBR's bios + dual hard drives (SSD solid state + mechanical hard drive)
1)/boot: This is the reason for your dual system. This is the directory used to start ubuntu. There will be system boot in it. This file is only a few dozen MB, but it is recommended to divide it into 200M and the file format is ext4. , this partition is essential!
Category c: UEFI bios + single hard drive
Category d: UEFI bios + dual hard drives (SSD solid state + mechanical hard drive)
1) efi: This is the reason for your dual system. This is the directory where ubuntu is started. There will be system boot in it. This file is actually only a few dozen MB, but it is recommended to divide it into 200M and the file format is efi. This partition is essential, otherwise you know the consequences!
The difference between MBR and UEFI, use /boot and efi respectively
In the next few steps, the installation methods for both computer types are again the same.
2) swap: This is the swap area directory of Linux, that is, Ubuntu. The size is generally 2 times the memory. When the computer memory is insufficient, the system calls this area to run the program. It can be divided into 4~8G, the file format is swap space, English swap
3) /: This is the root directory of Linux, which is the root directory of ubuntu. It is a backslash, which is equivalent to the C drive of Windows. We divide it into 10~20G. The file format is ext4. It can be larger if conditions permit. After all, ubuntu installation Software, installed here by default
4)/home: This is the "other disk" of Ubuntu, or the personal directory, which is equivalent to the DEF disk of Windows. In order to make the personal directory larger, all the remaining storage space is allocated to it, and the file format is ext4.
Still on this interface, select "Install boot drop-down menu". You just created the "/boot" or "efi" file in step 1). Now look at the number in front of this area and install the boot boot device. Just select the "/boot" or "efi" file, the corresponding number
and then find the corresponding number in the "Installation Startup Drop-down Menu", as shown in the following figure: /dev/sbd2 ("/boot" or "efi", the example in the figure is efi).
The installation continues, setting the region, keyboard layout, user name, password settings...
After everything is completed, the new system will remind you to restart. Remove the USB flash drive and click Restart. After that, every time you turn on the computer, you can choose the operating system to enter according to your own needs.
Under normal circumstances, the installation is complete, but I encountered a problem with the screen when installing Ubuntu 18.4. After the installation was completed, I found that the system could not connect to the Internet, so let's talk about the solutions to these problems.
2. Solving the problem of blurred screen
The reason for this problem is that the graphics card is incompatible. My computer uses Nvidia's T400Ti graphics card. Ubuntu 18.4 does not have the corresponding driver, so the screen will be distorted. I tried setting the default graphics card to the integrated graphics card in BISO, but in the end it was It keeps getting stuck and can't solve the problem. There will be a blurry screen problem when we install it. We can solve it through the following method and install the system normally.
Huaping during installation: Select install Ubuntu
when installing the GRUB page . Do not click, press e to enter the editing page, delete "---" after quiet splash , add nomodeset to support nvidia graphics cards, and then Ctrl+X to install.
After the installation is completed, we will still encounter the problem of blurry screen when we open the Ubuntu system. Don’t panic at this time, follow the following steps:
Huaping screen when booting:
After booting, we use the up and down keys to stop the cursor on Ubuntu on the boot interface, press 'e' to enter the edit mode, find the line of 'quite splash', delete all the content behind it, replace it with nomodeset, and then You can enter the system.
To solve this problem once and for all, after we enter the system, open the terminal, we open the reub file and run the following command:
sudo vi /etc/default/grubAfter opening the file, we found the line grub_cmdline_linux_default='quite splash', added nomodeset after splash, and sudo update-grub after saving. In this way, there will be no screen blur problem when we open it next time. This problem is completely solved.
3. Solution to being unable to connect to the Internet
After the system installation was completed, I found that my computer could not connect to the Internet. This problem was very serious, because if it could not connect to the Internet, many online dependency packages could not be downloaded, and many tools could not be installed normally. My computer is a desktop computer, and it only has a wired network card, not a wireless network card, so next I will mainly talk about the problem of the wired network card. If you encounter a wireless network card and cannot connect to the Internet, there are many wireless network card tutorials on the Internet, you can learn from it.
Open the terminal and enter ipconfig. You can see that there is only one IP address corresponding to lo. It is obviously a problem with the network card driver. Under normal circumstances, in addition to lo, there should be another physical network card information:
At this time, there are many tutorials on the Internet that provide solutions for downloading the network card driver online. I laughed when I saw this. How can I download it online without a network connection? ? ?
If anyone has the same problem as me, don't worry, let's reboot into the WIN10 system. Remember to change the storage mode back to RAID ON mode in the BIOS first, otherwise a blue screen will occur.
After entering WIN10, we enter device manager in the search bar in the lower left corner, open the device manager, and we can view our network card information:
You can see the network adapter. My network card model is Intel(R) Ethernet Connection(17)I219-LM. What we have to do is to download the network card driver of the LINUX system corresponding to this network card on WIN10 and copy it in U disk, and then unzip and install it through the LINUX system. The next step is how to operate it.
The Intel I219-LM model only has FreeBSD drivers on the Intel official website, and there is no Linux source code. However, it can be used with the e1000e network card driver, and the latter has a Linux driver on Intel. Download link: https://www.intel.com/content/www/us/en/download/14611/15817/intel-network-adapter-driver-for-pcie-intel-gigabit-ethernet-network-connections-under -linux-final-release.html?
Just download it. This network card driver is compatible with my network card, and then COPY it to unzip and install it in Ubuntu18.4. However, when installing the network card driver, you need make and gcc dependency packages, and we can't connect to the Internet, so we can't. You need to download the dependency package offline, so download it together here and then enter Ubuntu.
The link below is the offline installation package of gcc and make. I downloaded it and shared it with everyone.
http://Link: https://pan.baidu.com/s/1w6VIA8tlm9hU0N9tQyJnmA Extraction code: 32de
The following is the installation method of make and gcc. Just refer to this blog for installation.
After downloading these, enter Ubuntu. First, follow the tutorial above to install the dependency packages. After installation, you can install the network card driver. Extract the file in the Ubuntu system. After the decompression is complete, open the folder and you will see autorun.sh. Right-click on the blank area and open it in the terminal. Enter sudo ./autorun.sh, then you will be prompted to enter the password, enter the local password. If the installation is successful, the upper right corner should show that there is a network connection. Under normal circumstances, it will prompt that dependency packages such as make are missing, but we have installed them in advance.
4. Solve the blue screen problem when entering WIN10 in AHCI mode
Restart the computer, enter the BIOS, change the storage mode to RAID ON mode, and then enter the WIN10 system.
1. win+R, then enter msconfig and press Enter
2. Find the boot bar -> Check Safe Boot -> Click Confirm -> Select Restart -> Enter the BIOS interface
3. Change the RST mode to AHCI mode in the BIOS interface, save -> restart
4. After restarting, you will enter the safe mode. Then win+R, enter msconfig, uncheck safe boot in the boot bar, and click to confirm the restart. All the steps are over, so you can restart next time. You just need to choose to enter WIN10 or Ubuntu according to your needs. There is no need to enter the BIOS to modify the storage mode.
2. Construction of Synopsys tool environment (first install VCS and verdi)
At this point, the dual system has been installed. Next, you can start installing the Synopsys tools. The tools I installed are a series of tools in the 2018 version, including scl, vcs, verdi, dc compiler, primetime, formality, ic compiler.
First install VCS and VERDI.
Enter the vcs and verdi directories of synopsys and include the following directories:
Synopsys Installer:v5.0
SCL（Synopsys Common Licensing）: v2018.06
VCS: 2018.09
verdi: 2018.09
Before installation, first create the installation directory for each tool, including: VCS, VERDI, SCL, LICENSE
1. First run SynopsysInstaller_v5.0_run, run through 1./SynopsysInstaller_v5.0_run
a473@a473-ubuntu:~/Desktop/synopsys$ sudo mkdir -p /edaTools/synopsys/
[sudo] password for a473:
a473@a473-ubuntu:~/Desktop/synopsys$ sudo mkdir -p /edaTools/synopsys/installer
2. After running, setup.sh will be generated. Use ./setup.sh to run, and the installation program on the left will appear.
Fill in any information, next:
Click the browser button to select the path to the SCL installation package .spf file of the software that needs to be installed. After selecting, click done, next 
Select the installation path, here select the created installation directory:
Next, keep clicking next:
Click accept and install: 
Click Finish.
3.Install VCS
First, change the shell from dash to bash, otherwise an error will be reported. /bin/sh: 0: illegal option -h
First, ls -al /bin/shcheck the current sehll. Generally, the default is dash, just execute it sudo dpkg-reconfigure dashand choose to cancel.
Install VCS_mx_vO
Install VCS_vO
4.Install verdi
5.Activate
After the tool is installed, we need to crack it and generate the license file we need.
Get the hostname of the Linux environment: Enter hostname to view the host name.
Next, obtain the MAC address of the Linux environment and install net-tools:
sudo apt-get install net-tools
Use ifconfig to get the mac address:
Run the cracking software on Windows system, fill in the corresponding information, and generate a License
1 2It is the physical address of the computer, which can be viewed through ifconfigcommands. When filling in the physical address, ：remember to remove the ones in the middle. 3is the host-name of linux, as shown in the figure below. Click Generateto see it in this folder Synopsys.dat. This is the generated License file.
Click generate to generate license: Synopsys.dat in the path of the program.
Modify the second line of Synopsys.dat in the path of the snpslmd software of scl installed by yourself:
Place the License file under [scl installation path]/admin/licence
Basically, you will encounter some strange problems. Here I found an UP master who summarized it very well. Basically, the common problems are all included. Links are given for your reference. This is quite accurate. Let’s search online for other questions. Problems and solutions during the installation and use of Synopsys EDA Tools - Zhihu (zhihu.com)
Then there is the configuration of environment variables. Attached here are my own environment variables:
This is the environment variable after all my tools are installed. Just type it in. The operation method is:
sudo gedit /home/用户根目录/.bashrcgedit is a very good text compilation tool. It is much easier to use than vi and is closer to our usage habits of WIN10. Then just type these after the original file content. Here is another environment variable for the 2018 version, but I have not tried it.
export SynopsysList=/edaTools/synopsys
export DVE_HOME=$SynopsysList/vcs/O-2018.09-SP2/gui/dve/
export VCS_HOME=$SynopsysList/vcs/O-2018.09-SP2/
export VERDI_HOME=$SynopsysList/verdi/Verdi_O-2018.09-SP2/
#dve
export PATH=$PATH:$VCS_HOME/gui/dve/bin
alias dve='dve -full64'
#VCS
export PATH=$PATH:$VCS_HOME/bin
alias vcs='vcs'
#VERDI
export PATH=$PATH:$VERDI_HOME/bin
alias verdi='verdi'
#scl
export PATH=$PATH:$SynopsysList/scl/2018.06/linux64/bin/
export VCS_ARCH_OVERRIDE=linux
#LICENCE
export LM_LICENSE_FILE=27000@ming-ubuntu
alias lmg_vcs='lmgrd -c $SynopsysList/scl/2018.06/admin/license/Synopsys.dat'
Remember to source it after making the changes.
sudo source /......./.bashrcVerify License
Verify the license through the following commands until it appears Passed, as shown below. If it still does not appear after multiple verifications Passed, regenerate the license and verify again.
sssverify 自己的license路径
Start lmgrd
lmgrd is a license management tool, which is used to run the license in the background so that the software can work normally. Currently, this is the only understanding of lmgrd. Since the command is set in the environment variable, lmgrd can be started by typing lmli. This is where most of the problems arise! ! !
Question 1:
The path is obviously correct. You can also see lmgrd through ls, but it just cannot find lmgrd.
Solution: This is because there is no 32-bit runtime library. You can install it through the following commands. The first is the command under Ubuntu, and the second is the command under centos. Choose an execution command according to your needs.
apt-get install lsb
yum install lsb
Question 2:
Execute again lmli, prompting that there is no /usr/tmp directory and the license cannot be found in the /usr/local/flexlm/licenses directory. This is for sure, because you have not created these directories at all.
Solution: Create the tmp directory in /usr, create the local/flexlm/licenses directory, copy Synopsys.dat to the licenses directory, and change the name to license.bat
Question 3: It prompts that the license cannot be opened. This is because of an environment variable SNPSLMD_LICENSE_FILEproblem. The environment variable is assigned twice. The first time is the location of the license, and the second time is the user.
Solution: The location of the license is required here, so first comment out the second assignment. When DVE is started later, a second assignment will be needed, and then the comment is turned on.
Question 4:
Since lmgrd did not start successfully above, the port number is still occupied. When you enter lmli again , the following error should appear, showing that the port number is occupied
Solution: Enter the following command to terminate the port number. First release the license, display the port number occupied by lmgrd, and then end the port number process, as shown in the figure below
lmdown
ps auf | grep lmgrd
kill -9 2381
Then enter it again lmlito start lmgrd. Okay, witness the success~~ If you run here, it will be successful and you can ctrl+cend it .
Verify that the software is installed successfully
two
Enter dve, and an error is reported again, prompting SNPSLMD_LICENSE_FILE to indicate the wrong server.
Solution: This is the remaining problem above, just open the comment above. Enter it again dveto open it.
verdi
Enter verdi, don’t panic, what is supposed to come will come. Prompt that there is no libpng12.so.o library
Solution: Remember the library file mentioned in the first step? You need to use it at this time. Enter the following command. Note that libpng12.so.0 is a file in the folder. Moving the entire folder will not solve the problem.
sudo cp libpng12.so.0 /usr/lib/x86_64-linux-gnu/
Then enter verdi to open it:
VCS
Enter vcs -help, persistence is victory! The following error occurs
/bin/sh:0: illegal option –h
Solution: This is because Ubuntu will shlink to it by default bash. Enter the following command to relink.
rm -f /bin/sh
ln -s /bin/bash /bin/sh
Enter vcs -help, OK, successfully opened
At this point, VCS and Verdi can be used normally. You can do a small experiment to try it out.
cd /etc/profile.d/
sudo touch lmli.sh
sudo chmod 777 lmli.sh
Next, we set the license to start automatically at boot, so that we do not need to activate the license every time.
Create in /etc/profile.d/directorylmli.sh
Write the following:
`/usr/stone/software/SCL2018/scl/2018.06/linux64/bin/lmgrd -c /usr/stone/software/License/Synopsys.dat -l /usr/stone/software/SCL2018/scl/2018.06/linux64/bin/lmgrd.log`
At this point, VCS and verdi have basically been installed successfully. It is not easy to persist until now. Now that you have come this far, then follow me and build your own Synopsys environment. If you have completed the previous steps, many problems have actually been solved. The next step is to continue installing the software.
3. Installation of other Synopsys tools
It is very similar to the process of installing VCS and verdi. The paving work has been completed before, and the next step is to continue installing other tools.
As shown in the picture above, all my tools are of the 2018 version, and the license has been given when installing VCS and verdi, so there is no need to re-operate later.
We have the same installation process as VCS. Run the installation program, then select the installation package and select the installation path you created. It is recommended that the installation path here be created in advance and be consistent with the content entered in the environment variable file .basgrc.
It’s still this installer, with a graphical interface, just click and you’re done. The environment variable file is given again here, and the installation path is created against it.
In fact, after the installation is completed, many tools can be used directly. You will encounter some minor problems. You can almost solve them by referring to the common problem solutions given by the boss above. Here is a problem I encountered.
When opening PT, I encountered /usr/software/synopsys/.../pt/shlib/lib2.so.1:version 'ZLIB _1.2.9' not found (required by /usr/lib64/...)
Solution: Go to zlib to download the corresponding version of zlib, and download version 1.2.9 of zlib. Then unzip and install.
tar -zxvf zlib-1.2.9_tar.gz
cd zlib-1.2.9
-/configure
make
make install
ln -s /usr/local/lib/libz.so.1.2.9 /usr/software/synopsys/.../pt/shlib/Libz.so.1The last sentence actually means to create a soft link. If you want this file, I will download it and link it to you.
At this point, all my tools can be used normally. If you have other questions, you can search again, or refer to the questions summarized by others before.
4. Construction of intranet server
If you have no experience, this will be difficult to do at first. I have tried many methods and here are my own methods for success. We ended up using Xmanager for remote access.
Before implementation, we use another computer to conduct experiments. Use the same network cable to connect one computer to our computer, and then configure the IP address to be in the same network segment, for example, one is 168.192.0.1, and the other is 168.192.0.1. One is 168.192.0.2, the subnet mask is configured to 255.255.255.0, the gateways are configured to 168.192.0.1, and the DNS is set to 8.8.8.8.
After the configuration is successful, we use win+r to enter cmd to open the command line.
Then ping the IP address of another computer to ensure that the ping succeeds.
I don't have a connection here right now, so I won't show it. If it can be pinged, there will be a corresponding prompt. Use ububtu to open the terminal and ping the IP address of this Windows computer. After we can ping each other, we can proceed with the following work.
Xmanager uses the XDMCP protocol to connect to the desktop, so we need to enable this protocol.
First install the xubuntu-desktop desktop environment
$ sudo apt-get update
$ sudo apt-get install xubuntu-desktopRestart the XDMCP daemon and apply the desktop environment
16.0以上系统使用systemd配置：
Start running:
root #systemctl enable lightdm
···
现在启动
···
root #systemctl start lightdm###2. LightDM Configuration Because I need a lightweight window, I installed xubuntu. This is its launcher. If it is not configured properly, I need to configure it in the usr directory and then restart.
$ sudo vim /etc/lightdm/lightdm.conf
系统在"/usr/share/lightdm/lightdm.conf.d/*.conf "提供原始的配置文件，但是不建议使用。要把文件复制到"/etc/lightdm/lightdm.conf.d/*.conf"
You can set up hidden user list, manual login, and automatic login in the configuration file.
[XDMCPserver]
enabled=true
[SeatDefaults]
xserver-allow-tcp=true
greeter-show-remote-login=true
[XDMCPServer]
enabled=true
port=177test
$ sudo service lightdm restart
$ netstat -anp |grep :177 #确保UDP的177端口启动成功(XDMCP使用UDP 177端口)
udp 0 0 0.0.0.0:177 0.0.0.0:* -
udp6 0 0 :::177 :::* Restart the XDMCP service background process
$ sudo service lightdm restart
Create a task in Xmanager
At this point we can use another computer in the intranet to access our tools. We create new users for the server and let them access our server remotely through xmanager.
When other users use it, they will encounter the problem that the tool command is not recognized. We copy the environment variables we wrote to the environment variable files in other users' directories. Because we used absolute paths before, we can just copy them directly. , after completion, other users can also use the tool environment we configured.
Creation is not easy, thank you for your support! ! !