- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi - I can't find much on the web about this, but I'm wondering if anyone else has run into, or (even better) solved, this issue... I'm using free modelsim with my paid quartus. When I run modelsim interactively, and, at the beginning of the sim, tell it to log signals, often many signals aren't logged. I'm not talking about memories, or constants, or other funny things, just garden-variety signals.
Actually, log -r /* gives me my best results, but when I try something like log /top/* log /top/oneleveldown/* log /top/oneleveldown2/* the coverage is very spotty. I don't want to log everything all the time (takes too long), but there's something about being selective that causes me to lose out. Even if I just try to log all my test-bench signals (log /tb_top/*) I don't get many of them. Can anyone shed some light? Thanks! /jLink Copied
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've actually upgraded to paid Modelsim ($945 upgrade), and I continue to have this problem. log -r /* doesn't seem to work. Whenever I add signals to waves, I almost always have to re-run the simulation. It's gotten worse with the newest release. What could be breaking this?
/j
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page