luke
/
OpenRAM
mirror of https://github.com/VLSIDA/OpenRAM.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update Magic support in README.

This commit is contained in:
Matt Guthaus 2018-02-06 11:14:43 -08:00
parent 547746f839
commit 79e3f012a8
1 changed files with 21 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
README.md
View File

@ -123,15 +123,20 @@ passes, the files are deleted. If it fails, you will see these files:
* _calibreDRC.rul_ is the DRC rule file. * _calibreDRC.rul_ is the DRC rule file.
* dc_runset is the command file for caliber. * dc_runset is the command file for caliber.
* temp.gds is the layout * temp.gds is the layout
* test1.drc.err is the std err output of the command * (.mag files if using SCMOS)
* test1.drc.out is the standard output of the command * temp.sp is the netlist
* test1.drc.db is the DRC results file * test1.drc.err is the std err output of the DRC command
* test1.drc.out is the standard output of the DRC command
* test1.drc.results is the DRC results file
* test1.lvs.err is the std err output of the LVS command
* test1.lvs.out is the standard output of the LVS command
* test1.lvs.results is the DRC results file
If DRC/LVS fails, the first thing is to check if it ran in the .out and If DRC/LVS fails, the first thing is to check if it ran in the .out and
.err file. This shows the standard output and error output from .err file. This shows the standard output and error output from
running DRC/LVS. If there is a setup problem it will be shown here. running DRC/LVS. If there is a setup problem it will be shown here.
If DRC/LVS runs, but doesn't pass, you then should look at the .db If DRC/LVS runs, but doesn't pass, you then should look at the .results
file. If the DRC fails, it will typically show you the command that was used file. If the DRC fails, it will typically show you the command that was used
to run caliber. It is something like this: to run caliber. It is something like this:
``` ```
@ -139,8 +144,9 @@ to run caliber. It is something like this:
/tmp/openram_mrg_28781_temp/test1.drc.err 1> /tmp/openram_mrg_28781_temp/test1.drc.err 1>
/tmp/openram_mrg_28781_temp/test1.drc.out /tmp/openram_mrg_28781_temp/test1.drc.out
``` ```
To debug, you will need a layout viewer. I prefer to use glade on my Or, if you are using Magic+Netgen, there will be a shell script run_drc.sh
Mac, but you can also use Calibre, Magic, etc. and run_lvs.sh. To debug, you will need a layout viewer. I prefer to use glade
on my Mac, but you can also use Calibre, Magic, etc.
1. Calibre 1. Calibre
@ -187,9 +193,16 @@ ui().importCds("default",
To load the errors, you simply do Verify->Import Caliber Errors select To load the errors, you simply do Verify->Import Caliber Errors select
the .db file from calibre. the .db file from calibre.
3. It is possible to use other viewers as well, such as: 3. Magic
Magic is only supported in SCMOS. You will need to install the MOSIS SCMOS rules
as well from: http://opencircuitdesign.com/magic/
When running DRC or extraction, OpenRAM will load the GDS file, save
the .mag files, and export an extracted netlist.
4. It is possible to use other viewers as well, such as:
* LayoutEditor http://www.layouteditor.net/ * LayoutEditor http://www.layouteditor.net/
* Magic http://opencircuitdesign.com/magic/
# Example to output/input .gds layout files from/to Cadence # Example to output/input .gds layout files from/to Cadence