Stats

  • Locked Locked
  • Replies 5
  • Subscribers 143
  • Views 14407
  • 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

CIW error messages for SKill script

Inas Mohammed

Hello,

I have a sample skill script, on running it gives an error message in the CIW.

Here is the Code:

procedure(place_devices(cellView devLib devCell Length nfunit wfunit DUM1nf DUM1wf DUM2nf DUM2wf yPitch Pattern)
let((params array nRows nCols Type dev name nf wf inst devCounts x y xPitch (x0 0.0) (y0 0.0))

devCounts=makeTable('DEVCOUNT 0)
array = listToVector(foreach(mapcar row reverse(pattern) listToVector(parseString(row " "))))
nRows=length(pattern)
y=y0
for(row 0 nRows-1
x=x0
nCols=length(array[row])
for(col 0 nCols-1
dev=array[row][col]
devCounts[dev]++
name=sprintf(nil "%s.%d" dev devCounts[dev])
Type=cond(
(eq('M getchar(array[row][col] 1)) 'device)
(zerop(row) && (zerop(col) || col==nCol-1) 'corner)
(zerop(col) && (zerop(row) || row==nRows-1) 'corner)
(zerop(row) || row==nRows-1 'topBottom)
(zerop(col) || col==nCols-1 'leftRight)
(t 'dummy)
)
caseq(Type
((device dummy)
nf=nfunit
wf=wfunit
)

(corner
nf=DUM1nf
wf=DUM2wf
)

(topBottom
nf=DUM2nf
wf=DUM2wf
)

(leftRight
nf=DUM1nf
wf=DUM1wf
)

(t error("type=%l\n" Type)
)
)

params = list(
list("l" "string" aelSuffixNotation(1u * Length))
list("wf" "string" aelSuffixNotation(1u * wf))
list("fingers" "string" sprintf(nil "%d" nf))
list("routePolydir" "string" "Top")
) ; params

when(zerop(col)
; Device is on left edge. Add detached bodytie.
params = xcons(params
list("bodytie_type" "string" "Detached"))
)

when(col==nCols-1
; Device is on right edge. Add detached bodytie.
params = xcons(params
list("bodytie_typeR" "string" "Detached"))
)

inst=dbCreateParamInstByMasterName(cellView devLib devCell "layout" list(x y) "R0" params)
xPitch = nf * (Length + 0.1) + 0.12

;; TODO: Replace numbers with space/extension params
;; Or, use rodGetObj and/or M1 geometry of the
;; inst->master cellView to calculate the xPitch
;; of the instantiated device

;; Calculate x coordinate for next device
x = x + xPitch

)
)

)) ; let ; procedure

place_devices(
geGetEditCellView() ; cellView
"tsmcN65" ; devLib
"pch" ; devCell
0.2 ; Length (um)
2 ; nfunit
6.0 ; wfunit (um)
2 ; DUM1nf
6.0 ; DUM1wf (um)
2 ; DUM2nf
2.0 ; DUM2wf (um)
1.0 ; yPitch (um)
list(
"Du Du Du Du Du"
"Du M1 M2 M1 Du"
"Du M2 M1 M2 Du"
"Du Du Du Du Du"
) ; pattern (rows)
)

here is the message in the CIW for the highlighted line above:

*Error* dbCreateParamInstByMasterName: argument #6 should be a list (type template = "dggggltxlg") at line 67

Can you please tell me what is the issue with that? how can i define the orientation in a list?

Regards

  • OK, the answer here is to read the manual. Given the error message, I would have thought that would have been an obvious first step, rather than posting in a forum!

    Your line of code:

    inst=dbCreateParamInstByMasterName(cellView devLib devCell "layout" list(x y) "R0" params)

    The documentation for this function (the first part, at least):

    dbCreateParamInstByMasterName(
    d_cellView
    t_libName
    t_cellName
    t_viewName
    t_name
    l_origin
    l_orient
    [ x_numInst
    [ l_params
    [ g_physOnly ] ] ]
    )
    => d_inst / nil

    You have omitted the instance name (t_name). That should be the fifth argument. You also need to specify x_numInst before the list of parameters (if providing the parameters). Specify this as 1.

    Andrew.

  • Hi Andrew,

    Is this is the technique to get unique instance name? (by specifying 1). I had struggled a lot in the past to get unique instance name.

    Later on found a way to do. (just length of total number of instance + 1)

    Thanks

    Ramakrishnan

  • I guess I had misread your reply. Never mind.

    -Ramakrishnan

  • If you'd read the documentation, you'd see that you can specify the instance name argument as nil and then it will automatically come up with a unique instance name.

    Andrew

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.