On 10/19/06, Nicholas <[EMAIL PROTECTED]> wrote:
> Nicholas' video block is very good too, but it doesn't bring the video > output signals to the top-level module. It's just easier to use > Simon's. > > However, what Nicholas did do for us that was excellent is produce a > video capture block. This module acts like a monitor, watching video > signals, and spits the video frame out to a PPM file. There are only > two modifications I would suggest (or may make myself). > Yes, I recently (as in yesterday, I was going to post it today) combined them into one, and so the video signals go to the top level.
Combined which parts?
Also, a point of caution: the VCD file is ballooning in size. It is now approx. 450MB. I couldn't open it in GTKWave to analyze waveforms because while it did load, the UI was so slow that it still hadn't redrawn the screen after 30 min! I resorted to looking at the scanimage.ppm file instead.
As long as it's mostly working, you can turn off the VCD capture and just use the PPM file as your diagnostic. If you find a bug, then change the timing numbers to something really small and THEN use a waveform viewer. Not only does signal capture take up space, but it slows the simulation. Also, you can select a subset of signals to capture. You can capture only selected interesting signals.
Again, this should be much nicer later tonight (e.g. no editing needed)! PS. I attached a version with the 1600 width if people want it. Also, I need to add the dual licensing stuff to it - for now there is nothing, but pretend that it has the whole message.
I look forward to it. :) _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
