• 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. Functional Verification
  3. how to auto generate html document from exist e code

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 66
  • Views 13926
  • 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

how to auto generate html document from exist e code

spark
spark over 15 years ago

I heard that specman has auto document generation function from existing e code, but I dont know how to, would anyone tell me? Or which guide explain it, thank you.

  • Cancel
Parents
  • StephenH
    StephenH over 15 years ago

    The feature you're referring to is called eDoc, and the command (in Specman) is "write doc". This lets you write out HTML docs for all or some of the loaded e code. Usually we use it to generate the docs for the eRM packages rather than just the loaded files, so there is a switch to control that.

    I suggest you open up the docs and take a look to see how it works.

    All the Cadence VIP ships with eDoc files that you can explore.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • StephenH
    StephenH over 15 years ago

    The feature you're referring to is called eDoc, and the command (in Specman) is "write doc". This lets you write out HTML docs for all or some of the loaded e code. Usually we use it to generate the docs for the eRM packages rather than just the loaded files, so there is a switch to control that.

    I suggest you open up the docs and take a look to see how it works.

    All the Cadence VIP ships with eDoc files that you can explore.

    • 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