R
Riad KACED
Guest
Hi Dinac,
You are on the right track.
The best for you is read the following documentation:
"VerilogŽ In for Design Framework II User Guide and Reference". This
document is available in your cadence stream:
$CDSHOME/doc/verinuser/verinuser.pdf
I would like to highlight some points that might be useful for you.
1. References Libraries
put in the list (space separated) of all the digital core libraries of
all the primitives used in your veriliog code. There will be cells
missing otherwise.
2. Import structural modules as:
I wold advice to set it at "schematic & functional" to make a
schematic view for LVS and a functional view for simulation.
3. Power/Ground Net name:
If your verilog code contains nets named VDD/GND then verilogIn will
import them as global nets VDD!/GND!. If you wish to avoid this
behaviour then put arbitrary names in these fields.
That said, the most accurate and up to date information about
verilogIn id available in the document mentioned above.
Cheers,
Riad.
You are on the right track.
The best for you is read the following documentation:
"VerilogŽ In for Design Framework II User Guide and Reference". This
document is available in your cadence stream:
$CDSHOME/doc/verinuser/verinuser.pdf
I would like to highlight some points that might be useful for you.
1. References Libraries
put in the list (space separated) of all the digital core libraries of
all the primitives used in your veriliog code. There will be cells
missing otherwise.
2. Import structural modules as:
I wold advice to set it at "schematic & functional" to make a
schematic view for LVS and a functional view for simulation.
3. Power/Ground Net name:
If your verilog code contains nets named VDD/GND then verilogIn will
import them as global nets VDD!/GND!. If you wish to avoid this
behaviour then put arbitrary names in these fields.
That said, the most accurate and up to date information about
verilogIn id available in the document mentioned above.
Cheers,
Riad.