• 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. empty file while when exporting netlist cdl

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 143
  • Views 9537
  • 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

empty file while when exporting netlist cdl

saurabh96
saurabh96 over 4 years ago

Hello guys,.. i have few doubts..mentioned below...

for above gui,

Now when user selects cell view then it should export the  cdl netlist for the cell select from libraray manager-       ;;;;;;;;;;;;;;;;;;cell view is lib name and topcell is cell name

procedure(CCSRunNetlisterCell(cell_check cell_top viewName runDir simulatorName)
let( ( op runDirPath singleFile mvFile )

cell_check = form->cell_view_Entry->value
cell_top = form->Topcell->value

runDirPath=strcat(runDir "/" cell_top)
simInitEnvWithArgs(runDirPath cell_check cell_top viewName simulatorName nil)

op=outfile(strcat(runDirPath "/si.env") "a")
fprintf(op "incFILE=\"\" \n")
fprintf(op "setEQUIV=\"\" \n")
close(op)

netlist()

mvFile=sprintf(nil "mv -f ./%s/netlist ./%s/%s.cdl" runDirPath runDirPath cell_top)
singleFile=sprintf(nil "cat ./%s/%s.cdl >> ./%s/netlist.cdl" runDirPath cell_top runDir)
system(mvFile)
system(singleFile)
printf("Netlisting the cell:%L from Library:%L in the path:%L\n" cell_top cell_check runDirPath)

) ; let
) ;procedure
cell_check = form->cell_view_Entry->value
cell_top = form->Topcell->value
CCSRunNetlisterCell("%s" "%s" "schematic" "CDL" "auCdl" cell_check cell_top)

netlist = simplifyFilename(strcat(runDirPath "/" celltop ".cdl")

 

for above am getting error as max argument can be called 5 ...............in this how can i call arguments as it may keep changing as per user

  • Cancel

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