Forward eSign Authentication with airSlate SignNow

Forward esign authentication

hello everyone in this video I'm going to show you how to carry out functional synthesis in NC launch of cadence now I'm on the client side of a current server so I'm going to use putty as my SSH client it is the IP of the server now I'm going to use X Ming as my display server so I'm going to check this enable x11 forwarding well that's all now as it's very hard to work in online interface we are not used to it so I'm going to invoke the desktop manager of the server the server is based on a st. OS operating system and its desktop manager is not enough so I'm invoking Nautilus you now I'm going to create a directory or getting out my experiment I'm going to name it experiment for and inside it I will create another directory where my files will be created the very log files and on the same hierarchy I'm going to need file name cities live and age guild dot bar this two files are required for telling cadence that which configuration I'm going to use in my synthesis or functional verification now inside videos that live I have to tell cadence that we click like which directory I'm going to use as my library so I'm going to define my lip this would be my library name to be dot slash work underscore dir that's the decra name and inside HDL dot VAR I have to specify which library I'm going to use I have defining series dot lip that my library directory is work underscore dear and in HDL or bar I'm defining hash define work which means working directory which is my underscore Lib well that's all for configuring the environment now we are going to need the say log files you now it's the main thing which we are actually going to do is the functional synthesis I'm making a very basic and gate which will have two inputs and one output well this one is very straightforward very lock well now for testing it will will have to create a test bench file which is also very log you at first we have to create the input output signals in testbench all the input signals are to be defined as register and all the output signals to be wire we have to create an instance of the device we are going to use my device is basic and and I am going to name it instance to be duty which stands for device on the test you I'm renaming the pin names because I want to remove the confusion the pin names inside the basic end module are a B and out and inside my test bench is M am B and M out the naming convention is dot the name of the pin inside the module then inside the bracket the name of the pin inside the test page now...