Preventing Instantiation of Cells from Restricted Library

Hi Kevin,

I tried your code, and it worked for me - but to be honest it seems to completely mess up the create instance form in schematic. I have to mess around changing the library, cancelling the form and trying a few more things to get it to work.

I'll contact the author of the article to see if they can investigate further.

Regards,

Andrew

Actually, it seems a bit better if I changed the dialog form to have the argument as form rather than cdfgForm, and also changed to be called before it blanked out the library name and cell name fields:

;;Prevent usage of ohc15l_digital library
procedure(CCSFormProc1(cdfDataId)
  ;printf("hello")
  when(cdfDataId

    if((cdfgForm->hiFormSym == 'schCreateInstForm) && (schCreateInstForm->libraryName->value=="ohc15l_digital")
      then
        warn("\nCannot instantiate the selected cell in this projects' designs\n")
        CCSCustomMsg(cdfgForm)
        schCreateInstForm->libraryName->value=""
        schCreateInstForm->cellName->value=""

    ) ;if schCreateInstForm

    if(or((cdfgForm->hiFormSym == 'leCreateInstForm) (cdfgForm->hiFormSym == 'leCreateInstLForm) (cdfgForm->hiFormSym == 'leCreateInstXLForm)) && (leCreateInstForm->libName->value=="ohc15l_digital")
      then
        warn("\nCannot instantiate the selected cell in this projects' designs\n")
        CCSCustomMsg(cdfgForm)
        leCreateInstForm~>libName~>value = ""
        leCreateInstForm~>cellName~>value = ""

    ) ;if leCreateInstForm

  ) ;when
) ;procedure CCSFormProc1

procedure(CCSCustomMsg(form)
  hiDisplayAppDBox(?name 'messg
    ?dboxBanner "Attempted Use of Restricted Library"
    ?dboxText
    ;; You can change the message here in sprintf call
    sprintf(nil "Cells from Library %L are NOT ALLOWED in analog schematics, use Library %L."
    form~>libraryName~>value "ohc15l_digital_ana_lv") ;sprintf
    ?dialogStyle 'modal
  ) ;hiDisplayAppDBox
) ;procedure CCSCustomMsg

Thanks for looking into it. I'll try to circle back on it sometime this afternoon but I need to get back to design tasks. I was curious if there is a way to see how old the referenced procedure is? I thought there may have been some compatibility issue with newer versions of the tool as I was fairly sure I wasn't doing anything too weird with the slight modifications I made to the example.

I'm using version IC6.1.8-64b.500.9

The article was originally written in 2016, but I can't see how it's evolved in the meantime. It was last updated in March 2020, but I don't think anything in there is particularly sensitive to the version used (my tests were in the latest .21 subversion of IC6.1.8, but I would be very surprised if the behaviour was different in ISR9). Note that it does seem slightly flaky anyway, which is why I asked the article author to take a look (he was on vacation last week).

Andrew

Hi Andrew. Did your colleague have a chance to look at this?

Hi Kevin,

I didn't hear back from him (he was probably busy at the time) - I've just prompted him again.

Kind Regards,

Andrew

Hi Andrew,

Did you ever receive a reply from your colleague? Thanks.

-Kevin

Kevin,

Yes. It turned out that a number of changes in the article had been made by somebody else, not the original author - so he referred this back to the knowledge team for them to address.

The best thing to do here is to contact customer support, then your underlying request can be properly worked on as a support case.

Regards,

Andrew

I sent a support request, thanks for looking into it.

I sent a support request, thanks for looking into it.