Dieter wrote: >>> tim> The easiest interface (and arguably the most cross-platform) would be >>> tim> a simple terminal interface on the serial line. Fire up minicom or >>> tim> hyperterminal or whatever... to 8N1 @ 152000 and go. >>> tim> >>> tim> Easy to program, easy to use. No GUI needed. >>> >>> The command interface could probably be CLI. While the data display >>> could also be text based, you can display a lot more data using >>> graphics, so the data display should probably be graphical. >> Remember that 19200 bits/sec isn't very fast. I'd hate to slow it >> down by using an ASCII interface. > > A CLI or text based display does not imply a 19200 bits/sec limit. > I can send text to an xterm window way faster than 19200 bits/sec. > > The data capture running on the OGD can only talk to the analyzer > software at RS-232 speeds, (which are officially capped at 20,000 > although most systems these days can run much faster) but the analyzer > software is likely to have a faster path to the display, most likely > either a video card in the same machine or an Ethernet connection to a > machine with the display.
If we could use an opencores cpu and create an embedded single-task "pc" in the analyzer card, it can use its own dvi output, or two to display the data, is that fast enough? ;) And instead of creating an RS232 interface, we make one for PS/2 (keyboard and optionally mouse). (I have no idea if there is a synthetizable and stable core which has gcc support so it could be programmed quickly to behave as an logic analyzer gui) D. _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
