• 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. Logic Design
  3. Redirecting a command output to a file.

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 62
  • Views 23342
  • 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

Redirecting a command output to a file.

nozuey
nozuey over 14 years ago

Hi,

How can I redirect the output from    puts [find / -instance "U_*"]   to a file  on RTL Compiler ?

 I simply tried > and this is what I got.

rc:/designs> puts [find / -instance "U_*"]  > inst
bad argument "inst": should be "nonewline"

I also wonder why redirection with > works differently on different commands, even though they all output the results to STDOUT.  I mean "report area > file" works, but find / -instance "*" > file does not.  Any thoughts ?

 

Thanks

 

  • Cancel
Parents
  • bmiller
    bmiller over 14 years ago

    In addition to what grasshopper mentioned, you can consider using standard TCL syntax to output "puts" to a file:

     

    set _file [open file.txt w]
    puts $_file [find ....]
    close $_file


    Or, to output the result one line at a time:

    set _file [open file.txt w]
    foreach i [find ....] {puts $_file $i}
    close $_file


    Good Luck!

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • bmiller
    bmiller over 14 years ago

    In addition to what grasshopper mentioned, you can consider using standard TCL syntax to output "puts" to a file:

     

    set _file [open file.txt w]
    puts $_file [find ....]
    close $_file


    Or, to output the result one line at a time:

    set _file [open file.txt w]
    foreach i [find ....] {puts $_file $i}
    close $_file


    Good Luck!

     

    • 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