ift - User contributions [en]

Print schematics with Cadence

2018-03-24T13:51:06Z

Fli091: /* Tips */ =Using the schematics in latex=

= Print schematics from Cadence Virtuoso =

This article will show you how to save your schematics in a vectorised format so they can be manipulated or embedded in a report or a thesis.

Doing it this way, instead of "Export image" will result in something that looks useable and high resolution.

It is based on this youtube-movie https://www.youtube.com/watch?v=JivgqYabhWI

== Procedure ==

1. Locate the file containing the plotter-setups. It comes with the technology package and is located here:

/eda/cadence/2016-17/RHELx86/IC_6.1.7.704/tools.lnx86/plot/etc/cdsplotinit

2. Move the file to your own tsmc-folder

mv /eda/cadence/2016-17/RHELx86/IC_6.1.7.704/tools.lnx86/plot/etc/cdsplotinit ~/tsmc/.cdsplotinit

[[File:CadencePrintWindow.png|300px|thumb|right|The print-window in Virtuoso]]

3. Rename "your plotter": Change line 18, "Encapsulated PostScript:" to "p1|Encapsulated PostScript:"

gedit ~/tsmc/.cdsplotinit

or

vim ~/tsmc/.cdsplotinit

* If you get the error *Error* lessp: can't handle (nil <nil) you have to restart virtuoso for the plotters to be enabled

4. Now to print. First you might want to set a paper size. This is done here:

File - Print - Plot Options ... - Paper Size

Make sure the "Plotter Name" is what you called your plotter (p1).

5. Check the boxes "Fit to Page" and "Center plot"

6. Uncheck the the box "Mail Log To" and check the box "Send Plot Only To File" and set the path to where you want your plots/prints/schematics to be stored. This is also where you decide on a filename

~/tsmc/printedFromVirtuoso/voltageBuffer.ps

[[File:CadencePlotOptions.png|300px|thumb|right|The plot options-window in Virtuoso]]

7. Make sure the folder you have set to save your files in exist or Virtuoso will just output a warning ala

*WARNING* (SCH-1266): Cannot write to file "~/tsmc/printedFromVirtuoso/buffer.ps".

Create the folder:

mkdir ~/tsmc/printedFromVirtuoso/

8. Click OK in the Plot Options windows

9. Uncheck the "Plot with: header" box, just above the notes window

10. Press OK to save the schematic.

Now you can open the output.ps-file and it will look something like this:

[[File:Shaper.ps.jpg|center|thumb|The output of the Cadence postscript-printer converted to jpg]]

For the next schematics you want to plot you only have to "File - Print - Plot Options ...", change your filename and press OK.

== Tips ==

=== Disable all annotations ===

Do the following twice, once to enable this (and disable anything else) and the one more time to disable it again

View - Annotations - Component Parameters

This will make the schematic look cleaner and will hide fingers and channel lengths, etc. You could also do the same with net names, and possibly hide instance labels

View - Hide Instance Labels

=== Wider lines ===

Open the outputfile (.ps) in a text editor and find

setlinewidth

This set the width of all lines and can be changed to i.e. 2 for wider lines.

2 setlinewidth

Note: if you have text (not disabled annotations etc) the letters might mix together.

=== Sizing the "paper" ===

Changing the papersize from 5x5 to "unlimited" results in a larger plot, the filesize increased to 125%, but since PS is not a bitmap this is irrelevant as the schematic can be scaled to whatever size.

=== Using the schematics in latex ===

I recommend converting the ps-files to PDF it you want to use them in a latex-document. The ps can't be used directly and would have to be converted to eps, and since one is already converting PDF is a better choice. The converted PDF files are also 1/3 to 1/4 the size of the ps- and the eps-files and can be used without hassle as long as one uses the

\usepackage{graphicx}-package.

and the include the graphics like so

\begin{figure}[ptbh!]
\centering
\includegraphics[width=0.5\textwidth]{pictures/nmos_folded_cascode.pdf}
\caption{Folded cascode amplifier with NMOS input transistor.}\label{fig:foldedCascode}
\end{figure}

=== Convert the postscript(ps) to another format ===

On linux there are several tools that easily converts. For example

epstopdf output.ps

or

ps2pdf output.ps output.pdf

Results in a nice PDF to put in reports/theses. With ps2pdf the conversion can also be changed to output .png or .jpg

An alternative way to convert is to open the output.ps in a PDF viewer. Choose "Print" and "Print to File" and save the file as a PDF.

Note: some of these conversion might put the postscript-file on a large A4-paper with whitespace all around. Try epstopdf if this happens, it does not do that.

[[Category:Mikroelektronikk]] [[Category:Integrated_Circuts]]

Print schematics with Cadence

2018-03-24T12:47:33Z

Fli091: /* Convert the postscript(ps) to another format */ typo

= Print schematics from Cadence Virtuoso =

This article will show you how to save your schematics in a vectorised format so they can be manipulated or embedded in a report or a thesis.

Doing it this way, instead of "Export image" will result in something that looks useable and high resolution.

It is based on this youtube-movie https://www.youtube.com/watch?v=JivgqYabhWI

== Procedure ==

1. Locate the file containing the plotter-setups. It comes with the technology package and is located here:

/eda/cadence/2016-17/RHELx86/IC_6.1.7.704/tools.lnx86/plot/etc/cdsplotinit

2. Move the file to your own tsmc-folder

mv /eda/cadence/2016-17/RHELx86/IC_6.1.7.704/tools.lnx86/plot/etc/cdsplotinit ~/tsmc/.cdsplotinit

[[File:CadencePrintWindow.png|300px|thumb|right|The print-window in Virtuoso]]

3. Rename "your plotter": Change line 18, "Encapsulated PostScript:" to "p1|Encapsulated PostScript:"

gedit ~/tsmc/.cdsplotinit

or

vim ~/tsmc/.cdsplotinit

* If you get the error *Error* lessp: can't handle (nil <nil) you have to restart virtuoso for the plotters to be enabled

4. Now to print. First you might want to set a paper size. This is done here:

File - Print - Plot Options ... - Paper Size

Make sure the "Plotter Name" is what you called your plotter (p1).

5. Check the boxes "Fit to Page" and "Center plot"

6. Uncheck the the box "Mail Log To" and check the box "Send Plot Only To File" and set the path to where you want your plots/prints/schematics to be stored. This is also where you decide on a filename

~/tsmc/printedFromVirtuoso/voltageBuffer.ps

[[File:CadencePlotOptions.png|300px|thumb|right|The plot options-window in Virtuoso]]

7. Make sure the folder you have set to save your files in exist or Virtuoso will just output a warning ala

*WARNING* (SCH-1266): Cannot write to file "~/tsmc/printedFromVirtuoso/buffer.ps".

Create the folder:

mkdir ~/tsmc/printedFromVirtuoso/

8. Click OK in the Plot Options windows

9. Uncheck the "Plot with: header" box, just above the notes window

10. Press OK to save the schematic.

Now you can open the output.ps-file and it will look something like this:

[[File:Shaper.ps.jpg|center|thumb|The output of the Cadence postscript-printer converted to jpg]]

For the next schematics you want to plot you only have to "File - Print - Plot Options ...", change your filename and press OK.

== Tips ==

=== Disable all annotations ===

Do the following twice, once to enable this (and disable anything else) and the one more time to disable it again

View - Annotations - Component Parameters

This will make the schematic look cleaner and will hide fingers and channel lengths, etc. You could also do the same with net names, and possibly hide instance labels

View - Hide Instance Labels

=== Wider lines ===

Open the outputfile (.ps) in a text editor and find

setlinewidth

This set the width of all lines and can be changed to i.e. 2 for wider lines.

2 setlinewidth

Note: if you have text (not disabled annotations etc) the letters might mix together.

=== Sizing the "paper" ===

Changing the papersize from 5x5 to "unlimited" results in a larger plot, the filesize increased to 125%, but since PS is not a bitmap this is irrelevant as the schematic can be scaled to whatever size.

=== Convert the postscript(ps) to another format ===

On linux there are several tools that easily converts. For example

ps2pdf output.ps output.pdf

or

epstopdf output.ps

Results in a nice PDF to put in reports/theses. The conversion can also be changed to .png or .jpg

An alternative way to convert is to open the outpus.ps in a PDF viewer. Choose "Print" and "Print to File" and save the file as a PDF.

Note: some of these conversion might put the postscript-file on a large A4-paper with whitespace all around. Try epstopdf if this happens, it does not do that.

[[Category:Mikroelektronikk]] [[Category:Integrated_Circuts]]

Print schematics with Cadence

2018-03-24T12:47:17Z

Fli091: /* Convert the postscript(ps) to another format */ epstopdf conversion and whitespace around schematics

= Print schematics from Cadence Virtuoso =

This article will show you how to save your schematics in a vectorised format so they can be manipulated or embedded in a report or a thesis.

Doing it this way, instead of "Export image" will result in something that looks useable and high resolution.

It is based on this youtube-movie https://www.youtube.com/watch?v=JivgqYabhWI

== Procedure ==

1. Locate the file containing the plotter-setups. It comes with the technology package and is located here:

/eda/cadence/2016-17/RHELx86/IC_6.1.7.704/tools.lnx86/plot/etc/cdsplotinit

2. Move the file to your own tsmc-folder

mv /eda/cadence/2016-17/RHELx86/IC_6.1.7.704/tools.lnx86/plot/etc/cdsplotinit ~/tsmc/.cdsplotinit

[[File:CadencePrintWindow.png|300px|thumb|right|The print-window in Virtuoso]]

3. Rename "your plotter": Change line 18, "Encapsulated PostScript:" to "p1|Encapsulated PostScript:"

gedit ~/tsmc/.cdsplotinit

or

vim ~/tsmc/.cdsplotinit

* If you get the error *Error* lessp: can't handle (nil <nil) you have to restart virtuoso for the plotters to be enabled

4. Now to print. First you might want to set a paper size. This is done here:

File - Print - Plot Options ... - Paper Size

Make sure the "Plotter Name" is what you called your plotter (p1).

5. Check the boxes "Fit to Page" and "Center plot"

6. Uncheck the the box "Mail Log To" and check the box "Send Plot Only To File" and set the path to where you want your plots/prints/schematics to be stored. This is also where you decide on a filename

~/tsmc/printedFromVirtuoso/voltageBuffer.ps

[[File:CadencePlotOptions.png|300px|thumb|right|The plot options-window in Virtuoso]]

7. Make sure the folder you have set to save your files in exist or Virtuoso will just output a warning ala

*WARNING* (SCH-1266): Cannot write to file "~/tsmc/printedFromVirtuoso/buffer.ps".

Create the folder:

mkdir ~/tsmc/printedFromVirtuoso/

8. Click OK in the Plot Options windows

9. Uncheck the "Plot with: header" box, just above the notes window

10. Press OK to save the schematic.

Now you can open the output.ps-file and it will look something like this:

[[File:Shaper.ps.jpg|center|thumb|The output of the Cadence postscript-printer converted to jpg]]

For the next schematics you want to plot you only have to "File - Print - Plot Options ...", change your filename and press OK.

== Tips ==

=== Disable all annotations ===

Do the following twice, once to enable this (and disable anything else) and the one more time to disable it again

View - Annotations - Component Parameters

This will make the schematic look cleaner and will hide fingers and channel lengths, etc. You could also do the same with net names, and possibly hide instance labels

View - Hide Instance Labels

=== Wider lines ===

Open the outputfile (.ps) in a text editor and find

setlinewidth

This set the width of all lines and can be changed to i.e. 2 for wider lines.

2 setlinewidth

Note: if you have text (not disabled annotations etc) the letters might mix together.

=== Sizing the "paper" ===

Changing the papersize from 5x5 to "unlimited" results in a larger plot, the filesize increased to 125%, but since PS is not a bitmap this is irrelevant as the schematic can be scaled to whatever size.

=== Convert the postscript(ps) to another format ===

On linux there are several tools that easily converts. For example

ps2pdf output.ps output.pdf

or

epstopdf outpus.ps

Results in a nice PDF to put in reports/theses. The conversion can also be changed to .png or .jpg

An alternative way to convert is to open the outpus.ps in a PDF viewer. Choose "Print" and "Print to File" and save the file as a PDF.

Note: some of these conversion might put the postscript-file on a large A4-paper with whitespace all around. Try epstopdf if this happens, it does not do that.

[[Category:Mikroelektronikk]] [[Category:Integrated_Circuts]]

Print schematics with Cadence

2018-03-22T14:50:46Z

Fli091: /* Convert the postscript(ps) to another format */ Save to File/PDF

= Print schematics from Cadence Virtuoso =

This article will show you how to save your schematics in a vectorised format so they can be manipulated or embedded in a report or a thesis.

Doing it this way, instead of "Export image" will result in something that looks useable and high resolution.

It is based on this youtube-movie https://www.youtube.com/watch?v=JivgqYabhWI

== Procedure ==

1. Locate the file containing the plotter-setups. It comes with the technology package and is located here:

/eda/cadence/2016-17/RHELx86/IC_6.1.7.704/tools.lnx86/plot/etc/cdsplotinit

2. Move the file to your own tsmc-folder

mv /eda/cadence/2016-17/RHELx86/IC_6.1.7.704/tools.lnx86/plot/etc/cdsplotinit ~/tsmc/.cdsplotinit

[[File:CadencePrintWindow.png|300px|thumb|right|The print-window in Virtuoso]]

3. Rename "your plotter": Change line 18, "Encapsulated PostScript:" to "p1|Encapsulated PostScript:"

gedit ~/tsmc/.cdsplotinit

or

vim ~/tsmc/.cdsplotinit

* If you get the error *Error* lessp: can't handle (nil <nil) you have to restart virtuoso for the plotters to be enabled

4. Now to print. First you might want to set a paper size. This is done here:

File - Print - Plot Options ... - Paper Size

Make sure the "Plotter Name" is what you called your plotter (p1).

5. Check the boxes "Fit to Page" and "Center plot"

6. Uncheck the the box "Mail Log To" and check the box "Send Plot Only To File" and set the path to where you want your plots/prints/schematics to be stored. This is also where you decide on a filename

~/tsmc/printedFromVirtuoso/voltageBuffer.ps

[[File:CadencePlotOptions.png|300px|thumb|right|The plot options-window in Virtuoso]]

7. Make sure the folder you have set to save your files in exist or Virtuoso will just output a warning ala

*WARNING* (SCH-1266): Cannot write to file "~/tsmc/printedFromVirtuoso/buffer.ps".

Create the folder:

mkdir ~/tsmc/printedFromVirtuoso/

8. Click OK in the Plot Options windows

9. Uncheck the "Plot with: header" box, just above the notes window

10. Press OK to save the schematic.

Now you can open the output.ps-file and it will look something like this:

[[File:Shaper.ps.jpg|center|thumb|The output of the Cadence postscript-printer converted to jpg]]

For the next schematics you want to plot you only have to "File - Print - Plot Options ...", change your filename and press OK.

== Tips ==

=== Disable all annotations ===

Do the following twice, once to enable this (and disable anything else) and the one more time to disable it again

View - Annotations - Component Parameters

This will make the schematic look cleaner and will hide fingers and channel lengths, etc. You could also do the same with net names, and possibly hide instance labels

View - Hide Instance Labels

=== Wider lines ===

Open the outputfile (.ps) in a text editor and find

setlinewidth

This set the width of all lines and can be changed to i.e. 2 for wider lines.

2 setlinewidth

Note: if you have text (not disabled annotations etc) the letters might mix together.

=== Sizing the "paper" ===

Changing the papersize from 5x5 to "unlimited" results in a larger plot, the filesize increased to 125%, but since PS is not a bitmap this is irrelevant as the schematic can be scaled to whatever size.

=== Convert the postscript(ps) to another format ===

On linux there are several tools that easily converts. For example

ps2pdf output.ps output.pdf

Results in a nice PDF to put in reports/theses. The conversion can also be changed to .png or .jpg

An alternative way to convert is to open the outpus.ps in a PDF viewer. Choose "Print" and "Print to File" and save the file as a PDF.

[[Category:Mikroelektronikk]] [[Category:Integrated_Circuts]]

Print schematics with Cadence

2018-03-22T14:46:49Z

Fli091: /* Tips */ Papersize and conversion to other formats

= Print schematics from Cadence Virtuoso =

This article will show you how to save your schematics in a vectorised format so they can be manipulated or embedded in a report or a thesis.

Doing it this way, instead of "Export image" will result in something that looks useable and high resolution.

It is based on this youtube-movie https://www.youtube.com/watch?v=JivgqYabhWI

== Procedure ==

1. Locate the file containing the plotter-setups. It comes with the technology package and is located here:

/eda/cadence/2016-17/RHELx86/IC_6.1.7.704/tools.lnx86/plot/etc/cdsplotinit

2. Move the file to your own tsmc-folder

mv /eda/cadence/2016-17/RHELx86/IC_6.1.7.704/tools.lnx86/plot/etc/cdsplotinit ~/tsmc/.cdsplotinit

[[File:CadencePrintWindow.png|300px|thumb|right|The print-window in Virtuoso]]

3. Rename "your plotter": Change line 18, "Encapsulated PostScript:" to "p1|Encapsulated PostScript:"

