Stats

  • Locked Locked
  • Replies 3
  • Subscribers 143
  • Views 14047
  • 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

creating list of celviews

sanramz

Hi,

   I am trying to create multiple new layouts from a list unix file in to one library. In each cell Iam also trying to create a PR boundary with the coordinates that are present in the unix file.

 

The list file contains the cell name and PR boundary coordinates as shown below. 

cell_name                       llx    lly    urx       ury

BUF                                0     0     4.448    4.424

AND                                0     0     4.448    4.424 

 My code for this is as shown below.

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; 

ListPath = "/home/san/tiler/cell_list"

;lib_name="test"

inPort = infile( ListPath )

when( inPort

while( gets( line inPort )

;println( nextLine )

 

lineData = parseString(line " ")

        ;portTable[car(lineData)] = evalstring(cadr(lineData))

;cell_name=car(lineData)

cell_name=nth(0 lineData)

llx=nth(1 lineData)

lly=nth(2 lineData)

urx=nth(3 lineData)

ury=nth(4 lineData)

create_boundary(cell_name llx lly urx ury)

)

close( inPort )

)

procedure(create_boundary(cell_name llx lly urx ury)

let (cv)

cv=dbOpenCellViewByType("test" "cell_name" "layout" "maskLayout" "w")

dbCreateRect(cv list("prBoundary" "drawing") list(llx:lly urx:ury))

dbSave(cv)

);procedure

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
 
For this code, I am getting the following error.
 
*Error* eval: undefined function - create_boundary
*Error* load: error while loading file - "create_cell.il" at line 20 

  Kindly help me to solve this.

Is it because of the "parsing", as i expect \n is coming for the "urx" variable when I try to access it??

 Regards,

santhosh. 

Parents
  • Two problems (at least, may be more because I didn't try the code)

    1. The function create_boundary is not defined until after it's called, which is why you have the problem you're seeing. If the main bit of the code had been contained within a function definition, that would have been OK, because loading the file would have defined the functions rather than executing them. In other words, if you'd put procedure(createBoundaryFromFile(ListPath)... around your main code, the forward reference would have been fine because you would not have been calling create_boundary before it had been defined. Then after loading the code, you'd do createBoundaryFromFile("/path/to/the/file")
    2. The coordinates will all be strings, so you should do atof(nth(1 lineData)) etc.

    Note too that if this is for IC61, you'd have to use dbCreatePRBoundary rather than creating a shape on the PRBoundary/drawing LPP.

    Regards,

    Andrew
Reply
  • Two problems (at least, may be more because I didn't try the code)

    1. The function create_boundary is not defined until after it's called, which is why you have the problem you're seeing. If the main bit of the code had been contained within a function definition, that would have been OK, because loading the file would have defined the functions rather than executing them. In other words, if you'd put procedure(createBoundaryFromFile(ListPath)... around your main code, the forward reference would have been fine because you would not have been calling create_boundary before it had been defined. Then after loading the code, you'd do createBoundaryFromFile("/path/to/the/file")
    2. The coordinates will all be strings, so you should do atof(nth(1 lineData)) etc.

    Note too that if this is for IC61, you'd have to use dbCreatePRBoundary rather than creating a shape on the PRBoundary/drawing LPP.

    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.