Programmable Devices
CPLDs, FPGAs, SoC FPGAs, Configuration, and Transceivers
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
21615 Discussions

View internal signals when simulating testbech (.vht) in ModelSim-ALTERA

Altera_Forum
Honored Contributor II
2,660 Views

After writing and compiling my .vhd program, I create a testbench in Quartus II (Processing > Start > Start Test Bench Template Writer). This process creates a .vht file.  

 

After editing and saving the .vht file, I start ModelSim-Altera from within Quartus II. Upon opening, I compile the .vho files first, and then the .vht file second. I then simulate the .vht file. When adding waveforms, I'd like to add internal signals that are in the .vhd program. However, when searching the objects view for these signals (because only the inputs and outputs are shown), some signals are found while others are not. Moreover, when simulating, the signals I did find do not simulate correctly. The fix action I have found for this is to port these signals to the top and look at them as an output.  

 

Is there a way to look at these internal signals without porting them to the top? 

 

Let me know if I need to clarify. Thanks.
0 Kudos
3 Replies
Altera_Forum
Honored Contributor II
1,504 Views

To look at internal signals, you should first simulate with the .vhd file. 

 

The .vho files are 'optimized' during synthesis, so many internal signals will 'disappear' and you cannot probe them. 

 

Cheers, 

Dave
0 Kudos
Altera_Forum
Honored Contributor II
1,504 Views

Thanks, it works. RTL functionality check allows for probing internal signals. That is, upon opening ModelSim-Altera, compile the .vhd files (bottom up) and then simulate.

0 Kudos
Altera_Forum
Honored Contributor II
1,504 Views

When probing the synthesized design using SignalTap II, you can use synthesis attributes; keep, preserve, and noprune to stop synthesis from eliminating signal names. I've never tried this with the simulator, but it likely preserves them there too. 

 

Cheers, 

Dave
0 Kudos
Reply