• 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 Design
  3. skill to detect ADEXL options

Stats

  • Locked Locked
  • Replies 38
  • Subscribers 127
  • Views 26314
  • 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

skill to detect ADEXL options

ejm20
ejm20 over 14 years ago

Im trying to create a skill script that will look at the ADEXL HPO options to calculate the required tokens.  Ive been able to read the options on the HPO panel but need some help with the rest.   Heres the beginning of the code:


;; defining the PreRun function
(define (PreRun session_name sdb_highandle mode_string test_name)
        (printf "Launching a new run %L %L %L %L\n" session_name sdb_highandle mode_string test_name)
       

       tests=axlGetTests(sdb_highandle)
            
    jobPolicyName=axlGetAttachedJobPolicy()->name
    distmethod=axlGetAttachedJobPolicy()->distributionmethod

         ;; traversing all the tests and changing the mt option as per the requirement

   foreach(  test_name cadr(tests)
      if(  axlGetEnabled(axlGetTest(sdb_highandle test_name)) then
          printf("test %s is enabled\n" test_name)
          testSession=axlGetToolSession(session_name test_name)
        
    println( "check MT options")        
    
          mt_opt=testSession~>simID~>data~>env~>data~>turboOpts~>data~>mtOption~>value
          if(eq(strcmp(mt_opt "Manual")  0) printf("  Manual MT will be disabled!!! \n"))
          if(eq(strcmp(mt_opt "Disable")    0) printf("Disabled MT \n"))
          if(eq(strcmp(mt_opt "Auto")     0) printf(" Auto MT will be disabled!!! \n"))
          if(eq(strcmp(distmethod "Local") 0) then printf(" Turning off the MT options for this test \n")
            testSession~>simID~>data~>env~>data~>turboOpts~>data~>mtOption~>value="Disable" )

    println( "check tool options")        

      tool_opt=testSession~>simID~>data~>env~>data~>turboOpts~>data~>uniMode~>value
       if(eq(strcmp(tool_opt "Spectre")  0) printf(" This is a Spectre run \n"))
       if(eq(strcmp(tool_opt "Turbo")  0) printf(" This is a Turbo run    \n"))
       if(eq(strcmp(tool_opt "APS")  0) printf(" This is an APS  run \n"))
       
    println( "check parasitic reduction option")        
 
       paraRed_opt=testSession~>simID~>data~>env~>data~>turboOpts~>data~>psrSwitch~>value
       if(eq(strcmp(paraRed_opt t )  0) printf(" parasitic reduction enabled \n"))
       if(eq(strcmp(paraRed_opt nil )  0) printf(" parasitic reduction disabled \n")

 The first issue is that paraRed_opt is either a nil or t  so strcmp wont work, is a simular command for t/nil ?

 Once I have the options gathered, I can use a series of if/thens but is there a more elegant way to handle this like with a truth table or increment command?

 Thanks

 

  • Cancel
  • ejm20
    ejm20 over 14 years ago

    First I appreciate your time and info!!!   This is how we are using it.  What is the correct way to select ultrasim since the HPO for does not have that has a option.   You can open the simulator from either ADE or ADEXL and then select it.  Should ultrasim be used with ADEXL?

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 14 years ago

    Ultrasim is a separate simulator - it's very different in the way that it works. Whilst it shares some technology with spectre (e.g. device modelling and the netlist parser), it's a different simulator in the same way that hspice is, ams is and so on. For this you should use the simulator form (or test->simulator in ADE XL) to choose UltraSim. It's perfectly OK to use any simulator that's integrated in ADE L in ADE XL.

    The ability to set "aps" as a separate simulator (as opposed to a special mode of spectre) was a stop-gap measure during the early development of the APS technology. It never really was a wholly separate simulator in the same way that UltraSim is.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ejm20
    ejm20 over 14 years ago

    In summary, when selecting aps or turbo (for now) always select this on the HPO form, not thru the simulator menu option for both ADE and ADEXL.   When selecting UltraSim, you can use the simulator menu since its not listed on the HPO form.

    Is this correct??

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 14 years ago
    Yes
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ejm20
    ejm20 over 14 years ago

     Hi Andrew - I converted the code to the public commans as you suggested and it works quite well.  Below is the trigger for ADEXL.  The HPO command look the same for ADE so how can I create a trigger for ADE ?

     
    ;; defining the RegisterPreRunCallback function
     
    (define (RegisterPreRunCallback session_name)
            (axlSessionConnect session_name "preRun" 'PreRun))

    ; when ADE XL creates a new session it will call the RegisterPreRunCallback
     (axlSessionRegisterCreationCallback 'RegisterPreRunCallback)

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Michael85
    Michael85 over 13 years ago

    Hi,

     I'm trying to get the state of the tests (enable or disable).

    How can I do that?

     Thanks,

               Michael

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    Hi Michael,

    sess=axlGetWindowSession()
    sdb=axlGetMainSetupDB(sess)
    testNames=cadr(axlGetTests(sdb))
    foreach(test testNames
      printf("Test %s is %s\n"
        test if(axlGetEnabled(axlGetTest(sdb test)) "enabled" "disabled")
      )
    )

    Regards,

    Andrew.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Michael85
    Michael85 over 13 years ago

    Hi Andrew,

     Thanks a lot.

    Michael.

    • Cancel
    • Vote Up 0 Vote Down
    • 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