• 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. ADEXL Test Setup using Skill and asiGetSession Failure

Stats

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

ADEXL Test Setup using Skill and asiGetSession Failure

Curtisma
Curtisma over 8 years ago

I'm trying to setup an adexl cellview with a single test.  However everytime I load the script shown below the asiGetSession on line 7 often returns nil and its not clear why that is the case.  Any ideas as to what is causing it to fail to get the session?  Is there a better way to setup the state of that test using SKILL (not ocean)?

ddGetObj("pk1126_sky77366_5_CR_mayberc" "pk1126_01_TB" "adexl" "data.sdb" nil "w")
sessionName = strcat("mysession" (sprintf nil "%d" random()))
axlSession = axlCreateSession(sessionName)
sdb = axlSetMainSetupDBLCV( axlSession "pk1126_sky77366_5_CR_mayberc" "pk1126_01_TB" "adexl")

;---------- Test "IDAC_SWEEP_MAIN" -------------
testSession = asiGetSession( 'IDAC_SWEEP_MAIN )
dc_analysis = asiGetAnalysis(testSession, 'dc)
asiSaveState(testSession ?name "IDAC_SWEEP_MAIN" ?option 'dir ?stateDir "/prj/pk1126_sky77366_5_CR/work_libs/mayberc/cds/design/pk1126_01_TB/adexl/test_states" ?description "IDAC_SWEEP_MAIN" )
htest = axlPutTest( sdb "IDAC_SWEEP_MAIN" "ADE")
axlSetTestToolArgs( htest list( list("lib" "pk1126_sky77366_5_CR_mayberc") list("cell" "pk1126_01_TB") list("view" "config") list("path" "/prj/pk1126_sky77366_5_CR/work_libs/mayberc/cds/design/pk1126_01_TB/adexl/test_states") list("state" "IDAC_SWEEP_MAIN_active") list("sim" "spectre")))

;====================== Save Setup ============================================
axlSaveSetup(axlSession)
axlCommitSetupDB( sdb )
axlCloseSetupDB( sdb )

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    You're doing this the wrong way. You should look at this solution which gives an example of how to do this.

    It doesn't make sense to do asiGetSession() that way and then asiSaveState - what you should be doing is putting the test, and then something like this:

    testName="IDAC_SWEEP_MAIN"
    htest = axlPutTest( sdb testName "ADE")
    axlSetTestToolArgs(htest list( list("lib" libName) list("cell" cellName) list("view" "schematic") list("sim" "spectre")))
    testsess=axlGetToolSession(axlSession testName)
    testSession=asiGetSession(testsess)

    (I tend to use sevEnvironment(testsess) for the last bit, but I don't think it matters).

    Then having got that you can do whatever you need to the test session, no need to save state or anything like that.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    You're doing this the wrong way. You should look at this solution which gives an example of how to do this.

    It doesn't make sense to do asiGetSession() that way and then asiSaveState - what you should be doing is putting the test, and then something like this:

    testName="IDAC_SWEEP_MAIN"
    htest = axlPutTest( sdb testName "ADE")
    axlSetTestToolArgs(htest list( list("lib" libName) list("cell" cellName) list("view" "schematic") list("sim" "spectre")))
    testsess=axlGetToolSession(axlSession testName)
    testSession=asiGetSession(testsess)

    (I tend to use sevEnvironment(testsess) for the last bit, but I don't think it matters).

    Then having got that you can do whatever you need to the test session, no need to save state or anything like that.

    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