Hello, Cadence community,
A short question: has anyone tried to simulate extracted views and change them from the ocean environment?
I have, but didn't succeed (I'm not new to OCEAN or SKILL, so if anyone has any solutions, the level of complexity doesn't matter)... If I understand correctly, one can do this in several ways:
1) create a config file and bind the schematic to the extracted view;
2) bind the extracted view directrly from ADE using setup->environment options-> first two textboxes from the top...
I've tried to implement this in ocean and declare these lines in my script:
envOption('switchViewList '( "spectre" "cmos_sch" "cmos.sch" "schematicExtract" "veriloga" "ahdl"))
The schematicExtract is my extracted schematic :)
The lines above do not change the extracts, OCEAN still uses the simple schematic (not extract) during simulations...
I understand, that the hierarchy should be created (updated) for the software to bind extracts with schematics, but is there any way of doing that in OCEAN? May be OCEAN scripts are not capable of changing between extracted views?
By the by, the scripts DO calculate extracts when I first configure the config file (or through ADE) and then load the script. But as I mentioned earlyer - the calculations are conducted with only the present extract and if I try to change it to another one (now using the OCEAN lines and not from ADE or config file), nothing happens...
By the way, I do not generate the netlist after setting envOption in the script - maybe that's the case? (though I doubt it)
This should work fine - but I suspect it's related to how you've specified the design via the design() function in your OCEAN script.
Note that you don't have to renetlist for this to work - the run() function does a netlist and run (and does an incremental re-netlist as needed).
In reply to Andrew Beckett:
Thanks for the fast reply.
I've declared my design through design("/path/to/netlist") and as You said, it doesn't work.
After declaring the schematic with:
design("libName" "cellName" "schematic")
the lines with envOption now seem to work properly.
In reply to Alex Vasjanov:
Another question arose: say I have a schematic with only a block that has an extracted view and I need to change it's extracts within OCEAN. I assume that the envOption way isn't suitable for this. (didn't work for me) I can solve this with creating different config files every single of which binds the desired extract to that particular block and then change them (the configs) in the script.
Maybe there's another way, a smarter one?