Stats

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

Generate Netlist from the Command Line

MenghanSun

Dear all,

I'm trying generate netlist from command line:

I used the following commands in CIW window:

simulator( 'spectre )

design( "libname" "cellname" "viewname")

createNetlist( ?recreateAll t)

It does generate the netlist, it didn't generate it in the directory I want:

it generates the netlist in the following directory:

/home/elecpg/menghansun/simulation/diffRecSim/spectre/schematic/netlist/netlist


I wish to generate the netlist in:

/d2/data/GFBCD013/013BCDlite/CDS/DL-000024/Rev14/OA/1P6M_9kA_1k_1p0f_SM/simulation/diffRecSim/spectre/schematic/netlist/netlist

/home/elecpg/menghansun is the home directory on the system, it seems to me that cadence wants to do all the things in this home drectory, for example, it always creates its CDS.log in its home directory.

Is there a way to generate netlist into the directory that we specify?

And, does the way I do this seem to be a reasonable way?

Thanks,

Menghan Sun

Parents

  • Hi Andrew,


    Thanks for the reply, that did the trick.

    I have follow-on question. When I generate the netlist using the above method, in the netlist directory, there are two files. One is  "input.scs", the other is "netlist". Then, I use ADE to generate an ocean script and then run the simulation from ocean script. I found that there are overlaps between "input.scs" and my ocean script, regarding the model files & simulation options & results/data output, saving, etc. After I run the simulation using ocean, the overlap part of input.scs is modified to be in agreement with the ocean script, especially the model files part. Is this expected?

    After the ocean simulation is finished, I had a look at the spectre.out file in psf directory. It says:

    """"""""""""""""""""""""""""""""""""""""""""""

    Spectre received SIGTERM.

    Error found by spectre.
        ERROR (SPECTRE-25): Killed by user.
    """""""""""""""""""""""""""""""""""""""""""""""

    It seems that the ocean script has killed spectre prematurely. Since I got all the results I wanted and simulation runs smoothly and I didn't try to kill spectre in my ocean script, I'm wondering if ocean is internally implemented this way?

    Below is part of my ocean script.

    """""""""""""""""""""""""""""""""""""""""""""""""

    analysis('tran ?stop "30u"  ?errpreset "conservative"  )
    desVar(   "vinamp" 1    )
    envOption(
            'analysisOrder  list("tran")
    )
    saveOption( ?simOutputFormat "psf" )
    saveOption( 'pwr "total" )
    saveOption( 'save "selected" )
    save( 'v "/vdc" "/rfinp" "/rfinn" )
    save( 'i "/I7/rfinp" "/I7/rfinn" "/R0/PLUS")
    temp( 27 )
    run()

    outVol = VT("/vdc")
    plot(outVol ?expr '("outVol") )
    hardCopyOptions(?hcOutputFile "vdc_out.png")
    hardCopy()

    plusInVol = VT("/rfinp")
    plot(plusInVol ?expr '("plusInVol") )
    hardCopyOptions(?hcOutputFile "rfinp_out.png")
    hardCopy()

    minusInVol = VT("/rfinn")
    plot(minusInVol ?expr '("minusInVol") )
    hardCopyOptions(?hcOutputFile "rfinn_out.png")
    hardCopy()

    powP = (integ(VT("/rfinp") 2e-05 3e-05) / 1e-05)

    summaryFile = outfile("summary.txt")
    fprintf(summaryFile "Input %s C is %.3e \n" temp() powP)


    close(summaryFile)
    """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""


    Thank you.

    Menghan Sun

Reply

  • Hi Andrew,


    Thanks for the reply, that did the trick.

    I have follow-on question. When I generate the netlist using the above method, in the netlist directory, there are two files. One is  "input.scs", the other is "netlist". Then, I use ADE to generate an ocean script and then run the simulation from ocean script. I found that there are overlaps between "input.scs" and my ocean script, regarding the model files & simulation options & results/data output, saving, etc. After I run the simulation using ocean, the overlap part of input.scs is modified to be in agreement with the ocean script, especially the model files part. Is this expected?

    After the ocean simulation is finished, I had a look at the spectre.out file in psf directory. It says:

    """"""""""""""""""""""""""""""""""""""""""""""

    Spectre received SIGTERM.

    Error found by spectre.
        ERROR (SPECTRE-25): Killed by user.
    """""""""""""""""""""""""""""""""""""""""""""""

    It seems that the ocean script has killed spectre prematurely. Since I got all the results I wanted and simulation runs smoothly and I didn't try to kill spectre in my ocean script, I'm wondering if ocean is internally implemented this way?

    Below is part of my ocean script.

    """""""""""""""""""""""""""""""""""""""""""""""""

    analysis('tran ?stop "30u"  ?errpreset "conservative"  )
    desVar(   "vinamp" 1    )
    envOption(
            'analysisOrder  list("tran")
    )
    saveOption( ?simOutputFormat "psf" )
    saveOption( 'pwr "total" )
    saveOption( 'save "selected" )
    save( 'v "/vdc" "/rfinp" "/rfinn" )
    save( 'i "/I7/rfinp" "/I7/rfinn" "/R0/PLUS")
    temp( 27 )
    run()

    outVol = VT("/vdc")
    plot(outVol ?expr '("outVol") )
    hardCopyOptions(?hcOutputFile "vdc_out.png")
    hardCopy()

    plusInVol = VT("/rfinp")
    plot(plusInVol ?expr '("plusInVol") )
    hardCopyOptions(?hcOutputFile "rfinp_out.png")
    hardCopy()

    minusInVol = VT("/rfinn")
    plot(minusInVol ?expr '("minusInVol") )
    hardCopyOptions(?hcOutputFile "rfinn_out.png")
    hardCopy()

    powP = (integ(VT("/rfinp") 2e-05 3e-05) / 1e-05)

    summaryFile = outfile("summary.txt")
    fprintf(summaryFile "Input %s C is %.3e \n" temp() powP)


    close(summaryFile)
    """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""


    Thank you.

    Menghan Sun

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.