Stats

  • Locked Locked
  • Replies 5
  • Subscribers 143
  • Views 22786
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to fix the CDF termOrder mismatch

twen

When I add, delete, or rename a pin in the schematic or the symbol view, the netlister will complaint about this:

WARNING (ADE-6004): Mismatch was found between the terminals in the cellView and those on the
           termOrder property on the CDF. Because of the mismatch, the CDF termOrder will
           be ignored. The terminals in the cellView will be netlisted in the alphabetical
           order of their names. Eliminate the mismatch if you want the CDF termOrder
           property to be used for netlisting.

This is produced from IC6.1.6-64b.500-12.

Here is the SKILL code that I created to fix the termOrder mismatch problem:

/* twen
 * 2016-02-09
 * Eg: twFixTermOrder("mylib")
 *     twFixTermOrder("mylib" "mycell")
 */
procedure(twFixTermOrder(lib @optional (cell nil))
    let((oldAutoCtl libId cellId cellIds)
        ;; Save the prompting and automatic check-in and check-out controls
        oldAutoCtl = ddAutoCtlGetVars()
        ;; Do not prompt the user to check-in or check-out
        ddAutoCtlSetVars(0 0 3 3)
        
        when(libId=ddGetObj(lib)
            ;; If no cell name is specified, then fix all cells in the lib
            if(cell cellIds=list(ddGetObj(lib cell)) cellIds=libId->cells)
            foreach(cellId cellIds
                when(ddGetObj(lib cellId->name "schematic")
                    printf("Updating the CDF termOrder for %s/%s \n" lib cellId->name)
                    artGenerateHierSymbolCDF(dbOpenCellViewByType(lib cellId->name "schematic") t)
                )
            )
        )
        ;; Restore the prompting and automatic check-in and check-out controls
        apply(`ddAutoCtlSetVars oldAutoCtl)
    )
)

I'd like to add a feature to fix the termOrder for cells within a particular category. Any comments are welcomed!

TJ

Parents

  • TJ,

    The fact that the same env var appears twice is just a typo on the doc - one says "boolen" rather than "boolean" for some reason.

    However, I don't know why you used "asimenv.netlist" as the tool.partition. I didn't say that in my earlier post - I said "auCore.misc" which is what it says in the documentation. Prior to IC5141 (e.g. in IC5033) it used to be in asimenv.misc (not asimenv.netlist), but certainly since IC5141 base release in 2004 it has been in auCore.misc - which is what the documentation and my earlier post says.

    Also, the third argument should be 'boolean not 'bool (also look at what I wrote earlier).

    I am not aware of any existing built-in function that determines whether the termOrder in the CDF is consistent with the current terminals. There is the function (which is private) which detects whether the current CDF is different from the cellView in the current window - but it's both private and also requires a window to be open. So probably not the best choice. Easy enough to write your own though which gets the termOrder from each of the simInfo in the CDF and compares with the terminals in the specified cellView.

    Regards,

    Andrew.

Reply

  • TJ,

    The fact that the same env var appears twice is just a typo on the doc - one says "boolen" rather than "boolean" for some reason.

    However, I don't know why you used "asimenv.netlist" as the tool.partition. I didn't say that in my earlier post - I said "auCore.misc" which is what it says in the documentation. Prior to IC5141 (e.g. in IC5033) it used to be in asimenv.misc (not asimenv.netlist), but certainly since IC5141 base release in 2004 it has been in auCore.misc - which is what the documentation and my earlier post says.

    Also, the third argument should be 'boolean not 'bool (also look at what I wrote earlier).

    I am not aware of any existing built-in function that determines whether the termOrder in the CDF is consistent with the current terminals. There is the function (which is private) which detects whether the current CDF is different from the cellView in the current window - but it's both private and also requires a window to be open. So probably not the best choice. Easy enough to write your own though which gets the termOrder from each of the simInfo in the CDF and compares with the terminals in the specified cellView.

    Regards,

    Andrew.

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.