• 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. Configure VHDL design for simulation using VHDL Tool Bo...

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 13647
  • 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

Configure VHDL design for simulation using VHDL Tool Box

pyohayo
pyohayo over 6 years ago

Hello,

In my simple setup I proceeded as follows:

  1. Created cell block_A (clock stimuli)
  2. Created symbol view for block_A 
  3. In Symbol Editor ... "Create CellView from CellView", then select VHDL... cellview entity was created
  4. In Library Manager created new CellView (tolol VHDL-Editor) and named it vhdl
  5. Put block_A architecture in vhdl cellview
  6. Did pp. 1 ... 5 for block_B (device under test)
  7. Created schematic block_C, where I connected block_A and block_A 
  8. In VHDL Tool Box selected block_C as top hierarchy
  9. Run simulation
  10. In SimVision design browser for block_A it's Ok - I can see internal signals, whereas for only ports are seen  ... and consequently simulation results are not relevant
  11. Then I tried ro create config view for block_C ... but couldn't properly setup it ... what view should I put in "View ro Use" for block_A and block_B ? Only one view is accepted, whereas both entity and architectury are needed.

Thanks in advance.

Pavel.

  • Cancel
Parents
  • pyohayo
    pyohayo over 6 years ago

    Well ... the problem is resolved: there was a syntax error in  block_B    architecture.

    Before closing this topic can someone confirm ... or refute the following contents of config view for block_C:

    Cell                         View Found                           View to Use                    Inherited View List

    block_A                  vhdl                                         empty                               stimulus dataflow vhdl entity schematic symbol

    block_B                 vhdl                                          empty                              stimulus dataflow vhdl entity schematic symbol

    block_C                 schematic                              empty                               stimulus dataflow vhdl entity schematic symbol

    Thanks.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • pyohayo
    pyohayo over 6 years ago

    Well ... the problem is resolved: there was a syntax error in  block_B    architecture.

    Before closing this topic can someone confirm ... or refute the following contents of config view for block_C:

    Cell                         View Found                           View to Use                    Inherited View List

    block_A                  vhdl                                         empty                               stimulus dataflow vhdl entity schematic symbol

    block_B                 vhdl                                          empty                              stimulus dataflow vhdl entity schematic symbol

    block_C                 schematic                              empty                               stimulus dataflow vhdl entity schematic symbol

    Thanks.

    • 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