• 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. Allegro X PCB Editor
  3. Shell Command Window

Stats

  • Replies 11
  • Subscribers 160
  • Views 20395
  • Members are here 0
More Content

Shell Command Window

jmwilk
jmwilk over 16 years ago

Hi All,

Is there anyway using skill to run shell commands so the command window is minimalized or in background mode so that the command window doesn't appear to the user...?

 Thanks,

 JMWilk

  • Sign in to reply
  • Cancel
Parents
  • fxffxf
    fxffxf over 16 years ago

     The doc has a netin example, args are:     

        axlRunBatchDBProgram("netin" 
    "netin -$ -g -y 1 netlist %s"
    ?startMsg "Logic Import"
    ?logfile "netin"
    ?reloadDB t)
     args:
    1) the first arg can be any descriptive string
    2) the 2nd arg is the command line with options that you want to run netin. Typically you can go to the
       DOS command window and type "netin -help" to get a description of the arguments. "netlist" is the name
       of the 3rd party netlist file netin should read (netin will automatically add .txt extension). The "%s" is
       where axlRunBatchDBProgram to will insert the name of the current design. By default, axlRunBatchDBProgram
       will save the current design to a temp file on disk before running the specified program. If you want to
       have netin process a different design then use the "?noUnload t" option and but in the real design name
       instead of "%s". 
    3) Optional start msg to user
    4) Option logfile. If you want axlRunBatchDBProgram to suppress its logfile display use the "?silent t" option
    5) Since netin will save the db to disk the reloadDB option tells axlRunBatchDBProgram reload the database if
       netin is successful 
     
    If you want to see how the Allegro GUI sets command line options to its various batch programs then you should
    set the env variable "wait_debug" before doing an operation like Import Logic. Allegro reports to
    its status area the options it used to invoke the batch program. 
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • fxffxf
    fxffxf over 16 years ago

     The doc has a netin example, args are:     

        axlRunBatchDBProgram("netin" 
    "netin -$ -g -y 1 netlist %s"
    ?startMsg "Logic Import"
    ?logfile "netin"
    ?reloadDB t)
     args:
    1) the first arg can be any descriptive string
    2) the 2nd arg is the command line with options that you want to run netin. Typically you can go to the
       DOS command window and type "netin -help" to get a description of the arguments. "netlist" is the name
       of the 3rd party netlist file netin should read (netin will automatically add .txt extension). The "%s" is
       where axlRunBatchDBProgram to will insert the name of the current design. By default, axlRunBatchDBProgram
       will save the current design to a temp file on disk before running the specified program. If you want to
       have netin process a different design then use the "?noUnload t" option and but in the real design name
       instead of "%s". 
    3) Optional start msg to user
    4) Option logfile. If you want axlRunBatchDBProgram to suppress its logfile display use the "?silent t" option
    5) Since netin will save the db to disk the reloadDB option tells axlRunBatchDBProgram reload the database if
       netin is successful 
     
    If you want to see how the Allegro GUI sets command line options to its various batch programs then you should
    set the env variable "wait_debug" before doing an operation like Import Logic. Allegro reports to
    its status area the options it used to invoke the batch program. 
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Children
No Data
Cadence Guidelines

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