gedit ~/tsmc/.cdsplotinit

or

vim ~/tsmc/.cdsplotinit

* If you get the error *Error* lessp: can't handle (nil <nil) you have to restart virtuoso for the plotters to be enabled

4. Now to print. First you might want to set a paper size. This is done here:

File - Print - Plot Options ... - Paper Size

Make sure the "Plotter Name" is what you called your plotter (p1).

5. Check the boxes "Fit to Page" and "Center plot"

6. Uncheck the the box "Mail Log To" and check the box "Send Plot Only To File" and set the path to where you want your plots/prints/schematics to be stored. This is also where you decide on a filename

~/tsmc/printedFromVirtuoso/voltageBuffer.ps

[[File:CadencePlotOptions.png|300px|thumb|right|The plot options-window in Virtuoso]]

7. Make sure the folder you have set to save your files in exist or Virtuoso will just output a warning ala

*WARNING* (SCH-1266): Cannot write to file "~/tsmc/printedFromVirtuoso/buffer.ps".

Create the folder:

mkdir ~/tsmc/printedFromVirtuoso/

8. Click OK in the Plot Options windows

9. Uncheck the "Plot with: header" box, just above the notes window

10. Press OK to save the schematic.

Now you can open the output.ps-file and it will look something like this:

[[File:Shaper.ps.jpg|center|thumb|The output of the Cadence postscript-printer converted to jpg]]

For the next schematics you want to plot you only have to "File - Print - Plot Options ...", change your filename and press OK.

== Tips ==

=== Disable all annotations ===

Do the following twice, once to enable this (and disable anything else) and the one more time to disable it again

View - Annotations - Component Parameters

This will make the schematic look cleaner and will hide fingers and channel lengths, etc. You could also do the same with net names, and possibly hide instance labels

View - Hide Instance Labels

=== Wider lines ===

Open the outputfile (.ps) in a text editor and find

setlinewidth

This set the width of all lines and can be changed to i.e. 2 for wider lines.

2 setlinewidth

Note: if you have text (not disabled annotations etc) the letters might mix together.

=== Sizing the "paper" ===

Changing the papersize from 5x5 to "unlimited" results in a larger plot, the filesize increased to 125%, but since PS is not a bitmap this is irrelevant as the schematic can be scaled to whatever size.

=== Convert the postscript(ps) to another format ===

On linux there are several tools that easily converts. For example

ps2pdf output.ps output.pdf

Results in a nice PDF to put in reports/theses. The conversion can also be changed to .png or .jpg

[[Category:Mikroelektronikk]] [[Category:Integrated_Circuts]]

Print schematics with Cadence

2018-03-22T14:29:29Z

Fli091: Formatting

Print schematics with Cadence

2018-03-22T14:28:35Z

Fli091: Created page

File:Shaper.ps.jpg

2018-03-22T14:24:16Z

Fli091: The output of the Cadence postscript-printer converted to jpg for showing on the wiki

The output of the Cadence postscript-printer converted to jpg for showing on the wiki

File:CadencePlotOptions.png

2018-03-22T13:46:34Z

Fli091: A screenshot showing the plot options window in Cadence Virtuoso

A screenshot showing the plot options window in Cadence Virtuoso

File:CadencePrintWindow.png

2018-03-22T13:45:11Z

Fli091: A screenshot of the print-window in Cadence Virtuoso

A screenshot of the print-window in Cadence Virtuoso

User:Fli091

2018-03-22T13:08:12Z

Fli091: sandbox and category

[mailto:fli091@uib.no mailto:fli091@uib.no]

== Sandbox ==

* [[User:Fli091/Print schematics with Cadence]]

