• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. Error encountered during pcell instantiation??

Stats

  • Locked Locked
  • Replies 24
  • Subscribers 143
  • Views 21294
  • 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

Error encountered during pcell instantiation??

Messi
Messi over 14 years ago
 Hai,

     

    This is the code i have written to read a file and then instantiate a pcell inside an already created pcell:

procedure(mypcell(ruleFile pcellInfo)

  let( (ruleFileTable purposeList mastercv inst )

  ruleFileTable  =  readFile( ruleFile )

;readFile is the function name for another procedure I created to read an file and drop its contents into a table

           foreach(line FileTable

           purposeList = caddr(line)

    ;the table has mainly four elements and I want the third element based on which instantiation has to be carried out

          unless(rexMatchp(pcellinfo purposeList)

           case(pcellinfo

             ("a"

         ;;To Create PCell for “a”

                    mastercv   = dbOpenCellViewByType("test" "pcell" "layout" "" "w")

                  ;mastercv is an already created pcell

                    inst           = dbCreateParamInst(

                                         "pcell" mastercv "a" list(0 0) "R0" 1

                                           list(

                                               list( "w"  "float" 0.5)

                                                )

                                                );dbCreateParamInst

                                         dbClose(mastercv)

                                      ); for case “a”

           ("b"

;;To Create PCell for "b"                   

                     mastercv   = dbOpenCellViewByType("test" "pcell" "layout" "" "w")

                     inst           =  dbCreateParamInst(

                                        "pcell" mastercv "b" list(0 0) "R0" 2

                                           list(

                                                list( "w"  "float" 0.5)

                                                list( "s"  "float" 0.25)

                                                )

                                            );dbCreateParamInst

                                          dbClose(mastercv)

                                          );case

                                   );for case  "b"               

                           );unless

        );foreach

    );let

);procedure

But i am generating errors while i run this code :

Can anyone look into and this find the error in it.....

Thanks,

  Messi
  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 14 years ago
    Hi Messi,

    The problem is that you've parsed each line in your rule file to be a list of strings, and so you're passing a string where a float is expected.

    Use the function cdfParseFloatString or atof to convert it to a float when calling dbCreateParamInst. cdfParseFloatString has the benefit of handling suffixes like "k" and "u". So:

         dbCreateParamInst(
           cv mastercv i list(0 0) "R0" 2
         list( list(  "w1"     "float"                     cdfParseFloatString(nth(2 ruleTable[i])))))

    Note your code still has the unnecessary ruleTable~>? in the foreach loop.

    Another thing you might want to consider to make the code more readable is that rather than using rexMatchp, you could do:

           case(upperCase(nth(1 ruleTable[i]))
             ("WIDTH"       
                dbCreateParamInst(
           cv mastercv i list(0 0) "R0" 1
                   list(
                      list( "w1"      "float"  cdfParseFloatString(nth(2 ruleTable[i])))
                      list( "layer1"  "string" nth(0 ruleTable[i]))
                      list( "type"    "string" nth(1 ruleTable[i]))
                  ))
       )

      ("SPACE"  
       dbCreateParamInst(
           cv mastercv i list(0 0) "R0" 2
    ...

    In fact better still would be to do:

    ruleData=ruleTable[i]

    At the beginning (within) the foreach loop, so you don't have to keep looking up the entry in the hash.

    Regards,

    Andrew
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 14 years ago
    Hi Messi,

    The problem is that you've parsed each line in your rule file to be a list of strings, and so you're passing a string where a float is expected.

    Use the function cdfParseFloatString or atof to convert it to a float when calling dbCreateParamInst. cdfParseFloatString has the benefit of handling suffixes like "k" and "u". So:

         dbCreateParamInst(
           cv mastercv i list(0 0) "R0" 2
         list( list(  "w1"     "float"                     cdfParseFloatString(nth(2 ruleTable[i])))))

    Note your code still has the unnecessary ruleTable~>? in the foreach loop.

    Another thing you might want to consider to make the code more readable is that rather than using rexMatchp, you could do:

           case(upperCase(nth(1 ruleTable[i]))
             ("WIDTH"       
                dbCreateParamInst(
           cv mastercv i list(0 0) "R0" 1
                   list(
                      list( "w1"      "float"  cdfParseFloatString(nth(2 ruleTable[i])))
                      list( "layer1"  "string" nth(0 ruleTable[i]))
                      list( "type"    "string" nth(1 ruleTable[i]))
                  ))
       )

      ("SPACE"  
       dbCreateParamInst(
           cv mastercv i list(0 0) "R0" 2
    ...

    In fact better still would be to do:

    ruleData=ruleTable[i]

    At the beginning (within) the foreach loop, so you don't have to keep looking up the entry in the hash.

    Regards,

    Andrew
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information