ViVa waveform tool

So this is the same issue as you reported in this thread.

I suspect this might be because you may have a display.drf with the packets associated with layers y0-y9 drawing set to white. ADE uses these layer-purpose-pairs so that it can highlight the nets on the schematic the same colour as the trace is drawn with when probing the schematic. Other plots (e.g. originated from the calculator) don't need to have corresponding colours, so they'll use ViVA's built-in colours instead. Alternatively, you may be accessing a library over time which loads its own display.drf which is corrected?

I suggest you try using Tools->Display Resource Manager, click the Edit button, and then pick All (rather than LSW) in the Layers box in the Display Resource Manager. Hunt for y0 drawing etc and see what they are set to.

If that looks OK, please contact customer support because it's something else which will need more detailed investigation. If they are all white, you'll need to hunt down if you have a display.drf setting these colours somewhere.

Regards,

Andrew.

 Yes it is the same problem I mentioned in that post.

Thank you your solution by selecting All(instead of LSW) and assigning colours to the y0 drawings etc has worked. Now the only issue is that after restarting Virtuoso the LSW is selected (instead of All) which is why the traces turn back to white again. How to stop this from reseting although I have saved the display.drf file many times.

Regards

Sohaib 

Sohaib,

Commonly PDKs load their own display.drf by having a call to drLoadDrf(...)  in the technology library's libInit.il file. You should check to see if that is the case, because if it is, any display.drf you have in your working dir (say) will get loaded at startup, but then overridden by an explicit drLoadDrf() call later when the technology library is first accessed.

You can use this code in your .cdsinit to get around this:

procedure(CCSloadDisplayDrf(libId)
   let((libName fileName)
     libName=libId~>name
       when(libName=="gpdk090"
         ; change the path to be correct in the following statement
         drLoadDrf("./display.drf" nil)
     )
   )
)

ddRegTrigger("FirstAccessLib" 'CCSloadDisplayDrf)

Note that you may want to change the library name from gpdk090 to whatever your technology library is. The above code will work fine in IC615 - for IC5141 there's a slightly different code needed to workaround an issue with one of the existing triggers.

The idea is that this will kick in after the libInit.il has been loaded, and so give you the chance to override again with your own display.drf file.

Regards,

Andrew.