== Diverse lenker ==
* [https://www.eda.ncsu.edu/wiki/FreePDK The FreePDKTM process design kit is an open-source, Open-Access-based PDK for the 45nm technology]
* [http://venividiwiki.ee.virginia.edu/mediawiki/index.php/ToolsCadenceTutorialsBasicSimulationOceanFreePDK Simulere med Cadence via OCEAN skript]
* [https://drive.google.com/file/d/0B8aUrqN1GG-DMl9Mc29rQnRpaVE/edit En presentasjon av hvordan lage OCEANskript]

[[Category:Microelectronics Users|FredrikLindseth]]

GATE tutorial

2017-11-28T10:33:36Z

Fli091: Added Category:Mikroelektronikk to this page so is listed

== Introduction and overview ==
This is a simple tutorial for GATE (Geant4) installation and usage, originally presented as a workshop for the pCT group in March 2017.

# [http://geant4.in2p3.fr/spip.php?rubrique8 Geant4 and ROOT virtual machine]
# [http://wiki.opengatecollaboration.org/index.php/Compilation_Instructions_V8.0 Gate installation]

Agenda for the day is as follows:
# An introduction to GATE macros, i.e. GATE input scripts
# Setting up a simple simulation geometry in GATE using a proton bencil beam and a water phantom
# Running short simulations
# Examination of the GATE-output files

== GATE ==
''Simulations of Preclinical and Clinical Scans in Emission Tomography, Transmission Tomography and Radiation Therapy''

Geant4 is a C++ library, where an application / simulation is built by writing certain C++ classes (geometry, beam, scoring, output, physics), and compiling the binaries from where the simulations are run. Only certain modifications to the simulations can be made with the binaries, such as beam settings, certain physics settings as well as geometry objects pre-defined to be variable.

GATE is an application written for Geant4. It was originally meant for PET and SPECT uses, however it is very flexible so many different kinds of detectors can be designed. To run GATE, only macro files written in the Geant4 scripting language (with some GATE specific commands) are needed to build the geometry, scoring, physics and beam. The output is also defined in the macro files, either to ASCII files or to ROOT files.

In each simulation, the user has to:
# define the scanner geometry
# set up the physics processes
# initialize the simulation
# set up the detector model
# define the source(s)
# specify the data output format
# start the acquisition

=== Introduction to GATE macros ===
Gate, just as GEANT4, is a program in which the user interface is based on scripts. To perform actions, the user must either enter commands in interactive mode, or build up macro files containing an ordered collection of commands.

Each command performs a particular function, and may require one or more parameters. The Gate commands are organized following a tree structure, with respect to the function they represent. For example, all geometry-control commands start with geometry, and they will all be found under the ''/geometry/'' branch of the tree structure.

When Gate is run, the '''Idle>''' prompt appears. At this stage the command interpreter is active; i.e. all the Gate commands entered will be interpreted and processed on-line. All functions in Gate can be accessed to using command lines. The geometry of the system, the description of the radioactive source(s), the physical interactions considered, etc., can be parameterized using command lines, which are translated to the Gate kernel by the command interpreter. In this way, the simulation is defined one step at a time, and the actual construction of the geometry and definition of the simulation can be seen on-line. If the effect is not as expected, the user can decide to re-adjust the desired parameter by re-entering the appropriate command on-line. Although entering commands step by step can be useful when the user is experimenting with the software or when he/she is not sure how to construct the geometry, there remains a need for storing the set of commands that led to a successful simulation.

Macros are ASCII files (with '.mac' extension) in which each line contains a command or a comment. Commands are GEANT4 or Gate scripted commands; comments start with the character ' #'. Macros can be executed from within the command interpreter in Gate, or by passing it as a command-line parameter to Gate, or by calling it from another macro. A macro or set of macros must include all commands describing the different components of a simulation in the right order. Usually these components are visualization, definitions of volumes (geometry), systems, digitizer, physics, initialization, source, output and start. These steps are described in the next sections. A single simulation may be split into several macros, for instance one for the geometry, one for the physics, etc. Usually, there is a master macro which calls the more specific macros. Splitting macros allows the user to re-use one or more of these macros in several other simulations, and/or to organize the set of all commands. To execute a macro (mymacro.mac in this example) from the Linux prompt, just type :

Gate mymacro.mac

To execute a macro from inside the Gate environment, type after the "Idle>" prompt:
Idle>/control/execute mymacro.mac

And finally, to execute a macro from inside another macro, simply write in the master macro:
/control/execute mymacro.mac

=== Setting up a simple simulation geometry in GATE using a pencil beam and a water phantom ===

==== Visualization ====
First we may want to set up a visualization engine to see what's going on. This is optional, and runs in batch mode should not be visualized! Here we use the opengl visualizer OGLX, but different kinds of visualization engines are discussed in the [http://wiki.opengatecollaboration.org/index.php/Users_Guide_V7.2:Visualization GATE wiki]
/vis/open OGLSX
/vis/viewer/reset
/vis/viewer/set/viewpointThetaPhi 60 60
/vis/viewer/zoom 1
/vis/viewer/set/style surface
/vis/drawVolume
/tracking/storeTrajectory 1
/vis/scene/endOfEventAction accumulate
/vis/viewer/update
Most of these commands are self explainatory. By using the storeTrajectory command, all particles are displayed together with the geometry.

==== Materials database ====
The default material assigned to a new volume is Air. The list of available materials is defined in the GateMaterials.db file. It's included in the Gate folder, and should be copied to the active directory. It is easy to add new materials to the file, just have a look at the file.
/gate/geometry/setMaterialDatabase MyMaterialDatabase.db

==== Geometry ====
Apart from specialized geometries such as PET, SPECT, CT, the general geometry is called as ''scanner''. It must be placed within the ''world'' volume, and all parts of the detector (to be scored) be placed within the ''scanner'' volume.

[[File:geometry_hiarerachy.png|400px]]

To construct a simple water phantom geometry of 30x30x30 cm, use the following commands:
/gate/world/geometry/setXLength 1000. cm
/gate/world/geometry/setYLength 1000. cm
/gate/world/geometry/setZLength 1000. cm
So we've defined a world geometry of 1 m<sup>3</sup>. It must be larger than all its daughter volumes. Let's put the ''scanner'' volume inside the ''world'' volume. Since it's not already defined (the ''world'' volume was), we must insert a ''box'' object (with parameters XLength, YLength, ZLength as the side measurements of the box):
/gate/world/daughters/name scanner
/gate/world/daughters/insert box
/gate/scanner/geometry/setXLength 100. cm
/gate/scanner/geometry/setYLength 100. cm
/gate/scanner/geometry/setZLength 100. cm
/gate/scanner/placement/setTranslation 0 0 50. cm
/gate/scanner/vis/forceWireframe
Inside this scanner volume (the default material is Air):
/gate/scanner/daughters/name phantom
/gate/scanner/daughters/insert box
/gate/phantom/geometry/setXLength 30. cm
/gate/phantom/geometry/setYLength 30. cm
/gate/phantom/geometry/setZLength 30. cm
/gate/phantom/placement/setTranslation 0 0 -15. cm
/gate/phantom/setMaterial Water
/gate/phantom/vis/forceWireframe

It is possible to repeat volumes. The simple method is to use a linear replicator:
/gate/phantom/repeaters/insert linear
/gate/phantom/linear/autoCenter false
/gate/phantom/linear/setRepeatNumber 10
/gate/phantom/linear/setRepeatVector 0 0 35. cm
The autoCenter command: The original volume is anchored (false), instead of the center-of-mass of all copies being centered at that position (true).

==== Sensitive Detectors ====
The scoring system in Geant4/GATE is based around ''Sensitive Detectors'' (SD). If a volume is a daughter volume (or grand-daughter, ...), it may be assigned as a SD. This process is super simple in GATE:
/gate/phantom/attachCrystalSD

If you want to define hierarchically repeated structures, such as layers or individually simulated pixels, they should be defined as a ''level'':
/gate/scanner/level1/attach phantom
/gate/scanner/level2/attach repeatedStructureWithinPhantom

And now you can use the ROOT leaf ''level1ID'' and ''level2ID'' to identify the volume.

==== Physics ====
There are many physics lists to choose from in Geant4/GATE. For proton therapy and detector simulations, I most often use a combination of a low-energy-friendly hadronic list and the variable-steplength (for Bragg Peak accuracy) electromagnetic list.
From the [http://geant4.cern.ch/support/physicsLists/referencePL/referencePL.shtml Geant4 reference physics webpage]:
* QGSP: QGSP is the basic physics list applying the quark gluon string model for high energy interactions of protons, neutrons, pions, and Kaons and nuclei. The high energy interaction creates an exited nucleus, which is passed to the precompound model modeling the nuclear de-excitation.
* QGSP_BIC: Like QGSP, but using Geant4 Binary cascade for primary protons and neutrons with energies below ~10GeV, thus replacing the use of the LEP model for protons and neutrons In comparison to the LEP model, Binary cascade better describes production of secondary particles produced in interactions of protons and neutrons with nuclei.
* emstandard_opt3 designed for any applications required higher accuracy of electrons, hadrons and ion tracking without magnetic field. It is used in extended electromagnetic examples and in the QGSP_BIC_EMY reference Physics List.

An overview over the different electromagnetic physics lists can be found [http://geant4.cern.ch/collaboration/working_groups/electromagnetic/physlist10.3.shtml here].

The physics list to use all of these is called ''QGSP_BIC_EMY''. It is loaded with the command
/gate/physics/addPhysicsList QGSP_BIC_EMY

In addition, in order to accurately represent the water in the water phantom, we define the current recommended value for the mean ionization potential for water, which is <math>75\ \mathrm{eV}</math>. This can be performed for all materials, and it will override Bragg's additivity rule.
/gate/geometry/setIonisationPotential Water 75 eV

==== Initialization ====
After the geometry and physics has been set, initialize the run!
/gate/run/initialize

==== Proton beam ====
/gate/source/addSource PBS PencilBeam
/gate/source/PBS/setParticleType proton
/gate/source/PBS/setEnergy 188.0 MeV
/gate/source/PBS/setSigmaEnergy 1.0 MeV
/gate/source/PBS/setPosition 0 0 -10. mm
/gate/source/PBS/setSigmaX 2 mm
/gate/source/PBS/setSigmaY 4 mm
/gate/source/PBS/setSigmaTheta 3.3 mrad
/gate/source/PBS/setSigmaPhi 3.8 mrad
/gate/source/PBS/setEllipseXThetaEmittance 15 mm*mrad
/gate/source/PBS/setEllipseXThetaRotationNorm negative
/gate/source/PBS/setEllipseYPhiEmittance 20 mm*mrad
/gate/source/PBS/setEllipseYPhiRotationNorm negative
/gate/application/setTotalNumberOfPrimaries 5000
It is tricky to use this beam since all parameters need to match, so an '''alternative''' is to use a uniform General Particle Source:
/gate/source/addSource uniformBeam gps
/gate/source/uniformBeam/gps/particle proton
/gate/source/uniformBeam/gps/ene/type Gauss
/gate/source/uniformBeam/gps/ene/mono 188 MeV
/gate/source/uniformBeam/gps/ene/sigma 1 MeV
/gate/source/uniformBeam/gps/type Plane
/gate/source/uniformBeam/gps/shape Square
/gate/source/uniformBeam/gps/direction 0 0 1
/gate/source/uniformBeam/gps/halfx 0 mm
/gate/source/uniformBeam/gps/halfy 0 mm
/gate/source/uniformBeam/gps/centre 0 0 -1 cm
/gate/application/setTotalNumberOfPrimaries 5000

==== Output ====
For this tutorial, we will use the ROOT output.
/gate/output/root/enable
/gate/output/root/setFileName gate_simulation

==== Running the simulation ====
To finalize the macro file, start the randomization engine and run!
/gate/random/setEngineName MersenneTwister
/gate/random/setEngineSeed auto
/gate/application/start

=== Running short simulations ===
To run a simulation, create a macro file with the lines as descibed above, and run it with
$ Gate waterphantom.mac
The terminal output describes the geometry, physics, etc.
If you want the visualization to be persistent, use instead
$ Gate
... [TEXT]
Idle> /control/execute waterphantom.mac

It is also possible to use aliases in the macro file. For example, to simplify the energy selection, substitute with the line
/gate/source/PBS/setEnergy {energy} MeV
and run the macro with
$ Gate -a '[energy,175]' waterphantom.mac
Multiple aliases can be stacked:
$ Gate -a '[energy,175] [phantomsize,45]' waterphantom.mac
if you have defined multiple alises in the macro file. It is sadly not possible to do calculations in the macro language, so you have to do that through bash (<code>newvalue=`echo "$oldvalue/2" | bc`</code>).

=== Examination of the GATE output files ===
The ROOT output file(s) from the simulation can be opened several ways:
* By using the built-in <code>TBrowser</code> to look at scoring variable distributions
* By using loading the ROOT Tree into a C++ program and looping over events (interactions)

==== Using the built-in <code>TBrowser</code> ====
The hierarchy for the files are shown in the image below:

[[File:root_file_hierarchy.PNG|600px]]

In Gate, the TTree is called ''Hits'', and the leaves are named after the different variables that are automatically scored:
PDGEncoding - The Particle ID
trackID - Track number following a mother particle
parentID - The parent track's event ID. 0 if the current particle is a beam particle
time - Time in simulation (for ToF in PET, etc.)
edep - Deposited energy in this event / interaction
stepLength - The length of the current step
posX - Global X position of event
posY - Global Y position of event
posZ - Global Z position of event
localPosX - Local (in mother volume) X position of event
localPosY - Local (in mother volume) Y position of event
localPosZ - Local (in mother volume) Z position of event
baseID - ID of mother volume ''scanner'', == 0 if only one ''scanner'' defined
level1ID - ID of 1st level of volume hierarchy
level2ID - ID of 2nd level of volume hierarchy
level3ID - ID of 3rd level of volume hierarchy
level4ID - ID of 4th level of volume hierarchy
sourcePosX - Global X position of source particle
sourcePosY - Global Y position of source particle
sourcePosZ - Global X position of source particle
eventID - History number (important!!)
volumeID - ID of current volume (useful to isolate particles in a specific part of a fully scored volume)
processName - A string containing the name of the interaction type:
- hIoni: Ionization by hadron
- Transportation: No special interactions (usually from step limiter)
- eIoni: Ionization by electron
- ProtonInelastic: Inelastic nuclear interaction of proton
- compt: Compton scattering
- ionIoni: Ionization by ion
- msc: Multiple Coulomb Scattering process
- hadElastic: Elastic hadron / proton scattering

An example of the distribution of eventID (in histogram form, this is the number of interactions per particle (if bin size = 1))
$ root
ROOT [0] new TBrowser

[[File:root.PNG|600px]]

Or for the Z distribution (see the Bragg Peak)

[[File:root2.PNG|600px]]

==== Opening the files in C++ ====
It is quite simple to open the generated ROOT files in a C++ program.

In <code>openROOTFile.C</code>:
#include <TTree.h>
#include <TFile.h>

using namespace std;

void Run() {
TFile *f = new TFile("gate_simulation.root");
TTree *tree = (TTree*) f->Get("Hits"); // The TTree in the GATE file is called ''Hits''

// Declare the variables (leafs) to be readout
Float_t x,y,z,edep;
Int_t eventID, parentID;

// Make a connection between the declared variables and the leafs
tree->SetBranchAddress("posX", &x);
tree->SetBranchAddress("posY", &y);
tree->SetBranchAddress("posZ", &z);
tree->SetBranchAddress("edep", &edep);
tree->SetBranchAddress("eventID", &eventID);
tree->SetBranchAddress("parentID", &parentID);

// Loop over all the entries in the tree
for (Int_t i=0, i < tree->GetEntries(); ++i) {
tree->GetEntry(i);
if (eventID > 2) break; // To limit the output!
if (parentID != 0) continue; // Only show results from primary particles

printf("Primary particle with event ID %d has an interaction with %.2f MeV energy loss at (x,y,z) = (%.2f, %.2f, %.2f).\n", eventID, edep, x, y, z);
}

delete f;
}

Then you can run the program with
$ root
ROOT [0] .L openROOTFile.C+ // The + tells ROOT to compile the code
ROOT [1] Run();

Please note that it is also possible to make a complete class to read out the root files using ROOT's <code>MakeClass</code> function. See [http://wiki.opengatecollaboration.org/index.php/Users_Guide_V7.2:Data_output#How_to_analyze_the_Root_output "How to analyze the ROOT output"].

==== Test case: Finding the range and straggling of a proton beam ====
#include <TTree.h>
#include <TH1F.h>
#include <TFile.h>
#include <TF1.h>

using namespace std;

void Run() {
TFile * f = new TFile("gate_simulation.root");
TTree * tree = (TTree*) f->Get("Hits"); // The TTree in the GATE file is called ''Hits''
TH1F * rangeHistogram = new TH1F("rangeHistogram", "Stopping position for protons"; 800, 0, 400); // Histogram 1D with Float values

Float_t z;
Int_t eventID, parentID;

Int_t lastEventID = -1;
Float_t lastZ = -1;

tree->SetBranchAddress("posZ", &z);
tree->SetBranchAddress("eventID", &eventID);
tree->SetBranchAddress("parentID", &parentID);

for (Int_t i=0, i < tree->GetEntries(); ++i) {
tree->GetEntry(i);
if (parentID != 0) continue;

// Check if this is the first event of a primary particle
if (eventID != lastEventID && lastEventID >= 0) {
rangeHistogram->Fill(lastZ);
}

// Store the current variables
lastZ = z;
lastEventID = eventID;
}

rangeHistogram->Draw();

// Make a Gaussian fit to the range
TF1 * fit = new TF1("fit", "gaus");
rangeHistogram->Fit("fit", "", "", 150, 250); // Most probable values for fit is in this range, ROOT is quite sensitive to Gaussians occupying only a small part of the histogram, so give narrow fit range

printf("The range of the proton beam is %.3f +- %.3f mm.\n", fit->GetParameter(1), fit->GetParameter(2));
}

This time, the program will yield the following output (from a 250 MeV beam):
The range of the proton beam is 378.225 mm +- 3.791 mm

With the following histogram (I've added some color and a SetOptFit to the legend)

[[File:ranges.PNG|600px]]

[[Category:Mikroelektronikk]]

User:Fli091

2017-11-28T10:32:21Z

Fli091:

[mailto:fli091@uib.no mailto:fli091@uib.no]

== Diverse lenker ==
* [https://www.eda.ncsu.edu/wiki/FreePDK The FreePDKTM process design kit is an open-source, Open-Access-based PDK for the 45nm technology]
* [http://venividiwiki.ee.virginia.edu/mediawiki/index.php/ToolsCadenceTutorialsBasicSimulationOceanFreePDK Simulere med Cadence via OCEAN skript]
* [https://drive.google.com/file/d/0B8aUrqN1GG-DMl9Mc29rQnRpaVE/edit En presentasjon av hvordan lage OCEANskript]

MikroserverSetup

2017-11-14T12:11:21Z

Fli091: Formatting

= Set-up of connection to mikroservers and cadence virtuoso =

This set-up will allow you to connect to the mikroservers and/or start Cadence virtuoso with one command without typing any password or host-names.

'''''NB: This setup is for TSMC, but the commands can be tweaked to be used with IHP or AMS too.'''''

The three mikroservers are :
* mikroserver1.klientdrift.uib.no
* mikroserver2.klientdrift.uib.no
* mikroserver3.klientdrift.uib.no

== SSH key ==
* Generate an ssh-key
ssh-keygen -f ~/.ssh/id.rsa -t rsa -N ''

* Copy the key with your identity to your chosen mikroserver (mikroserver3 is chosen in this example). NB: Replace USERNAME with your user name

ssh-copy-id USERNAME@mikroserver3.klientdrift.uib.no

== Connection aliases ==

For ease of use set up aliases for the connections in your terminal. Open .bashrc in a text editor (vim / nano) and type in this

alias mikroserver1='ssh -X USERNAME@mikroserver1.klientdrift.uib.no'
alias mikroserver2='ssh -X USERNAME@mikroserver2.klientdrift.uib.no'
alias mikroserver3='ssh -X USERNAME@mikroserver3.klientdrift.uib.no'

Also create another alias for your favourite mikroserver
echo "alias mikroserver='ssh -X USERNAME@mikroserver3.klientdrift.uib.no'" >> ~/.bashrc

== Automatic sourcing ==

Source scripts inside .bashrc. This will make sure the scripts are loaded every time you log in, so you don't have to do it manually
# TSMC setup
echo "source /eda/cadence/2016-17/scripts/analog_flow.sh" >> ~/.bashrc
echo "source /eda/cadence/eda_general_init.sh" >> ~/.bashrc
# IHP setup
echo "source ~/ihp/cds/sh.cadence" >> ~/.bashrc

== Commands to run virtuoso remotely ==
Then finally on the computers in the lab (NOT connected to the mikroservers)
echo "alias virtuoso_tsmc="ssh -X USERNAME@mikroserver3.klientdrift.uib.no 'cd tsmc;virtuoso &'"" >> ~/.bashrc
echo "alias virtuoso_ihp="ssh -X USERNAME@mikroserver3.klientdrift.uib.no 'cd ihp/cds;virtuoso &'"" >> ~/.bashrc

The next time you open your terminal on your computer you can type
virtuoso_tsmc
to start Cadence Virtuoso, or
mikroserver
to connect to mikroserver3 without any hassle!

== Add mikroserver as a folder on your pc ==

Open up your home folder in linux and in the bottom left corner click "Connect to Server" as shown in this picture:
[[File:ConnectToServer.png|thumbnail]]

as server address type:
sftp://mikroserver3.ift.uib.no/home/USERNAME
to add your homefolder on mikroserver as a folder on your local PC for easy access to your files (for example the [[Transistor_operating_point_printer]])
To store this connection, right click the "mikroserver3"-folder and click "Add Bookmark". The next time you just click the bookmark to open it.

=== Alternative way using scp/secure copy===
If for some reason the above doesn’t work you can try this:
* connect to your mikroserver (ssh mikroserver3)
* locate the file you want to copy. i.e /home/fredrik/picture.jpg
* type this command
scp picture.jpg USERNAME@login.uib.no:~
* this will copy the file to your home folder on any UiB machine

== Troubleshooting ==
* Make sure you copy your ID (ssh-copy-id) to the correct mikroserver
* Make sure you have restarted your terminal (or source ~/.bashrc) if the commands doesn't work
* You have to be either connected to the UiB VPN or run the commands via the computers in the lab to be able to connect to microserver
* If you are using another shell like zsh or csh the aliases has to be in ~/.zshrc or ~/.cshrc instead of ~/.bashrc
* Make sure you have replaced all the instances of USERNAME with your usename, i.e "fli091"

[[Category:Mikroelektronikk]]

MikroserverSetup

2017-11-14T12:10:58Z

Fli091: Added alternative way to get your files from mikroserver

= Set-up of connection to mikroservers and cadence virtuoso =

This set-up will allow you to connect to the mikroservers and/or start Cadence virtuoso with one command without typing any password or host-names.

'''''NB: This setup is for TSMC, but the commands can be tweaked to be used with IHP or AMS too.'''''

The three mikroservers are :
* mikroserver1.klientdrift.uib.no
* mikroserver2.klientdrift.uib.no
* mikroserver3.klientdrift.uib.no

== SSH key ==
* Generate an ssh-key
ssh-keygen -f ~/.ssh/id.rsa -t rsa -N ''

* Copy the key with your identity to your chosen mikroserver (mikroserver3 is chosen in this example). NB: Replace USERNAME with your user name

ssh-copy-id USERNAME@mikroserver3.klientdrift.uib.no

== Connection aliases ==

For ease of use set up aliases for the connections in your terminal. Open .bashrc in a text editor (vim / nano) and type in this

alias mikroserver1='ssh -X USERNAME@mikroserver1.klientdrift.uib.no'
alias mikroserver2='ssh -X USERNAME@mikroserver2.klientdrift.uib.no'
alias mikroserver3='ssh -X USERNAME@mikroserver3.klientdrift.uib.no'

Also create another alias for your favourite mikroserver
echo "alias mikroserver='ssh -X USERNAME@mikroserver3.klientdrift.uib.no'" >> ~/.bashrc

== Automatic sourcing ==

Source scripts inside .bashrc. This will make sure the scripts are loaded every time you log in, so you don't have to do it manually
# TSMC setup
echo "source /eda/cadence/2016-17/scripts/analog_flow.sh" >> ~/.bashrc
echo "source /eda/cadence/eda_general_init.sh" >> ~/.bashrc
# IHP setup
echo "source ~/ihp/cds/sh.cadence" >> ~/.bashrc

== Commands to run virtuoso remotely ==
Then finally on the computers in the lab (NOT connected to the mikroservers)
echo "alias virtuoso_tsmc="ssh -X USERNAME@mikroserver3.klientdrift.uib.no 'cd tsmc;virtuoso &'"" >> ~/.bashrc
echo "alias virtuoso_ihp="ssh -X USERNAME@mikroserver3.klientdrift.uib.no 'cd ihp/cds;virtuoso &'"" >> ~/.bashrc

The next time you open your terminal on your computer you can type
virtuoso_tsmc
to start Cadence Virtuoso, or
mikroserver
to connect to mikroserver3 without any hassle!

== Add mikroserver as a folder on your pc ==

Open up your home folder in linux and in the bottom left corner click "Connect to Server" as shown in this picture:
[[File:ConnectToServer.png|thumbnail]]

as server address type:
sftp://mikroserver3.ift.uib.no/home/USERNAME
to add your homefolder on mikroserver as a folder on your local PC for easy access to your files (for example the [[Transistor_operating_point_printer]])
To store this connection, right click the "mikroserver3"-folder and click "Add Bookmark". The next time you just click the bookmark to open it.

=== Alternative way using scp/secure copy==
If for some reason the above doesn’t work you can try this:
* connect to your mikroserver (ssh mikroserver3)
* locate the file you want to copy. i.e /home/fredrik/picture.jpg
* type this command
scp picture.jpg USERNAME@login.uib.no:~
* this will copy the file to your home folder on any UiB machine

== Troubleshooting ==
* Make sure you copy your ID (ssh-copy-id) to the correct mikroserver
* Make sure you have restarted your terminal (or source ~/.bashrc) if the commands doesn't work
* You have to be either connected to the UiB VPN or run the commands via the computers in the lab to be able to connect to microserver
* If you are using another shell like zsh or csh the aliases has to be in ~/.zshrc or ~/.cshrc instead of ~/.bashrc
* Make sure you have replaced all the instances of USERNAME with your usename, i.e "fli091"

[[Category:Mikroelektronikk]]

Cadence Virtuoso overview

2017-11-11T16:08:02Z

Fli091: Added link to another helpful thing / DCoperatingparameters

= IC design flow using Cadence =

We have access to several silicon technologies from different foundries

* 130nm CMOS process from Taiwan Semiconductor Manufacturing: '''[[ TSMC 130nm process ]]'''
* 130nm SiGe process from Innovations for High Performance Microelectronics: '''[[ IHP 130nm process ]]'''
* 350nm CMOS process from Austria Mikro Systeme: '''[[ AMS 350nm process ]]'''

= Simulation =

[[Testbench|Virtuoso Testbench]]

= Layout =

[[Layout XL and IHP SG13S]]

=Helpful stuff=
[[MikroserverSetup]] - setup for easy connection to the mikroservers and Cadence Virtuoso

[[ Transistor operating point printer ]] - Script to extract transistor operating point parameters after simulation.

[[DCoperatingparameters]] - Guide for showing transistor operating points in the schematic

[[ ADEXL-butterfly-curves ]] - Howto make DC butterfly curves easily.

[[Category:Mikroelektronikk]] [[Category:Integrated_Circuts]]

DCoperatingparameters

2017-11-11T15:59:04Z

Fli091: Created a guide to dc operating parameters in cadence virtuoso

= Show DC operating parameters =
This guide will show you how to show DC operating parameters like gm, R_{out} V_{th} etc for all your transistors in a Cadence schematic.

If you just want to save all parameters to a file have a look at this guide instead: [[Transistor operating point printer]]

== Steps ==
# Create your circuit in a schematic
# Set up a DC simulation, check the "save operating point"-box in the creating of the test
# Go back to your schematic window and at the top-men click:
# View - Annotations - DC Operating Points. This will give a default selection of parameters [[File:AnnotationMenu.png|thumbnail|right|The annotation menu]]
# To chose which to view in your schematic go back to View - Annotations and at the bottom click "Setup.."
# Make sure the library-drop-down is showing "tsmc13rf" (or your transistor library), choose pmos in "Cell" and leave instance to "*" if you want to change it for all transistors in your sheet.
# Here you can see the list that is showing by default and three "free" cells at the rows Parameter:cdsPara(6), (7) and (8)
# Double click in the column "Expression" for those rows and select the parameter you want to show (i.e region, rout, gm, gds) [[File:AnnotationSetupWindow.png|100px|thumbnail|right|The annotation setup window]]
#* You might want to disable annotation of the first four rows here to hide some annotation noise
# Click apply and repeat the same steps for the nmos cell [[File:PmosWithDCParameters.png|thumbnail|right|PMOS with parameters showing]]
# Save this annotation set-up by clicking File - Save. Chose the default location to make it easy for yourself. (If you don't save you have to do this set-up every time you close Virtuoso)
#* The next time you load your design just click View - Annotations - Setup.. and then File - Load - OK

== Note ==
* Region 0 is cutoff
* Region 1 is linear
* Region 2 is saturation
* Region 3 is subthreshold
* Region 4 is breakdown

* Type 0 is nMOS
* Type 1 is pMOS

[[Category:Mikroelektronikk]] [[Category:Integrated_Circuts]]

File:AnnotationSetupWindow.png

2017-11-11T15:54:34Z

Fli091: Picture showing the annotation setup in Cadence Virtuoso

Picture showing the annotation setup in Cadence Virtuoso

File:AnnotationMenu.png

2017-11-11T15:53:36Z

Fli091: Picture showing the location of the annotation menu in Cadence Virtuso

Picture showing the location of the annotation menu in Cadence Virtuso

File:PmosWithDCParameters.png

2017-11-11T15:51:15Z

Fli091: Picture showing Cadence Virtuso with a pmos with DC operating parameters showing

Picture showing Cadence Virtuso with a pmos with DC operating parameters showing

Transistor operating point printer

2017-11-11T15:21:01Z

Fli091: Link to another guide

= DC operating parameters from simulation =
This script can be used to print the operating point parameters of all transistors in your design and save them to a file.

If you just want to view them in Virtusoso have a look at this guide instead: [[DCoperatingparameters]]

== Get the DC operating points from a previous simulation ==
Navigate to the folder you want to save the script in (this tutorial uses the home (./) directory) and create a new file in the terminal by entering <code> touch transistors.ocn </code>. Open the file by writing <code> gedit transistors.ocn & </code> and copy the following script into the document. Change ./transistors.csv in the script if you want another output file name and/or location. Save the file.
selectResult('dcOpInfo)
report(?output "./transistors.csv" ?param list("gm" "gmb" "gmoverid" "gds" "id" "idsat" "vth" "region" "cgs" "cgd" "self_gain" "type" "vds" "vdsat" "vgs") ?format "spice" ?maxLineWidth 1000)

file = outfile("./transistors.csv" "a")
fprintf(file "\n\nRegion 0 is cutoff.\nRegion 1 is linear.\nRegion 2 is saturation .\nRegion 3 is subthreshold.\nRegion 4 is breakdown.\n\nType 0 is nMOS. \nType 1 is pMOS.")
close(file)

For the IHP design kit use:
selectResult('dcOpInfo)
report(?output "./transistors.csv" ?param list("model" "gm" "gmb" "gds" "ids" "idsat" "vth" "region" "cgs" "cgd" "vds" "vsat" "vgs") ?format "spice" ?maxLineWidth 1000)

file = outfile("./transistors.csv" "a")
fprintf(file "\n\nRegion 0 is cutoff.\nRegion 1 is linear.\nRegion 2 is saturation .\nRegion 3 is subthreshold.\nRegion 4 is breakdown.\n\nType 0 is nMOS. \nType 1 is pMOS.")
close(file)

This script uses the results from the previous Debug Test (from ADE XL Test Editor). Before running the script, run a test with DC analysis, and remember to check the box with "Save DC Operating Point" :

[[File:Run_debug_simulation.png | 500px]]

After running DC analysis, run the script by entering the following into the Virtuoso Log Window (with file name and location as mentioned above): <code>load("./transistors.ocn")</code>

[[File:Run_transistors_script.png]]

== Copy the file to your computer and convert the values ==
After running the script, you can open the results file from the terminal using for example: <code> gedit transistors.csv & </code> or alternatively to get the file out from mikroserver
to another computer try this:

Create a file named "Makefile" and put this into it:

# target that is the first (and default) and does all the stuff below
all: get fix clean

# gets the file from mikroserver3 and copies it to your computer in the root of your homefolder
get :
scp fli091@mikroserver3.ift.uib.no:~/tsmc/transistors.csv ~/transistors_raw.csv

# converts transitors.csv to a copy where all the postfixes for the SI units generated from Virtuoso (m, f, K etc), has been replaced with E-3, E-15, E+3 etc, so the values are useable in LibreOffice
fix :
sed -e 's/$[0-9]\+$m/\1E-3/g' -e 's/$[0-9]\+$u/\1E-6/g' -e 's/$[0-9]\+$n/\1E-9/g' -e 's/$[0-9]\+$p/\1E-12/g' -e 's/$[0-9]\+$f/\1E-15/g' -e 's/$[0-9]\+$a/\1E-18/g' -e 's/$[0-9]\+$z/\1E-21/g' -e 's/$[0-9]\+$y/\1E-24/g' -e 's/$[0-9]\+$K/\1E+3/g' -e 's/$[0-9]\+$M/\1E+6/g' -e 's/$[0-9]\+$G/\1E+9/g' -e 's/$[0-9]\+$T/\1E+12/g' transistors_raw.csv > transistors.csv

# removes the not-fixed copy
clean:
rm transistors_raw.csv

Modify the scp-command to use
* The username(and not fli091) in the scp-command
* change mikroserver if you are not using mikroserver3.
* change the folder on mikroserver where the transistors.csv is created, default is /home/$user/tsmc/
* change the local folder where you want your copy to be placed, default is /home/$user/

Now you can type <code>make</code> in the folder you created the Makefile and the latestst simulation data will appear in your homefolder.

== Open the file in Libre Office ==
The resulting transistors.csv can then be imported into LibreOffice Calc (similar to Microsoft Excel) using File->Open, then choose the .csv file and enter the settings as in the following image:

[[File:Csv_import_libreoffice.png | 500px]]

== Troubleshooting ==
For the scp-command to work without password you have to set up your connection as described in [[MikroserverSetup]]

[[Category:Mikroelektronikk]] [[Category:Integrated_Circuts]]

Transistor operating point printer

2017-11-01T12:51:08Z

Fli091: Commented the makefile

= DC operating parameters from simulation =
This script can be used to print the operating point parameters of all transistors in your design.

== Get the DC operating points from a previous simulation ==
Navigate to the folder you want to save the script in (this tutorial uses the home (./) directory) and create a new file in the terminal by entering <code> touch transistors.ocn </code>. Open the file by writing <code> gedit transistors.ocn & </code> and copy the following script into the document. Change ./transistors.csv in the script if you want another output file name and/or location. Save the file.
selectResult('dcOpInfo)
report(?output "./transistors.csv" ?param list("gm" "gmb" "gmoverid" "gds" "id" "idsat" "vth" "region" "cgs" "cgd" "self_gain" "type" "vds" "vdsat" "vgs") ?format "spice" ?maxLineWidth 1000)

file = outfile("./transistors.csv" "a")
fprintf(file "\n\nRegion 0 is cutoff.\nRegion 1 is linear.\nRegion 2 is saturation .\nRegion 3 is subthreshold.\nRegion 4 is breakdown.\n\nType 0 is nMOS. \nType 1 is pMOS.")
close(file)

For the IHP design kit use:
selectResult('dcOpInfo)
report(?output "./transistors.csv" ?param list("model" "gm" "gmb" "gds" "ids" "idsat" "vth" "region" "cgs" "cgd" "vds" "vsat" "vgs") ?format "spice" ?maxLineWidth 1000)

file = outfile("./transistors.csv" "a")
fprintf(file "\n\nRegion 0 is cutoff.\nRegion 1 is linear.\nRegion 2 is saturation .\nRegion 3 is subthreshold.\nRegion 4 is breakdown.\n\nType 0 is nMOS. \nType 1 is pMOS.")
close(file)

This script uses the results from the previous Debug Test (from ADE XL Test Editor). Before running the script, run a test with DC analysis, and remember to check the box with "Save DC Operating Point" :

[[File:Run_debug_simulation.png | 500px]]

After running DC analysis, run the script by entering the following into the Virtuoso Log Window (with file name and location as mentioned above): <code>load("./transistors.ocn")</code>

[[File:Run_transistors_script.png]]

== Copy the file to your computer and convert the values ==
After running the script, you can open the results file from the terminal using for example: <code> gedit transistors.csv & </code> or alternatively to get the file out from mikroserver
to another computer try this:

Create a file named "Makefile" and put this into it:

# target that is the first (and default) and does all the stuff below
all: get fix clean

# gets the file from mikroserver3 and copies it to your computer in the root of your homefolder
get :
scp fli091@mikroserver3.ift.uib.no:~/tsmc/transistors.csv ~/transistors_raw.csv

# converts transitors.csv to a copy where all the postfixes for the SI units generated from Virtuoso (m, f, K etc), has been replaced with E-3, E-15, E+3 etc, so the values are useable in LibreOffice
fix :
sed -e 's/$[0-9]\+$m/\1E-3/g' -e 's/$[0-9]\+$u/\1E-6/g' -e 's/$[0-9]\+$n/\1E-9/g' -e 's/$[0-9]\+$p/\1E-12/g' -e 's/$[0-9]\+$f/\1E-15/g' -e 's/$[0-9]\+$a/\1E-18/g' -e 's/$[0-9]\+$z/\1E-21/g' -e 's/$[0-9]\+$y/\1E-24/g' -e 's/$[0-9]\+$K/\1E+3/g' -e 's/$[0-9]\+$M/\1E+6/g' -e 's/$[0-9]\+$G/\1E+9/g' -e 's/$[0-9]\+$T/\1E+12/g' transistors_raw.csv > transistors.csv

# removes the not-fixed copy
clean:
rm transistors_raw.csv

Modify the scp-command to use
* The username(and not fli091) in the scp-command
* change mikroserver if you are not using mikroserver3.
* change the folder on mikroserver where the transistors.csv is created, default is /home/$user/tsmc/
* change the local folder where you want your copy to be placed, default is /home/$user/

Now you can type <code>make</code> in the folder you created the Makefile and the latestst simulation data will appear in your homefolder.

== Open the file in Libre Office ==
The resulting transistors.csv can then be imported into LibreOffice Calc (similar to Microsoft Excel) using File->Open, then choose the .csv file and enter the settings as in the following image:

[[File:Csv_import_libreoffice.png | 500px]]

== Troubleshooting ==
For the scp-command to work without password you have to set up your connection as described in [[MikroserverSetup]]

[[Category:Mikroelektronikk]] [[Category:Integrated_Circuts]]

Transistor operating point printer

2017-11-01T12:48:38Z

Fli091: Remember to check the box with "Save DC Operating Point" !

= DC operating parameters from simulation =
This script can be used to print the operating point parameters of all transistors in your design.

== Get the DC operating points from a previous simulation ==
Navigate to the folder you want to save the script in (this tutorial uses the home (./) directory) and create a new file in the terminal by entering <code> touch transistors.ocn </code>. Open the file by writing <code> gedit transistors.ocn & </code> and copy the following script into the document. Change ./transistors.csv in the script if you want another output file name and/or location. Save the file.
selectResult('dcOpInfo)
report(?output "./transistors.csv" ?param list("gm" "gmb" "gmoverid" "gds" "id" "idsat" "vth" "region" "cgs" "cgd" "self_gain" "type" "vds" "vdsat" "vgs") ?format "spice" ?maxLineWidth 1000)

file = outfile("./transistors.csv" "a")
fprintf(file "\n\nRegion 0 is cutoff.\nRegion 1 is linear.\nRegion 2 is saturation .\nRegion 3 is subthreshold.\nRegion 4 is breakdown.\n\nType 0 is nMOS. \nType 1 is pMOS.")
close(file)

For the IHP design kit use:
selectResult('dcOpInfo)
report(?output "./transistors.csv" ?param list("model" "gm" "gmb" "gds" "ids" "idsat" "vth" "region" "cgs" "cgd" "vds" "vsat" "vgs") ?format "spice" ?maxLineWidth 1000)

file = outfile("./transistors.csv" "a")
fprintf(file "\n\nRegion 0 is cutoff.\nRegion 1 is linear.\nRegion 2 is saturation .\nRegion 3 is subthreshold.\nRegion 4 is breakdown.\n\nType 0 is nMOS. \nType 1 is pMOS.")
close(file)

This script uses the results from the previous Debug Test (from ADE XL Test Editor). Before running the script, run a test with DC analysis, and remember to check the box with "Save DC Operating Point" :

[[File:Run_debug_simulation.png | 500px]]

After running DC analysis, run the script by entering the following into the Virtuoso Log Window (with file name and location as mentioned above): <code>load("./transistors.ocn")</code>

[[File:Run_transistors_script.png]]

== Copy the file to your computer and convert the values ==
After running the script, you can open the results file from the terminal using for example: <code> gedit transistors.csv & </code> or alternatively to get the file out from mikroserver
to another computer try this:

Create a file named "Makefile" and put this into it:

all: get fix clean

get :
scp fli091@mikroserver3.ift.uib.no:~/tsmc/transistors.csv ~/transistors_raw.csv

fix :
sed -e 's/$[0-9]\+$m/\1E-3/g' -e 's/$[0-9]\+$u/\1E-6/g' -e 's/$[0-9]\+$n/\1E-9/g' -e 's/$[0-9]\+$p/\1E-12/g' -e 's/$[0-9]\+$f/\1E-15/g' -e 's/$[0-9]\+$a/\1E-18/g' -e 's/$[0-9]\+$z/\1E-21/g' -e 's/$[0-9]\+$y/\1E-24/g' -e 's/$[0-9]\+$K/\1E+3/g' -e 's/$[0-9]\+$M/\1E+6/g' -e 's/$[0-9]\+$G/\1E+9/g' -e 's/$[0-9]\+$T/\1E+12/g' transistors_raw.csv > transistors.csv

clean:
rm transistors_raw.csv

Modify the scp-command to use
* The username(and not fli091) in the scp-command
* change mikroserver if you are not using mikroserver3.
* change the folder on mikroserver where the transistors.csv is created, default is /home/$user/tsmc/
* change the local folder where you want your copy to be placed, default is /home/$user/

A short explanation of the Makefile
* The get-target gets the file from mikroserver3 and copies it to your computer in the root of your homefolder
* The fix-target converts transitors.csv to a copy where all the postfixes for the SI units generated from Virtuoso (m, f, K etc), has been replaced with E-3, E-15, E+3 etc, so the values are useable in LibreOffice
* The clean-target just removes the not-fixed copy

Now you can type <code>make</code> in the folder you created the Makefile and the latestst simulation data will appear in your homefolder.

== Open the file in Libre Office ==
The resulting transistors.csv can then be imported into LibreOffice Calc (similar to Microsoft Excel) using File->Open, then choose the .csv file and enter the settings as in the following image:

[[File:Csv_import_libreoffice.png | 500px]]

== Troubleshooting ==
For the scp-command to work without password you have to set up your connection as described in [[MikroserverSetup]]

[[Category:Mikroelektronikk]] [[Category:Integrated_Circuts]]

MikroserverSetup

2017-10-31T10:53:20Z

Fli091: How to bookmark the mikroserver folder-connection

= Set-up of connection to mikroservers and cadence virtuoso =

This set-up will allow you to connect to the mikroservers and/or start Cadence virtuoso with one command without typing any password or host-names.

'''''NB: This setup is for TSMC, but the commands can be tweaked to be used with IHP or AMS too.'''''

The three mikroservers are :
* mikroserver1.klientdrift.uib.no
* mikroserver2.klientdrift.uib.no
* mikroserver3.klientdrift.uib.no

== SSH key ==
* Generate an ssh-key
ssh-keygen -f ~/.ssh/id.rsa -t rsa -N ''

* Copy the key with your identity to your chosen mikroserver (mikroserver3 is chosen in this example). NB: Replace USERNAME with your user name

ssh-copy-id USERNAME@mikroserver3.klientdrift.uib.no

== Connection aliases ==

For ease of use set up aliases for the connections in your terminal. Open .bashrc in a text editor (vim / nano) and type in this

alias mikroserver1='ssh -X USERNAME@mikroserver1.klientdrift.uib.no'
alias mikroserver2='ssh -X USERNAME@mikroserver2.klientdrift.uib.no'
alias mikroserver3='ssh -X USERNAME@mikroserver3.klientdrift.uib.no'

Also create another alias for your favourite mikroserver
echo "alias mikroserver='ssh -X USERNAME@mikroserver3.klientdrift.uib.no'" >> ~/.bashrc

== Automatic sourcing ==

Source scripts inside .bashrc. This will make sure the scripts are loaded every time you log in, so you don't have to do it manually
# TSMC setup
echo "source /eda/cadence/2016-17/scripts/analog_flow.sh" >> ~/.bashrc
echo "source /eda/cadence/eda_general_init.sh" >> ~/.bashrc
# IHP setup
echo "source ~/ihp/cds/sh.cadence" >> ~/.bashrc

== Commands to run virtuoso remotely ==
Then finally on the computers in the lab (NOT connected to the mikroservers)
echo "alias virtuoso_tsmc="ssh -X USERNAME@mikroserver3.klientdrift.uib.no 'cd tsmc;virtuoso &'"" >> ~/.bashrc
echo "alias virtuoso_ihp="ssh -X USERNAME@mikroserver3.klientdrift.uib.no 'cd ihp/cds;virtuoso &'"" >> ~/.bashrc

The next time you open your terminal on your computer you can type
virtuoso_tsmc
to start Cadence Virtuoso, or
mikroserver
to connect to mikroserver3 without any hassle!

== Add mikroserver as a folder on your pc ==

Open up your home folder in linux and in the bottom left corner click "Connect to Server" as shown in this picture:
[[File:ConnectToServer.png|thumbnail]]

as server address type:
sftp://mikroserver3.ift.uib.no/home/USERNAME
to add your homefolder on mikroserver as a folder on your local PC for easy access to your files (for example the [[Transistor_operating_point_printer]])
To store this connection, right click the "mikroserver3"-folder and click "Add Bookmark". The next time you just click the bookmark to open it.

== Troubleshooting ==
* Make sure you copy your ID (ssh-copy-id) to the correct mikroserver
* Make sure you have restarted your terminal (or source ~/.bashrc) if the commands doesn't work
* You have to be either connected to the UiB VPN or run the commands via the computers in the lab to be able to connect to microserver
* If you are using another shell like zsh or csh the aliases has to be in ~/.zshrc or ~/.cshrc instead of ~/.bashrc
* Make sure you have replaced all the instances of USERNAME with your usename, i.e "fli091"

[[Category:Mikroelektronikk]]

MikroserverSetup

2017-10-31T10:51:33Z

Fli091: Added description to add mikroserver as a folder

= Set-up of connection to mikroservers and cadence virtuoso =

This set-up will allow you to connect to the mikroservers and/or start Cadence virtuoso with one command without typing any password or host-names.

'''''NB: This setup is for TSMC, but the commands can be tweaked to be used with IHP or AMS too.'''''

The three mikroservers are :
* mikroserver1.klientdrift.uib.no
* mikroserver2.klientdrift.uib.no
* mikroserver3.klientdrift.uib.no

== SSH key ==
* Generate an ssh-key
ssh-keygen -f ~/.ssh/id.rsa -t rsa -N ''

* Copy the key with your identity to your chosen mikroserver (mikroserver3 is chosen in this example). NB: Replace USERNAME with your user name

ssh-copy-id USERNAME@mikroserver3.klientdrift.uib.no

== Connection aliases ==

For ease of use set up aliases for the connections in your terminal. Open .bashrc in a text editor (vim / nano) and type in this

alias mikroserver1='ssh -X USERNAME@mikroserver1.klientdrift.uib.no'
alias mikroserver2='ssh -X USERNAME@mikroserver2.klientdrift.uib.no'
alias mikroserver3='ssh -X USERNAME@mikroserver3.klientdrift.uib.no'

Also create another alias for your favourite mikroserver
echo "alias mikroserver='ssh -X USERNAME@mikroserver3.klientdrift.uib.no'" >> ~/.bashrc

== Automatic sourcing ==

Source scripts inside .bashrc. This will make sure the scripts are loaded every time you log in, so you don't have to do it manually
# TSMC setup
echo "source /eda/cadence/2016-17/scripts/analog_flow.sh" >> ~/.bashrc
echo "source /eda/cadence/eda_general_init.sh" >> ~/.bashrc
# IHP setup
echo "source ~/ihp/cds/sh.cadence" >> ~/.bashrc

== Commands to run virtuoso remotely ==
Then finally on the computers in the lab (NOT connected to the mikroservers)
echo "alias virtuoso_tsmc="ssh -X USERNAME@mikroserver3.klientdrift.uib.no 'cd tsmc;virtuoso &'"" >> ~/.bashrc
echo "alias virtuoso_ihp="ssh -X USERNAME@mikroserver3.klientdrift.uib.no 'cd ihp/cds;virtuoso &'"" >> ~/.bashrc

The next time you open your terminal on your computer you can type
virtuoso_tsmc
to start Cadence Virtuoso, or
mikroserver
to connect to mikroserver3 without any hassle!

== Add mikroserver as a folder on your pc ==

Open up your home folder in linux and in the bottom left corner click "Connect to Server" as shown in this picture:
[[File:ConnectToServer.png|thumbnail]]

as server address type:
sftp://mikroserver3.ift.uib.no/home/USERNAME
to add your homefolder on mikroserver as a folder on your local PC for easy access to your files (for example the [[Transistor_operating_point_printer]])

== Troubleshooting ==
* Make sure you copy your ID (ssh-copy-id) to the correct mikroserver
* Make sure you have restarted your terminal (or source ~/.bashrc) if the commands doesn't work
* You have to be either connected to the UiB VPN or run the commands via the computers in the lab to be able to connect to microserver
* If you are using another shell like zsh or csh the aliases has to be in ~/.zshrc or ~/.cshrc instead of ~/.bashrc
* Make sure you have replaced all the instances of USERNAME with your usename, i.e "fli091"

[[Category:Mikroelektronikk]]

File:ConnectToServer.png

2017-10-31T10:41:15Z

Fli091: Screenshot showing where to click to add a folder on a server

Screenshot showing where to click to add a folder on a server

MikroserverSetup

2017-10-31T08:43:56Z

Fli091: The aliases needed the &. Added it again

= Set-up of connection to mikroservers and cadence virtuoso =

This set-up will allow you to connect to the mikroservers and/or start Cadence virtuoso with one command without typing any password or host-names.

'''''NB: This setup is for TSMC, but the commands can be tweaked to be used with IHP or AMS too.'''''

The three mikroservers are :
* mikroserver1.klientdrift.uib.no
* mikroserver2.klientdrift.uib.no
* mikroserver3.klientdrift.uib.no

Do the following:

* Generate an ssh-key
ssh-keygen -f ~/.ssh/id.rsa -t rsa -N ''

* Copy the key with your identity to your chosen mikroserver (mikroserver3 is chosen in this example). NB: Replace USERNAME with your user name

ssh-copy-id USERNAME@mikroserver3.klientdrift.uib.no

* Set up aliases for the connections in your terminal
echo "alias mikroserver1='ssh -X USERNAME@mikroserver1.klientdrift.uib.no'" >> ~/.bashrc
echo "alias mikroserver2='ssh -X USERNAME@mikroserver2.klientdrift.uib.no'" >> ~/.bashrc
echo "alias mikroserver3='ssh -X USERNAME@mikroserver3.klientdrift.uib.no'" >> ~/.bashrc

Also create another alias for your favourite mikroserver
echo "alias mikroserver='ssh -X USERNAME@mikroserver3.klientdrift.uib.no'" >> ~/.bashrc

* source scripts inside .bashrc. This will make sure the scripts are loaded every time you log in, so you don't have to do it manually
# TSMC setup
echo "source /eda/cadence/2016-17/scripts/analog_flow.sh" >> ~/.bashrc
echo "source /eda/cadence/eda_general_init.sh" >> ~/.bashrc
# IHP setup
echo "source ~/ihp/cds/sh.cadence" >> ~/.bashrc

Then finally on the computers in the lab (NOT connected to the mikroservers)
echo "alias virtuoso_tsmc="ssh -X USERNAME@mikroserver3.klientdrift.uib.no 'cd tsmc;virtuoso &'"" >> ~/.bashrc
echo "alias virtuoso_ihp="ssh -X USERNAME@mikroserver3.klientdrift.uib.no 'cd ihp/cds;virtuoso &'"" >> ~/.bashrc

The next time you open your terminal on your computer you can type
virtuoso_tsmc
to start Cadence Virtuoso, or
mikroserver
to connect to mikroserver3 without any hassle!

== Troubleshooting ==
* Make sure you copy your ID (ssh-copy-id) to the correct mikroserver
* Make sure you have restarted your terminal (or source ~/.bashrc) if the commands doesn't work
* You have to be either connected to the UiB VPN or run the commands via the computers in the lab to be able to connect to microserver
* If you are using another shell like zsh or csh the aliases has to be in ~/.zshrc or ~/.cshrc instead of ~/.bashrc
* Make sure you have replaced all the instances of USERNAME with your usename, i.e "fli091"

[[Category:Mikroelektronikk]]

MikroserverSetup

2017-10-30T14:21:23Z

Fli091: Added a alias for launching IHP directly as the TSMCcommand and renamed the aliases from "virtuoso" to "virtuoso_tsmc"

= Set-up of connection to mikroservers and cadence virtuoso =

This set-up will allow you to connect to the mikroservers and/or start Cadence virtuoso with one command without typing any password or host-names.

'''''NB: This setup is for TSMC, but the commands can be tweaked to be used with IHP or AMS too.'''''

The three mikroservers are :
* mikroserver1.klientdrift.uib.no
* mikroserver2.klientdrift.uib.no
* mikroserver3.klientdrift.uib.no

Do the following:

* Generate an ssh-key
ssh-keygen -f ~/.ssh/id.rsa -t rsa -N ''

* Copy the key with your identity to your chosen mikroserver (mikroserver3 is chosen in this example). NB: Replace USERNAME with your user name

ssh-copy-id USERNAME@mikroserver3.klientdrift.uib.no

* Set up aliases for the connections in your terminal
echo "alias mikroserver1='ssh -X USERNAME@mikroserver1.klientdrift.uib.no'" >> ~/.bashrc
echo "alias mikroserver2='ssh -X USERNAME@mikroserver2.klientdrift.uib.no'" >> ~/.bashrc
echo "alias mikroserver3='ssh -X USERNAME@mikroserver3.klientdrift.uib.no'" >> ~/.bashrc

Also create another alias for your favourite mikroserver
echo "alias mikroserver='ssh -X USERNAME@mikroserver3.klientdrift.uib.no'" >> ~/.bashrc

* source scripts inside .bashrc. This will make sure the scripts are loaded every time you log in, so you don't have to do it manually
# TSMC setup
echo "source /eda/cadence/2016-17/scripts/analog_flow.sh" >> ~/.bashrc
echo "source /eda/cadence/eda_general_init.sh" >> ~/.bashrc
# IHP setup
echo "source ~/ihp/cds/sh.cadence" >> ~/.bashrc

Then finally on the computers in the lab (NOT connected to the mikroservers)
echo "alias virtuoso_tsmc="ssh -X USERNAME@mikroserver3.klientdrift.uib.no 'cd tsmc;virtuoso'"" >> ~/.bashrc
echo "alias virtuoso_ihp="ssh -X USERNAME@mikroserver3.klientdrift.uib.no 'cd ihp/cds;virtuoso'"" >> ~/.bashrc

The next time you open your terminal on your computer you can type
virtuoso_tsmc
to start Cadence Virtuoso, or
mikroserver
to connect to mikroserver3 without any hassle!

== Troubleshooting ==
* Make sure you copy your ID (ssh-copy-id) to the correct mikroserver
* Make sure you have restarted your terminal (or source ~/.bashrc) if the commands doesn't work
* You have to be either connected to the UiB VPN or run the commands via the computers in the lab to be able to connect to microserver
* If you are using another shell like zsh or csh the aliases has to be in ~/.zshrc or ~/.cshrc instead of ~/.bashrc
* Make sure you have replaced all the instances of USERNAME with your usename, i.e "fli091"

[[Category:Mikroelektronikk]]

IHP 130nm process

2017-10-30T14:19:48Z

Fli091: Removed uneccesary bash alias and linked to the setup page instead.

=Cadence design with IHP 130nm process=

==Starting up the IHP SG13S Design Kit==

The following steps describe how to install the Process Design Kit and start a new design.

Log on to server (mikroserver2 or mikroserver3):
ssh -X mikroserver2

The preferred shell is bash. When using another shell it will be necessary to change the installation routine and modify the initialization script accordingly.

The '''first time''' you are using the IHP design kit you should copy the user environment design to your chosen parent directory (e.g ~/ihp)
cp -rp /eda/design_kits/ihp_sg13/SG13S_616_rev1.5.0_a/work/skel ~/ihp

Change sh.cadence in ~/ihp/cds to suit your needs. In particular you must define $IHP_TECH and $PROJECT according to your local environment. Then set general and user Cadence environment variables by doing:
source /eda/cadence/2016-17/scripts/analog_flow.sh
cd ~/ihp/cds/
source sh.cadence
virtuoso &

To avoid having to do this every time try to set up your environment like described in [[MikroserverSetup]]

Follow the Design Kit User manual found in the menu SG13S Features > Design Kit Documentation. Make sure that your web browser is closed or started from the microserver, else the file will not be found.

[[Category:Mikroelektronikk]] [[Category:Integrated_Circuts]] [[Category:Cadence_Virtuoso]]

Transistor operating point printer

2017-10-26T19:44:30Z

Fli091: Added a script and description to get the file out from mikroserver and convert it to useable data

= DC operating parameters from simulation =
This script can be used to print the operating point parameters of all transistors in your design.

== Get the DC operating points from a previous simulation ==
Navigate to the folder you want to save the script in (this tutorial uses the home (./) directory) and create a new file in the terminal by entering <code> touch transistors.ocn </code>. Open the file by writing <code> gedit transistors.ocn & </code> and copy the following script into the document. Change ./transistors.csv in the script if you want another output file name and/or location. Save the file.
selectResult('dcOpInfo)
report(?output "./transistors.csv" ?param list("gm" "gmb" "gmoverid" "gds" "id" "idsat" "vth" "region" "cgs" "cgd" "self_gain" "type" "vds" "vdsat" "vgs") ?format "spice" ?maxLineWidth 1000)

file = outfile("./transistors.csv" "a")
fprintf(file "\n\nRegion 0 is cutoff.\nRegion 1 is linear.\nRegion 2 is saturation .\nRegion 3 is subthreshold.\nRegion 4 is breakdown.\n\nType 0 is nMOS. \nType 1 is pMOS.")
close(file)

For the IHP design kit use:
selectResult('dcOpInfo)
report(?output "./transistors.csv" ?param list("model" "gm" "gmb" "gds" "ids" "idsat" "vth" "region" "cgs" "cgd" "vds" "vsat" "vgs") ?format "spice" ?maxLineWidth 1000)

file = outfile("./transistors.csv" "a")
fprintf(file "\n\nRegion 0 is cutoff.\nRegion 1 is linear.\nRegion 2 is saturation .\nRegion 3 is subthreshold.\nRegion 4 is breakdown.\n\nType 0 is nMOS. \nType 1 is pMOS.")
close(file)

This script uses the results from the previous Debug Test (from ADE XL Test Editor). Before running the script, run a Debug Test with DC analysis:

[[File:Run_debug_simulation.png | 500px]]

After running DC analysis, run the script by entering the following into the Virtuoso Log Window (with file name and location as mentioned above): <code>load("./transistors.ocn")</code>

[[File:Run_transistors_script.png]]

== Copy the file to your computer and convert the values ==
After running the script, you can open the results file from the terminal using for example: <code> gedit transistors.csv & </code> or alternatively to get the file out from mikroserver
to another computer try this:

Create a file named "Makefile" and put this into it:

all: get fix clean

get :
scp fli091@mikroserver3.ift.uib.no:~/tsmc/transistors.csv ~/transistors_raw.csv

fix :
sed -e 's/$[0-9]\+$m/\1E-3/g' -e 's/$[0-9]\+$u/\1E-6/g' -e 's/$[0-9]\+$n/\1E-9/g' -e 's/$[0-9]\+$p/\1E-12/g' -e 's/$[0-9]\+$f/\1E-15/g' -e 's/$[0-9]\+$a/\1E-18/g' -e 's/$[0-9]\+$z/\1E-21/g' -e 's/$[0-9]\+$y/\1E-24/g' -e 's/$[0-9]\+$K/\1E+3/g' -e 's/$[0-9]\+$M/\1E+6/g' -e 's/$[0-9]\+$G/\1E+9/g' -e 's/$[0-9]\+$T/\1E+12/g' transistors_raw.csv > transistors.csv

clean:
rm transistors_raw.csv

Modify the scp-command to use
* The username(and not fli091) in the scp-command
* change mikroserver if you are not using mikroserver3.
* change the folder on mikroserver where the transistors.csv is created, default is /home/$user/tsmc/
* change the local folder where you want your copy to be placed, default is /home/$user/

A short explanation of the Makefile
* The get-target gets the file from mikroserver3 and copies it to your computer in the root of your homefolder
* The fix-target converts transitors.csv to a copy where all the postfixes for the SI units generated from Virtuoso (m, f, K etc), has been replaced with E-3, E-15, E+3 etc, so the values are useable in LibreOffice
* The clean-target just removes the not-fixed copy

Now you can type <code>make</code> in the folder you created the Makefile and the latestst simulation data will appear in your homefolder.

== Open the file in Libre Office ==
The resulting transistors.csv can then be imported into LibreOffice Calc (similar to Microsoft Excel) using File->Open, then choose the .csv file and enter the settings as in the following image:

[[File:Csv_import_libreoffice.png | 500px]]

== Troubleshooting ==
For the scp-command to work without password you have to set up your connection as described in [[MikroserverSetup]]

[[Category:Mikroelektronikk]] [[Category:Integrated_Circuts]]

Transistor operating point printer

2017-10-23T14:53:53Z

Fli091: Added sed command to convert transistors.csv

= DC operating parameters from simulation =
This script can be used to print the operating point parameters of all transistors in your design.

Navigate to the folder you want to save the script in (this tutorial uses the home (./) directory) and create a new file in the terminal by entering <code> touch transistors.ocn </code>. Open the file by writing <code> gedit transistors.ocn & </code> and copy the following script into the document. Change ./transistors.csv in the script if you want another output file name and/or location. Save the file.
selectResult('dcOpInfo)
report(?output "./transistors.csv" ?param list("gm" "gmb" "gmoverid" "gds" "id" "idsat" "vth" "region" "cgs" "cgd" "self_gain" "type" "vds" "vdsat" "vgs") ?format "spice" ?maxLineWidth 1000)

file = outfile("./transistors.csv" "a")
fprintf(file "\n\nRegion 0 is cutoff.\nRegion 1 is linear.\nRegion 2 is saturation .\nRegion 3 is subthreshold.\nRegion 4 is breakdown.\n\nType 0 is nMOS. \nType 1 is pMOS.")
close(file)

For the IHP design kit use:
selectResult('dcOpInfo)
report(?output "./transistors.csv" ?param list("model" "gm" "gmb" "gds" "ids" "idsat" "vth" "region" "cgs" "cgd" "vds" "vsat" "vgs") ?format "spice" ?maxLineWidth 1000)

file = outfile("./transistors.csv" "a")
fprintf(file "\n\nRegion 0 is cutoff.\nRegion 1 is linear.\nRegion 2 is saturation .\nRegion 3 is subthreshold.\nRegion 4 is breakdown.\n\nType 0 is nMOS. \nType 1 is pMOS.")
close(file)

This script uses the results from the previous Debug Test (from ADE XL Test Editor). Before running the script, run a Debug Test with DC analysis:

[[File:Run_debug_simulation.png | 500px]]

After running DC analysis, run the script by entering the following into the Virtuoso Log Window (with file name and location as mentioned above): <code>load("./transistors.ocn")</code>

[[File:Run_transistors_script.png]]

After running the script, you can open the results file from the terminal using for example: <code> gedit transistors.csv & </code>

The results file can also be imported into LibreOffice Calc (similar to Microsoft Excel) using File->Open, then choose the .csv file and enter the settings as in the following image:

[[File:Csv_import_libreoffice.png | 500px]]

== Importing the data into LibreOffice ==

To use transistors.csv one has to get rid of the postfixes for the SI units generated from Virtuoso (m, f, K etc). To do this navigate to the folder with the transistors.csv and type this command:
sed -e 's/$[0-9]\+$m/\1E-3/g' -e 's/$[0-9]\+$u/\1E-6/g' -e 's/$[0-9]\+$n/\1E-9/g' -e 's/$[0-9]\+$p/\1E-12/g' -e 's/$[0-9]\+$f/\1E-15/g' -e 's/$[0-9]\+$a/\1E-18/g' -e 's/$[0-9]\+$z/\1E-21/g' -e 's/$[0-9]\+$y/\1E-24/g' -e 's/$[0-9]\+$K/\1E+3/g' -e 's/$[0-9]\+$M/\1E+6/g' -e 's/$[0-9]\+$G/\1E+9/g' -e 's/$[0-9]\+$T/\1E+12/g' transistors.csv > transistors_fixed.csv
That converts transitors.csv to transistors_fixed.csv where all the SI-symbols has been replaced with E-3, E-15, E+3 etc, so the values are useable in LibreOffice

[[Category:Mikroelektronikk]] [[Category:Integrated_Circuts]]

Tips

2017-10-23T09:00:21Z

Fli091: Added categories / Category:Mikroelektronikk Category:Integrated_Circuts

==Estimere delay av en og to invertere i serie==

1. Høyre klikk i cell view i library vinduet og velg "New Cell View".

2. Kall det delay, velg schematic i dropdown menyen og trykk finish.

3. Trykk "Add instance" på venstre side, velg inverteren du nettop laget og trykk OK.

4. Lag tre invertere i serie ved å merke den du la til og trykke C på tastaturet.

5. Velg "Add->Source", merk av DC og sett spenningen til 3.3V

6. Trykk på "HIT-Kit Utilities->AMS Library" på fil-menyen.

7. Legg til VDD og GND. De ligger under "etc->cell power->vdd_g" for VDD og "etc->cell power->gnda_g" for GND

8. Legg til puls kilde ved å velge "Add->Source", merk av PULSE og sett verdiene som vist på bildet.

[[File:pulse.jpg|400px]]

9. Legg til kabler som på bildet under.

10. Sett navn på nettet mellom første og andre inverter ved å velge den og trykke på "Net name", kall den out1. Kall nettet mellom inverter 2 og 3 for out2. Kall nettet etter kilden for in.

[[File:skjema.jpg|600px]]

11. Trykk "Check & Save". Trykk "HIT-Kit Utilities->Create Viewpoint", trykk navigator og finn frem til mappen der prosjektet dit er i, $navn_på_library/default.group/logic.views/delay
Ikke åpne delay mappen, bare merk den.

12. Trykk "Enter simulation mode" og trykk ok på vinduet som kommer opp.

13. Velg "Session->netlister" på høyre side og sjekk at det står gnda i "Set Node 0" feltet.

14. Velg Analysis på høyre side, hak av for transient(ta vekk AC), trykk på setup ved siden av transient og sett stop time til 3n og max step time til 10p.

15. Hold nede CTRL og velg in, out1 og out2 nettene. Trykk så på "Wave outputs" på høyre side.

16. Velg alle nettene under objects, velg TRAN under analysis og trykk på knappen med en tegning av ett ark med et pluss tegn på, trykk krysset for å lukke.

17. Velg "HIT-Kit Utilities->Set simulation models", trykk ok på vinduet.

18. Trykk "Run ELDO" og når det er ferdig å flytte på seg i tekstruten som kommer opp kan du trykke "View waves"

19. Ekspander tran mappen på venstre side, merk alle tre plottene med ctrl, høyreklikk og velg plot stacked.

20. Trykk CTRL+M for å få opp measurement tool. Velg Time domain under measurement. Trykk på V(IN) på plottet i bakgrunnen(uten å lukke measurement tool) og trykk på knappen med bilde av en graf på på linjen til #1. Trykk så på V(Out1) og på knappen til #2.
Under Edge trigger trykker du på oppadgående flanke, under edge relationship velger du inverting, hak av for find closest reference edge og trykk apply. Skift edge trigger til nedadgående og trykk apply igjen.

21. Gjør det samme som over men velg V(out2) istedet for V(out1) og skift edge relationship til non-inverting.

22. Du får nå opp tpdf og tpdr på grafen.

[[File:graf.jpg]]

== Andre tips til oppgaven ==
Fungerer ikke dynamiske eller statiske vippen?

Sjekk at du har plassert clock og clock invers på riktig inngang/riktig transistor, de skifter side fra første til andre ledd.

Prøv å bruke Cgs til kalkulering av delay om du ikke får noe fornuftig svar.

Når du skal lage clk invers så er det en fordel å ikke bruke en inverter, lag to pulskilder der den ene har et delay like langt som en pulsbredde, ellers så får du et ekstra delay på klokken aka clock skew.

Tristate bufferet kan regnes som parasitisk, mao tilfører den 8C på inngangen og utgangen.

Transmition gaten kobles opp med source mot kilden. Kobl bulk for nmos til gnd og pmos til VDD.

Blir utsignalet bare bølgete rundt VDD så har du for kort pulslengde, hold deg over 2ns.

[[Category:Mikroelektronikk]]
[[Category:Integrated_Circuts]]

Cadence Virtuoso overview

2017-10-18T10:37:51Z

Fli091: Some text to the different IC processes

= IC design flow using Cadence =

We have access to several silicon technologies from different foundries

* 130nm CMOS process from Taiwan Semiconductor Manufacturing: '''[[ TSMC 130nm process ]]'''
* 130nm SiGe process from Innovations for High Performance Microelectronics: '''[[ IHP 130nm process ]]'''
* 350nm CMOS process from Austria Mikro Systeme: '''[[ AMS 350nm process ]]'''

= Simulation =

[[Testbench|Virtuoso Testbench]]

= Layout =

[[Layout XL and IHP SG13S]]

=Helpful stuff=
[[MikroserverSetup]] - setup for easy connection to the mikroservers and Cadence Virtuoso

[[ Transistor operating point printer ]] - Script to extract transistor operating point parameters after simulation.

[[ ADEXL-butterfly-curves ]] - Howto make DC butterfly curves easily.

[[Category:Mikroelektronikk]] [[Category:Integrated_Circuts]]

MikroserverSetup

2017-10-18T10:32:14Z

Fli091: Actually sourcing the IHPscript too

MikroserverSetup

2017-10-18T10:31:23Z

Fli091: Sourcing the script for IPH in .bashrc

MikroserverSetup

2017-10-18T10:19:32Z

Fli091: TSMC warning and fixed typos

User talk:Fli091

2017-10-14T14:29:44Z

Fli091: Kill the red links

MikroserverSetup

2017-10-14T14:27:57Z

Fli091: Fixed typo

= Setup of connection to mikroservers and cadence virtuoso =

This setup will allow you to connect to the mikroservers and/or start Cadence virtuoso with one command without typing any password or hostnames

The three mikroservers are :
* mikroserver1.klientdrift.uib.no
* mikroserver2.klientdrift.uib.no
* mikroserver3.klientdrift.uib.no

Do the following:

* Generate an ssh-key
ssh-keygen -f ~/.ssh/id.rsa -t rsa -N ''

* Copy the key with your identity to your chosen mikroserver (mikroserver3 is chosen in this example). NB: Replace USERNAME with your usename

ssh-copy-id USENAME@mikroserver3.klientdrift.uib.no

* Set up aliases for the connections in your terminal
echo "alias mikroserver1='ssh -X USERNAME@mikroserver1.klientdrift.uib.no'" >> ~/.bashrc
echo "alias mikroserver2='ssh -X USERNAME@mikroserver2.klientdrift.uib.no'" >> ~/.bashrc
echo "alias mikroserver3='ssh -X USERNAME@mikroserver3.klientdrift.uib.no'" >> ~/.bashrc

Also create another alias for your favourite mikroserver
echo "alias mikroserver='ssh -X USERNAME@mikroserver3.klientdrift.uib.no'" >> ~/.bashrc

* source scripts inside .bashrc. This will make sure the scripts are loaded every time you log in, so you don't have to do it manually
echo "source /eda/cadence/2016-17/scripts/analog_flow.sh" >> ~/.bashrc
echo "source /eda/cadence/eda_general_init.sh" >> ~/.bashrc

Then finally on the computers in the lab (NOT connected to the mikroservers)
echo "alias virtuoso="ssh -X USERNAME@mikroserver3.klientdrift.uib.no 'cd tsmc;virtuoso'&"" >> ~/.bashrc

The next time you open your terminal on your computer you can type
virtuoso
to start Cadence Virtuoso, or
mikroserver
to connect to mikroserver3 without any hassle!

== Troubleshooting ==
* Make sure you copy your ID (ssh-copy-id) to the correct mikroserver
* Make sure you have restarted your terminal (or source ~/.bashrc) if the commands doesn't work
* You have to be either connected to the UiB VPN or run the commands via the computers in the lab to be able to connect to microserver
* If you are using another shell like zsh or csh the aliases has to be in ~/.zshrc or ~/.cshrc instead of ~/.bashrc
* Make sure you have replaced all the instances of USERNAME with your usename, i.e "fli091"

[[Category:Mikroelektronikk]]

MikroserverSetup

2017-10-14T14:15:37Z

Fli091: Added Category:Mikroelektronikk

= Setup of connection to mikroservers and cadence virtuoso =

This setup will allow you to connect to the mikroservers and/or start Cadence virtuoso with one command without typing any password or hostnames

The three mikroservers are :
* mikroserver1.klientdrift.uib.no
* mikroserver2.klientdrift.uib.no
* mikroserver3.klientdrift.uib.no

Do the following:

* Generate an ssh-key
ssh-keygen -f ~/.ssh/id.rsa -t rsa -N ''

* Copy the key with your identity to your chosen mikroserver (mikroserver3 is chosen in this example). NB: Replace USERNAME with your usename

ssh-copy-id USENAME@mikroserver3.klientdrift.uib.no

* Set up aliases for the connections in your terminal
echo "alias mikroserver1='ssh -X USERNAME@mikroserver1.klientdrift.uib.no'" >> ~/.bashrc
echo "alias mikroserver2='ssh -X USERNAME@mikroserver2.klientdrift.uib.no'" >> ~/.bashrc
echo "alias mikroserver3='ssh -X USERNAME@mikroserver3.klientdrift.uib.no'" >> ~/.bashrc

Also create another alias for your favourite mikroserver
echo "alias mikroserver='ssh -X USERNAME@mikroserver3.klientdrift.uib.no'" >> ~/.bashrc

* source scripts inside .bashrc. This will make sure the scripts are loaded every time you log in, so you don't have to do it manually
echo "source /eda/cadence/2016-17/scripts/analog_flow.sh" >> ~/.bashrc
echo "source /eda/cadence/eda_general_init.sh" >> ~/.bashrc

Then finally on the computers in the lab (NOT connected to the mikroservers)
echo "alias virtuoso="ssh -X USERNAME@mikroserver3.klientdrift.uib.no 'cd tsmc;virtuoso'&"" >> ~/.bashrc

The next time you open your terminal on your computer you can type
virtuoso
to start cadence virutoso, or
mikroserver
to connect to mikroserver3 without any hassle!

== Troubleshooting ==
* Make sure you copy your ID (ssh-copy-id) to the correct mikroserver
* Make sure you have restarted your terminal (or source ~/.bashrc) if the commands doesn't work
* You have to be either connected to the UiB VPN or run the commands via the computers in the lab to be able to connect to microserver
* If you are using another shell like zsh or csh the aliases has be in ~/.zshrc or ~/.cshrc instead of ~/.bashrc
* Make sure you have replaced all the USERNAME with your usename, i.e "fli091"

[[Category:Mikroelektronikk]]

Cadence Virtuoso overview

2017-10-14T14:15:27Z

Fli091: Added link to setup of mikroservers

=Analog IC design flow using Cadence from basics (Schematic capture, Netlist extraction, Simulating using ELDO, Layout, Signoff Layout)=

[[ TSMC 130nm process ]]

[[ IHP 130nm process ]]

[[ AMS 350nm process ]]

= Simulation =

[[Testbench|Virtuoso Testbench]]

= Layout =

[[Layout XL and IHP SG13S]]

=Helpful stuff=
[[MikroserverSetup]] - setup for easy connection to the mikroservers and Cadence Virtuoso

[[ Transistor operating point printer ]] - Script to extract transistor operating point parameters after simulation.

[[ ADEXL-butterfly-curves ]] - Howto make DC butterfly curves easily.

[[Category:Mikroelektronikk]] [[Category:Integrated_Circuts]]

MikroserverSetup

2017-10-14T14:14:14Z

Fli091: created page

= Setup of connection to mikroservers and cadence virtuoso =

This setup will allow you to connect to the mikroservers and/or start Cadence virtuoso with one command without typing any password or hostnames

The three mikroservers are :
* mikroserver1.klientdrift.uib.no
* mikroserver2.klientdrift.uib.no
* mikroserver3.klientdrift.uib.no

Do the following:

* Generate an ssh-key
ssh-keygen -f ~/.ssh/id.rsa -t rsa -N ''

* Copy the key with your identity to your chosen mikroserver (mikroserver3 is chosen in this example). NB: Replace USERNAME with your usename

ssh-copy-id USENAME@mikroserver3.klientdrift.uib.no

* Set up aliases for the connections in your terminal
echo "alias mikroserver1='ssh -X USERNAME@mikroserver1.klientdrift.uib.no'" >> ~/.bashrc
echo "alias mikroserver2='ssh -X USERNAME@mikroserver2.klientdrift.uib.no'" >> ~/.bashrc
echo "alias mikroserver3='ssh -X USERNAME@mikroserver3.klientdrift.uib.no'" >> ~/.bashrc

Also create another alias for your favourite mikroserver
echo "alias mikroserver='ssh -X USERNAME@mikroserver3.klientdrift.uib.no'" >> ~/.bashrc

* source scripts inside .bashrc. This will make sure the scripts are loaded every time you log in, so you don't have to do it manually
echo "source /eda/cadence/2016-17/scripts/analog_flow.sh" >> ~/.bashrc
echo "source /eda/cadence/eda_general_init.sh" >> ~/.bashrc

Then finally on the computers in the lab (NOT connected to the mikroservers)
echo "alias virtuoso="ssh -X USERNAME@mikroserver3.klientdrift.uib.no 'cd tsmc;virtuoso'&"" >> ~/.bashrc

The next time you open your terminal on your computer you can type
virtuoso
to start cadence virutoso, or
mikroserver
to connect to mikroserver3 without any hassle!

== Troubleshooting ==
* Make sure you copy your ID (ssh-copy-id) to the correct mikroserver
* Make sure you have restarted your terminal (or source ~/.bashrc) if the commands doesn't work
* You have to be either connected to the UiB VPN or run the commands via the computers in the lab to be able to connect to microserver
* If you are using another shell like zsh or csh the aliases has be in ~/.zshrc or ~/.cshrc instead of ~/.bashrc
* Make sure you have replaced all the USERNAME with your usename, i.e "fli091"

TSMC 130nm process

2017-10-13T10:00:24Z

Fli091: Updated the setup. Now it works!

=Cadence design with TSMC 130nm process=
This tutorial will start from very basics in analog IC design then take you through the whole analog IC design process.

Here is the outline of the analog IC design flow:
# Schematic capture (Cadence tool)
# Netlist extraction from schematic
# Simulating using ELDO simulator and viewing results with EZWAVE (ELDO is a Mentor Graphic's tool for netlist level simulations)
# Layout using Cadence
# Signoff layout (DRC, LVS and parasitic extraction) using Calibre (Calibre is a Mentor Graphic's tool)

==Setup of Cadence==

To start virtuoso one must first connect to mikroserver3
ssh -X mikroserver3

'''First''' time you should add the following line to your cds.lib-file by running this command:
mkdir ~/tsmc
echo "DEFINE tsmc13rf /eda/design_kits/tsmc_013/tsmc13rf" > ~/tsmc/cds.lib

Then ('''each time''') run these commands to set up Cadence
source /eda/cadence/2016-17/scripts/analog_flow.sh
source /eda/cadence/eda_general_init.sh

Virtuoso Mixed Signal Design Environment is started by issuing this command:
virtuoso &

=== Troubleshooting ===
* Make sure you source the script from the correct year. I.e 2016-17 and not 2015-16
* Make sure you are connected the the right mikroserver
* Make sure you run virtuoso from the same folder as your 'cds.lib'-folder ('~/tsmc/')

== Getting started ==

In the log window, choose "File > New > Library".

In the "New Library" dialog box, you must give the library a name (for example TORLIB, as I did). You must also specify a technology file. Here you choose "Attach to an existing technology library". Then click the OK button. When asked for technology, choose "tsmc13rf".

After successfully creating the new library, it is time to create your first design. In the log window, choose "File > New > Cellview". In the "Create New File" dialog box, you must give the design a name. You must also specify which library the design belongs to, and here you specify the library that you have just created. Choose to open the cell with "Schematics XL" and add a check-mark to always use this application if it is not checked.

Now click OK, and the Virtuoso Schematic Editor should pop up. We will now draw a simple inverter design, as shown in the picture:

[[File:virtuoso_schematic_editor.png|400px]]

==Entering the design==
To create the inverter design, do the following:

# Press 'i' or click on the "Instance" icon to invoke the transistors. The "Add Instance" dialog box will now pop up. In the "Library" field, click "Browse" to open the "Library Browser". In the library browser, choose "tsmc13rf" as library, "nmos3v" (for n-type transistor) or "pmos3v" (for p-type transistor) as cell and "spectre" as view. The cell is placed in the schematic by moving the cursor to the desired location and clicking the left mouse button.
# To insert the voltage sources, pick the "vdc" cell from the "analogLib" library. Add one connected to vdd and gnd and one connected to the input.
# To insert the ground and vdd nets, pick the "vdd" and "gnd" cells from the "analogLib" library. Here the view name should be "symbol", not "spectreS" (in fact, "symbol" is the only available option).
# To connect the symbols, press 'w' or click the "Wire (narrow)" icon. Then use the left mouse button to click the nodes togeter, two by two.
# To remove an instance or a wire, left click at the instance or wire that you want to remove, then press the "Delete" button on the keyboard.
# To insert a pin, press 'p'. Choose a name for the pin in the dialog that occurs and click on the schematic to place it. Create one input and one output.
# To change the properties of the icons, press 'q' or click at the "Properties" icon. Then click at the instances or nets that you want to modify. For the vdc source connected between vdd and gnd, set the "DC voltage" property to 3.3.
# To check and save the schematic, press 'x' or click the "Check and save" icon.
# If there are any errors or warnings, press ok and press 'g' or "Check->Find Marker" to view the errors. Make sure you have no errors or warnings before continuing.
# Then open "Launch > ADE GXL" and press create new view. The "Virtuoso Analog Environment" should now come up.

==Simulating the design==

# Choose "Create > Test..." select the cell to simulate.
# Choose "Outputs > To be plotted > Select on Schematic". Click at the "in" node connected to the inverter input and the "out" node connected to the output.
# Choose "Analyses > Choose". We will now run a dc analysis to obtain the DC transfer characteristics of the inverter. Choose "Component parameter" as your sweep variable. Then click at "Select component". In the schematic, click at the input "vdc" instance. In the "Select Component Parameter" dialog box, choose dc as your sweep parameter. The sweep range should go from 0 to 3.3.
[[File:select_comp_parameter.png|300px]]
The analog environment should now look like this:
[[File:analog_env_2.png|500px]]
# Switch to the "adexl" tab and choose the green run button. When the run is completed press the graph button beside the box that says "Replace". The outputs should look like this:
[[File:plot_output_dc.png|600px]]

To save your simulation settings, choose "Session > Save state" in the test editor windoe to save your state information under whatever file name you want. In a later session, you can reload your saved states using "Session > Load state".

==Generating a Symbol==
Finally, we want to generate a symbol for our inverter. This symbol is needed if we want to use our inverter design inside another design (hierarchical design methodology).

Select the schematic tab and choose "Create -> Create Cellview -> From Cellview".

Press OK in the dialog that occurs.

The pins should already be connected to the right positions in the symbol generator, so press OK here also and ths symbol editor will occur.

Press the red X and delete the pre-created green square. Use the line tool and the circle tool to create the inverter symbol

[[File:symbol.png|400px]]

Save it by clicking the "Save and check" symbol or pressing 'shift+X'.

[[Category:Mikroelektronikk]] [[Category:Integrated_Circuts]]

TSMC 130nm process

2017-10-13T07:04:38Z

Fli091: Put "first" in bold and added command to echo define into cds.lib

=Cadence design with TSMC 130nm process=

==Starting up==
This tutorial will start from very basics in analog IC design then take you through the whole analog IC design process.

Here is the outline of the analog IC design flow:
# Schematic capture (Cadence tool)
# Netlist extraction from schematic
# Simulating using ELDO simulator and viewing results with EZWAVE (ELDO is a Mentor Graphic's tool for netlist level simulations)
# Layout using Cadence
# Signoff layout (DRC, LVS and parasitic extraction) using Calibre (Calibre is a Mentor Graphic's tool)

ssh -X mikroserver2
source /eda/cadence/cadence_init.sh

'''First''' time you should add the following line to your cds.lib file before starting the design environment. If the ~/cds.lib doesn't exist, just create it.
echo "DEFINE tsmc13rf /eda/design_kits/tsmc_013/tsmc13rf" > cds.lib

Virtuoso Mixed Signal Design Environment is started by issuing this command:
tsmc_cds_start

In the log window, choose "File > New > Library".

In the "New Library" dialog box, you must give the library a name (for example TORLIB, as I did). You must also specify a technology file. Here you choose "Attach to an existing technology library". Then click the OK button. When asked for technology, choose "tsmc13rf".

After successfully creating the new library, it is time to create your first design. In the log window, choose "File > New > Cellview". In the "Create New File" dialog box, you must give the design a name. You must also specify which library the design belongs to, and here you specify the library that you have just created. Choose to open the cell with "Schematics XL" and add a check-mark to always use this application if it is not checked.

Now click OK, and the Virtuoso Schematic Editor should pop up. We will now draw a simple inverter design, as shown in the picture:

[[File:virtuoso_schematic_editor.png|400px]]

==Entering the design==
To create the inverter design, do the following:

# Press 'i' or click on the "Instance" icon to invoke the transistors. The "Add Instance" dialog box will now pop up. In the "Library" field, click "Browse" to open the "Library Browser". In the library browser, choose "tsmc13rf" as library, "nmos3v" (for n-type transistor) or "pmos3v" (for p-type transistor) as cell and "spectre" as view. The cell is placed in the schematic by moving the cursor to the desired location and clicking the left mouse button.
# To insert the voltage sources, pick the "vdc" cell from the "analogLib" library. Add one connected to vdd and gnd and one connected to the input.
# To insert the ground and vdd nets, pick the "vdd" and "gnd" cells from the "analogLib" library. Here the view name should be "symbol", not "spectreS" (in fact, "symbol" is the only available option).
# To connect the symbols, press 'w' or click the "Wire (narrow)" icon. Then use the left mouse button to click the nodes togeter, two by two.
# To remove an instance or a wire, left click at the instance or wire that you want to remove, then press the "Delete" button on the keyboard.
# To insert a pin, press 'p'. Choose a name for the pin in the dialog that occurs and click on the schematic to place it. Create one input and one output.
# To change the properties of the icons, press 'q' or click at the "Properties" icon. Then click at the instances or nets that you want to modify. For the vdc source connected between vdd and gnd, set the "DC voltage" property to 3.3.
# To check and save the schematic, press 'x' or click the "Check and save" icon.
# If there are any errors or warnings, press ok and press 'g' or "Check->Find Marker" to view the errors. Make sure you have no errors or warnings before continuing.
# Then open "Launch > ADE GXL" and press create new view. The "Virtuoso Analog Environment" should now come up.

==Simulating the design==

# Choose "Create > Test..." select the cell to simulate.
# Choose "Outputs > To be plotted > Select on Schematic". Click at the "in" node connected to the inverter input and the "out" node connected to the output.
# Choose "Analyses > Choose". We will now run a dc analysis to obtain the DC transfer characteristics of the inverter. Choose "Component parameter" as your sweep variable. Then click at "Select component". In the schematic, click at the input "vdc" instance. In the "Select Component Parameter" dialog box, choose dc as your sweep parameter. The sweep range should go from 0 to 3.3.
[[File:select_comp_parameter.png|300px]]
The analog environment should now look like this:
[[File:analog_env_2.png|500px]]
# Switch to the "adexl" tab and choose the green run button. When the run is completed press the graph button beside the box that says "Replace". The outputs should look like this:
[[File:plot_output_dc.png|600px]]

To save your simulation settings, choose "Session > Save state" in the test editor windoe to save your state information under whatever file name you want. In a later session, you can reload your saved states using "Session > Load state".

==Generating a Symbol==
Finally, we want to generate a symbol for our inverter. This symbol is needed if we want to use our inverter design inside another design (hierarchical design methodology).

Select the schematic tab and choose "Create -> Create Cellview -> From Cellview".

Press OK in the dialog that occurs.

The pins should already be connected to the right positions in the symbol generator, so press OK here also and ths symbol editor will occur.

Press the red X and delete the pre-created green square. Use the line tool and the circle tool to create the inverter symbol

[[File:symbol.png|400px]]

Save it by clicking the "Save and check" symbol or pressing 'shift+X'.

[[Category:Mikroelektronikk]] [[Category:Integrated_Circuts]]

IHP 130nm process

2017-10-10T14:02:41Z

Fli091: Specified mikroserver2 or mikroserver3 (1 does not work atm)

=Cadence design with IHP 130nm process=

==Starting up the IHP SG13S Design Kit==

The following steps describe how to install the Process Design Kit and start a new design.

Log on to server (mikroserver2 or mikroserver3):
ssh -X mikroserver2

The preferred shell is bash. When using another shell it will be necessary to change the installation routine and modify the initialization script accordingly.

The '''first time''' you are using the IHP design kit you should copy the user environment design to your chosen parent directory (e.g ~/ihp)
cp -rp /eda/design_kits/ihp_sg13/SG13S_616_rev1.5.0_a/work/skel ~/ihp

Change sh.cadence in ~/ihp/cds to suit your needs. In particular you must define $IHP_TECH and $PROJECT according to your local environment. Then set general and user Cadence environment variables by doing:
source /eda/cadence/2016-17/scripts/analog_flow.sh
cd ~/ihp/cds/
source sh.cadence
virtuoso &

To create a command that will do this for you try this command:
echo "alias startVirtuoso='source /eda/cadence/2016-17/scripts/analog_flow.sh && cd ~/ihp/cds/ && source sh.cadence && virtuoso &'" >> ~/.bashrc
Typing 'startVirtuoso' in the terminal will execute these four commands

Follow the Design Kit User manual found in the menu SG13S Features > Design Kit Documentation. Make sure that your web browser is closed or started from the microserver, else the file will not be found.

[[Category:Mikroelektronikk]] [[Category:Integrated_Circuts]]

Category:Integrated Circuts

2017-09-15T13:32:50Z

Fli091: Created mikroelektronikk subcategory integrated_circuits

[[Category:Mikroelektronikk]]

Transistor operating point printer

2017-09-15T13:32:07Z

Fli091: Added Category:Integrated_Circuts

This script can be used to print the operating point parameters of all transistors in your design.

Navigate to the folder you want to save the script in (this tutorial uses the home (./) directory) and create a new file in the terminal by entering <code> touch transistors.ocn </code>. Open the file by writing <code> gedit transistors.ocn & </code> and copy the following script into the document. Change ./transistors.csv in the script if you want another output file name and/or location. Save the file.
selectResult('dcOpInfo)
report(?output "./transistors.csv" ?param list("gm" "gmb" "gmoverid" "gds" "id" "idsat" "vth" "region" "cgs" "cgd" "self_gain" "type" "vds" "vdsat" "vgs") ?format "spice" ?maxLineWidth 1000)

file = outfile("./transistors.csv" "a")
fprintf(file "\n\nRegion 0 is cutoff.\nRegion 1 is linear.\nRegion 2 is saturation .\nRegion 3 is subthreshold.\nRegion 4 is breakdown.\n\nType 0 is nMOS. \nType 1 is pMOS.")
close(file)

For the IHP design kit use:
selectResult('dcOpInfo)
report(?output "./transistors.csv" ?param list("model" "gm" "gmb" "gds" "ids" "idsat" "vth" "region" "cgs" "cgd" "vds" "vsat" "vgs") ?format "spice" ?maxLineWidth 1000)

file = outfile("./transistors.csv" "a")
fprintf(file "\n\nRegion 0 is cutoff.\nRegion 1 is linear.\nRegion 2 is saturation .\nRegion 3 is subthreshold.\nRegion 4 is breakdown.\n\nType 0 is nMOS. \nType 1 is pMOS.")
close(file)

This script uses the results from the previous Debug Test (from ADE XL Test Editor). Before running the script, run a Debug Test with DC analysis:

[[File:Run_debug_simulation.png | 500px]]

After running DC analysis, run the script by entering the following into the Virtuoso Log Window (with file name and location as mentioned above): <code>load("./transistors.ocn")</code>

[[File:Run_transistors_script.png]]

After running the script, you can open the results file from the terminal using for example: <code> gedit transistors.csv & </code>

The results file can also be imported into LibreOffice Calc (similar to Microsoft Excel) using File->Open, then choose the .csv file and enter the settings as in the following image:

[[File:Csv_import_libreoffice.png | 500px]]

[[Category:Mikroelektronikk]] [[Category:Integrated_Circuts]]

TSMC 130nm process

2017-09-15T13:31:55Z

Fli091: Added Category:Integrated_Circuts

=Cadence design with TSMC 130nm process=

==Starting up==
This tutorial will start from very basics in analog IC design then take you through the whole analog IC design process.

Here is the outline of the analog IC design flow:
# Schematic capture (Cadence tool)
# Netlist extraction from schematic
# Simulating using ELDO simulator and viewing results with EZWAVE (ELDO is a Mentor Graphic's tool for netlist level simulations)
# Layout using Cadence
# Signoff layout (DRC, LVS and parasitic extraction) using Calibre (Calibre is a Mentor Graphic's tool)

ssh -X mikroserver2
source /eda/cadence/cadence_init.sh

First time you should add the following line to your cds.lib file before starting the design environment. If the ~/cds.lib doesn't exist, just create it.
DEFINE tsmc13rf /eda/design_kits/tsmc_013/tsmc13rf

Virtuoso Mixed Signal Design Environment is started by issuing this command:
tsmc_cds_start

In the log window, choose "File > New > Library".

In the "New Library" dialog box, you must give the library a name (for example TORLIB, as I did). You must also specify a technology file. Here you choose "Attach to an existing technology library". Then click the OK button. When asked for technology, choose "tsmc13rf".

After successfully creating the new library, it is time to create your first design. In the log window, choose "File > New > Cellview". In the "Create New File" dialog box, you must give the design a name. You must also specify which library the design belongs to, and here you specify the library that you have just created. Choose to open the cell with "Schematics XL" and add a check-mark to always use this application if it is not checked.

Now click OK, and the Virtuoso Schematic Editor should pop up. We will now draw a simple inverter design, as shown in the picture:

[[File:virtuoso_schematic_editor.png|400px]]

==Entering the design==
To create the inverter design, do the following:

# Press 'i' or click on the "Instance" icon to invoke the transistors. The "Add Instance" dialog box will now pop up. In the "Library" field, click "Browse" to open the "Library Browser". In the library browser, choose "tsmc13rf" as library, "nmos3v" (for n-type transistor) or "pmos3v" (for p-type transistor) as cell and "spectre" as view. The cell is placed in the schematic by moving the cursor to the desired location and clicking the left mouse button.
# To insert the voltage sources, pick the "vdc" cell from the "analogLib" library. Add one connected to vdd and gnd and one connected to the input.
# To insert the ground and vdd nets, pick the "vdd" and "gnd" cells from the "analogLib" library. Here the view name should be "symbol", not "spectreS" (in fact, "symbol" is the only available option).
# To connect the symbols, press 'w' or click the "Wire (narrow)" icon. Then use the left mouse button to click the nodes togeter, two by two.
# To remove an instance or a wire, left click at the instance or wire that you want to remove, then press the "Delete" button on the keyboard.
# To insert a pin, press 'p'. Choose a name for the pin in the dialog that occurs and click on the schematic to place it. Create one input and one output.
# To change the properties of the icons, press 'q' or click at the "Properties" icon. Then click at the instances or nets that you want to modify. For the vdc source connected between vdd and gnd, set the "DC voltage" property to 3.3.
# To check and save the schematic, press 'x' or click the "Check and save" icon.
# If there are any errors or warnings, press ok and press 'g' or "Check->Find Marker" to view the errors. Make sure you have no errors or warnings before continuing.
# Then open "Launch > ADE GXL" and press create new view. The "Virtuoso Analog Environment" should now come up.

==Simulating the design==

# Choose "Create > Test..." select the cell to simulate.
# Choose "Outputs > To be plotted > Select on Schematic". Click at the "in" node connected to the inverter input and the "out" node connected to the output.
# Choose "Analyses > Choose". We will now run a dc analysis to obtain the DC transfer characteristics of the inverter. Choose "Component parameter" as your sweep variable. Then click at "Select component". In the schematic, click at the input "vdc" instance. In the "Select Component Parameter" dialog box, choose dc as your sweep parameter. The sweep range should go from 0 to 3.3.
[[File:select_comp_parameter.png|300px]]
The analog environment should now look like this:
[[File:analog_env_2.png|500px]]
# Switch to the "adexl" tab and choose the green run button. When the run is completed press the graph button beside the box that says "Replace". The outputs should look like this:
[[File:plot_output_dc.png|600px]]

To save your simulation settings, choose "Session > Save state" in the test editor windoe to save your state information under whatever file name you want. In a later session, you can reload your saved states using "Session > Load state".

==Generating a Symbol==
Finally, we want to generate a symbol for our inverter. This symbol is needed if we want to use our inverter design inside another design (hierarchical design methodology).

Select the schematic tab and choose "Create -> Create Cellview -> From Cellview".

Press OK in the dialog that occurs.

The pins should already be connected to the right positions in the symbol generator, so press OK here also and ths symbol editor will occur.

Press the red X and delete the pre-created green square. Use the line tool and the circle tool to create the inverter symbol

[[File:symbol.png|400px]]

Save it by clicking the "Save and check" symbol or pressing 'shift+X'.

[[Category:Mikroelektronikk]] [[Category:Integrated_Circuts]]

Cadence Virtuoso setup

2017-09-15T13:31:42Z

Fli091: Added Category:Integrated_Circuts

= New single script install =
Edit the europractice_installer.sh and change INST_DIR=/eda to INST_DIR=/prog (ignore the warning of changing install paths){{-}}
Run "source europractice_installer.sh" and wait until done.{{-}}
Check in the /prog/cadence/20xx-xx/script folder if there is a IC, VIPCAT and ASSURA script in there, if not modify the release versions and add the following snippet in a file called cadence_missing.csh

<source lang="tcl">
setenv YEAR 2014-15
setenv $CDS_INST /prog/cadence/$YEAR/RHELx86
setenv CDS_VIPCAT $CDS_INST/VIPCAT_11.30.029_OVM
setenv PATH "${PATH}:${CDS_VIPCAT}/tools/bin"
if ( $?SPECMAN_PATH == 0) then
setenv SPECMAN_PATH "${CDS_VIPCAT}/utils:${CDS_VIPCAT}/packages"
else
setenv SPECMAN_PATH "${CDS_VIPCAT}/utils:${CDS_VIPCAT}/packages:${SPECMAN_PATH}"
endif
alias help_cds_vipcat '$CDS_VIPCAT/tools/bin/cdnshelp &'
#

setenv CDS_VIPCAT $CDS_INST/VIPCAT_11.30.029_UVM
setenv PATH "${PATH}:${CDS_VIPCAT}/tools/bin"
if ( $?SPECMAN_PATH == 0) then
setenv SPECMAN_PATH "${CDS_VIPCAT}/utils:${CDS_VIPCAT}/packages"
else
setenv SPECMAN_PATH "${CDS_VIPCAT}/utils:${CDS_VIPCAT}/packages:${SPECMAN_PATH}"
endif
alias help_cds_vipcat '$CDS_VIPCAT/tools/bin/cdnshelp &'
#

setenv CDS_ASSURA $CDS_INST/ASSURA_04.14.111_IC616OA
setenv ASSURAHOME $CDS_ASSURA
#the following line might be completely redundant
setenv SUBSTRATESTORMHOME $ASSURAHOME # For Assura-RF
setenv LANG C
setenv PATH "${PATH}:${CDS_ASSURA}/tools/bin"
setenv PATH "${PATH}:${CDS_ASSURA}/tools/assura/bin"
setenv PATH "${PATH}:${SUBSTRATESTORMHOME}/bin"
setenv ASSURA_AUTO_64BIT ALL
alias help_cds_assura '$CDS_ASSURA/tools/bin/cdnshelp &'
# assura

setenv CDS_IC $CDS_INST/IC_6.1.6.080
# This line is required by the some design kits...
setenv CDSDIR $CDS_IC
# When using ADE set netlisting mode to analog ("dfIIconfig.pdf"), p16.
setenv CDS_Netlisting_Mode Analog
setenv MG_ENABLE_PTOT true
# Required for tutorial material and cadence libraries (eg analogLib)
setenv CDSHOME $CDS_IC
setenv CDS_USE_PALETTE
setenv PATH "${PATH}:${CDS_IC}/tools/bin"
setenv PATH "${PATH}:${CDS_IC}/tools/dfII/bin"
alias help_cds_ic '$CDS_IC/tools/bin/cdnshelp &'
</source>

Run the following to generate the startup script

<source lang="tcl">
setenv YEAR 2014-15
# Fix path
sed -i 's/eda/prog/g' /prog/cadence/$YEAR/scripts/*.csh
# Fix non existent manpath
sed -i 's/setenv MANPATH/#setenv MANPATH/g' /prog/cadence/$YEAR/scripts/*.csh
chmod +x /prog/cadence/$YEAR/scripts/*.csh
# Add all scripts to one fil
ls /prog/cadence/$YEAR/scripts/*.csh > /prog/cadence/cadence_$YEAR\_init.csh
# Add source to each line
sed -i -e 's/^/source /' /prog/cadence/cadence_$YEAR\_init.csh
echo 'source /prog/cadence/eda_general_init.csh' >> /prog/cadence/cadence_$YEAR\_init.csh
chmod +x /prog/cadence/cadence_$YEAR\_init.csh
ln -s /prog/cadence/cadence_$YEAR\_init.csh /prog/cadence/cadence_init.csh
source /prog/cadence/cadence_init.csh
</source>

The content of eda_general_init.csh is
<source lang="tcl">
setenv CDS_LIC_FILE 5280@vlsi.ift.uib.no
setenv AMS_DIR /path/to/amslib
setenv TSMC_DIR /path/to/tsmc
setenv PATH "${PATH}:${AMS_DIR}/cds/bin"
setenv CDS_BIND_TMP_DD true
setenv IUSDIR $CDS_INCV
alias ams_cds_start 'setenv AMS;ams_cds -tech c35b4 -nologo'
alias tsmc_cds_start 'unsetenv AMS;virtuoso &'
</source>

Run checksys.sh script given at end of this page.

= Old install method=
== Update install manager ==
Always update install manager if a newer exists or else installations may fail.

cd /prog/cadence/
mkdir iscape
tar zxvf /prog/download/download.msc.rl.ac.uk/Cadence/2012_2013/ISCAPE/lnx86/iscape_VERSION

== Extract downloaded files ==

cd /prog/cadence/
mkdir download
cd download
find /prog/download/download.msc.rl.ac.uk/Cadence/ -name '*.tar' | xargs -l tar xvf

== Run install manager ==

/prog/cadence/iscape/iscape/bin/iscape.sh&

== configure install manager ==
preferences -> directories{{-}}
Set default install directory to{{-}}
/prog/cadence

== install/update program with install manager ==
For new installs, follow the install instructions provided by europractice in addition to the tips from this guide. Correct directory naming reduces the amount of editing of the settings file later.

* Press the icon which has the text "local directory/media install"
* Select browse and navigate to the directory containing the install files and select the CDROM1 folder. *Check that there isn't a slash at the end of the path. The program doesn't search recursively.
fex: /prog/cadence/unpacked/ASSURA04.12.020-5141_lnx86.Hotfix/CDROM1
*You don't need to install all updates recursively, select only the latest hotfix and the install will ask for the path to the base install when it is needed. If there are no hotfixes, install the base install.
*Select the correct path to install to, keep the existing naming convention.
*If a window opens with "Welcome to OpenAccess.....", just press enter and then 'n' and then enter again.
*If a window opens which asks about configuring the license server, press n.
*When the install is finished and you are back in the result list, you need to press the small underlined cancel text to change the path.
*To make make less changes to the environment script later run this command and use the provided paths in the installation. The CDS_INST path will be changed later.
cat /prog/download/download.msc.rl.ac.uk/Cadence/2013_2014/cadence_ic_2013.csh | grep CDS_INST

== Package specifics ==

=== INCISIVE ===
When doing a full install, INCISIVE needs to be installed first as it is required by IC.
Press cancel when the ARM license file dialog shows.

=== ASSURA ===
There are two versions ASSURA*-615 and ASSURA*-5141.
5141 is for compability with IC5 (CDB).
61 is for use with IC6 (OA).

=== VIPCAT ===
Choose UVM as the packet to install for IP verification

== Configuration ==
If a new install, then copy the template script called "cadence_ic_20xx.csh" from the download folder to the /prog/cadence folder.

Line references following will be based on the 2012 release of the file. Check that actual folder names are correct.

*24 - Set correct license server at line
*27 - Set CDS_INST to /prog/candence
*37 - Set ALTOS path to /ALTOS/altos_rel3.2p3
*57 - Set ASSURA path to /ASSURA_4.12_CDB if using IC5, /ASSURA_4.12_OA if using IC6
*72/74 - Comment/uncomment line according to IC version
*83 - Set to correct MVS folder (correct according to install instructions)
*110 - Set to correct IC6 folder (correct according to install instructions)
*151 - Set to correct ICC folder (correct according to install instructions)
*188 - Set PVE path to /PVE_11.12HF106
*213 - Set Conformal path to /CONFORMAL_11.10
*229 - Set to correct RCL folder (correct according to install instructions)
*243 - Set EDI path to /EDI_11.1
*258 - Set to correct ET folder (correct according to install instructions)
*274 - Set to correct ETS folder (correct according to install instructions)
*293 - Set MMSIM path to /MMSIM_11.10
*315 - Set INCISIVE path to /INCISIVE_12.1
*387 - Set VIPCAT path to /VIPCAT_11.3.014
*411 - Set CTOS path to /CTOS_12.1

If you correctly set the directories like specified above you can skip editing the paths to the specific programs and only change the one for CDS_INT.

Include these lines at the bottom
setenv AMS_DIR /path/to/amslib
setenv TSMC_DIR /path/to/tsmc
setenv PATH "${PATH}:${AMS_DIR}/cds/bin"
setenv CDS_BIND_TMP_DD true
setenv IUSDIR $CDS_INCV
alias ams_cds_start 'setenv AMS;ams_cds -tech c35b4 -nologo'
alias tsmc_cds_start 'unsetenv AMS;virtuoso &'

Save file as cadence_ic_20xx_uib.csh and add/update the symlink
csh
chmod +x /prog/cadence/cadence_ic_20xx_uib.csh
ln -s /prog/cadence/cadence_ic_20xx_uib.csh /prog/cadence/cadence_init.csh
source /prog/cadence/cadence_init.csh
Run lmstat to check that it is possible to connect to the license server
lmstat -c 5280@<your licenceserver>
Both cdslmd and altosda should be listed as up.

Run the checksys.sh script listed below to check for any missing dependencies and to set up any missing tools links.
In case the scipt gives an error like
<source lang=text>

Configuration checks failed, status is: FAIL

checkSysConf cannot reliably parse your systems /etc/redhat-release file
It would appear that the file is non-standard and does not contain release
information in the standard readable format.

The contents of your /etc/redhat-release is listed below between
<RELEASE_FILE> tags.
A 'correct' release file should have only one line of content, containing
version information in a standard format.

<RELEASE_FILE>
Red Hat Enterprise Linux Server release 5.9 (Tikanga)
</RELEASE_FILE>

Please check/correct your /etc/redhat-release file and try again.
There is no OEM datafile for -r for the Linux platform.

Valid OEM images are :
foreach: No match.
</source>
then the OS is probably newer than checkSysConf used, copy a newer version from another program folder.
If you then get
<source lang=text>
This operating system version '5.0WS' is not supported

If you believe you are running a supported OS then check that
the OS version directory exists in the data directory:
/<path to cadence>/ICC_11.2.41/share/patchData/Linux/x86_64
</source>
Then check the version in the aforementioned folder and the text file inside it.

Copy the .cdsinit script below to the folder /prog/cadence/IC_6.X.X.X/tools/dfII/local

== Scripts ==

===Checksys.sh===
Usefull for setting up missing tools folders and checking that all dependencies are installed
<source lang="bash">
#!/bin/bash
#
# Script for setting up tools folders and checking dependencies
# By Arild Velure 2014
#

if ( [ -z "$CDS_INST" ] && [ -z "$CDS_TOP" ] )
then
echo "Please run environment script first"
exit 1
fi

# Add new modules if needed
#2012
#cds_paths=( $CDS_ASSURA $CDS_MVS $CDS_IC $CDS_ICC $CDS_PVE $CDS_CONFORMAL $RC_PATH $CDS_SOCE
#$CDS_ET $CDS_ETS $CDS_MMSIM $incisiv_dir $CDS_VIPCAT $CTOS_ROOT )
#2013
cds_paths=( $ALTOSHOME $CDS_ASSURA $CDS_IC $CDS_ICC $CDS_PVE $CDS_CONFORMAL $CDS_RC $CDS_EDI $CDS_ET
$CDS_ETS $CDS_MMSIM $CDS_INCV $CDS_VIPCAT $CTOS_ROOT)
# CTOS_ROOT doesn't seem to have a checksysconf
#2014
cds_paths=( $CDS_ASSURA $CDS_CONFORMAL $CTOS_ROOT $CDS_EDI $CDS_ET $CDS_EXT $CDS_IC $CDS_INCV $ALTOSHOME $CDS_MMSIM $CDS_MVS $CDS_PVS $CDS_RC $CDS_SSV $CDS_VIPCAT )
# CDS_ASSURA CDS_IC and CDS_VIPCAT needs manual script

if [ -e ./problems.txt ]
then
rm ./problems.txt
fi

# Some installers forget to link the tools folder to the tools.lnx86
# Creat links so we don't need to edit and check settings file
for i in "${cds_paths[@]}"
do
if [ ! -e $i ]
then
echo "Can't find path $i is it installed?"
continue
fi
if [ ! -e $i/tools ]
then
if [ -e $i/tools.lnx86 ]
then
ln -s tools.lnx86 $i/tools
fi
fi
# Run checksys to check that system is properly installed
echo "Checking $i"
if [ ! -e $i/tools/bin/checkSysConf ]
then
echo "checkSysConf not found"
continue
fi
# You need to specifically mention the name of the release to test for.
# Next line parses the output and grabs all lines which starts with a space and contains
# some characters, which should only be release names, and puts them in an array
proglist=($($i/tools/bin/checkSysConf -r | egrep '^ +\w'))
# If it returns empty it propably didn't find a supported OS version
if [ ${#proglist[@]} = 0 ]
then
$i/tools/bin/checkSysConf -r >> problems.txt
echo "FAIL, couldn't find releasename"
fi
for a in "${proglist[@]}"
do
echo "Prog version $a"
result=$($i/tools/bin/checkSysConf $a -q)
echo "$result"
if [ "$result" = "FAIL" ]
then
#Something failed, run again with verbosity
$i/tools/bin/checkSysConf $a >> problems.txt
fi
done
done

if [ -e ./problems.txt ]
then
echo "Missing modules:"
cat ./problems.txt | grep FAIL
fi
</source>

===.cdsinit===
<source lang="autohotkey">
; AMS runs a script before starting virtuoso which creates a local .cdsinit in the current folder
; load the local .cdsinit if the program was started with the variable AMS set else load TSMC settings
if(getShellEnvVar("AMS") then
loadi("./.cdsinit")
else
;if( ddIsId( ddGetObj( "tsmc13rf" ) ) then
printf("********************************************\n")
printf(" Starting TSMC 130nm \n")
printf("********************************************\n")
ddCreateLib( "tsmc13rf" strcat(getShellEnvVar("TSMC_DIR") "/tsmc13rf"))
loadi(strcat(getShellEnvVar("TSMC_DIR") "/tsmc13rf/libInit.il"))
)
</source>

== Linux packages that might be required ==
*openmotif22
*libXp
*compat-readline43
*tk
*ksh
*sysstat

[[Category:Mikroelektronikk]] [[Category:Integrated_Circuts]]

Cadence Virtuoso overview

2017-09-15T13:31:28Z

Fli091: Added Category:Integrated_Circuts

=Analog IC design flow using Cadence from basics (Schematic capture, Netlist extraction, Simulating using ELDO, Layout, Signoff Layout)=

[[ TSMC 130nm process ]]

[[ IHP 130nm process ]]

[[ AMS 350nm process ]]

= Simulation =

[[Testbench|Virtuoso Testbench]]

= Layout =

[[Layout XL and IHP SG13S]]

=Helpful stuff=

[[ Transistor operating point printer ]] - Script to extract transistor operating point parameters after simulation.

[[ ADEXL-butterfly-curves ]] - Howto make DC butterfly curves easily.

[[Category:Mikroelektronikk]] [[Category:Integrated_Circuts]]

ADEXL-butterfly-curves

2017-09-15T13:31:14Z

Fli091: Added Category:Integrated_Circuts

To create a butterfly curve, for example for characterizing SRAM read and hold margins, simulate a single DC sweep (one source, one sweep) on a input.
Plot both the input (shows up as a straight line for a linear DC sweep) and the output (shows up as the DC response of your circuit).

Have both plots in the same subwindows.

go to Axis -> Y vs Y
choose the first trace, press ok.

go again to Axis -> Y vs Y
choose the second trace, press ok.

Put both results in the same plot, and you are finished.

[[Category:Mikroelektronikk]] [[Category:Integrated_Circuts]]