Subversion Repositories rs232_syscon

<!--# set var="title" value="rs232_syscon synthesizable soft core." -->
<!--# include virtual="/ssi/ssi_start.shtml" -->
<b><font size=+3 face="Helvetica, Arial"color=#bf0000>Project: rs232_syscon</font></b><p><table  align=center border=1 cellPadding=2 cellSpacing=0 width="100%" valign="top"><tbody><tr bgcolor=#bbccff>    <td align=center valign=center>               
<a href="./people.shtml">People</a>               |
<a href="./documentation.shtml">Documentation</a>               |
<a href="./download.shtml">Download</a>               |
<a href="mailto:cores@opencores.org">OpenCores Mail list</a>               |
<a href="mailto:jclaytons@earthlink.net">Contact me</a>    </td></tr></tbody></table><p><font size=+1><b>Description</b></font><P>rs232_syscon is a synthesizeable soft core that allows debugging of peripherals connected to a Wishbone type of bus.  Specifically, it lets the user write and read registers, and send out reset pulses, via an rs232 serial connection to a "dumb terminal." (Such as windows "hyperterm"!)  It is completely scalable through parameter settings, to accomodate address and data buses of any arbitrary size.  Furthermore, the rs232_syscon module can share the Wishbone bus with the master (presumably a processor of some kind).  It implements a handshaking protocol with the master to "request" the bus.  When the master grants access, the rs232_syscon runs bus cycles on its own, to report contents of registers and memory back to the user, in an easy-to-read hexadecimal format.  This is very useful when debugging peripherals -- you can set the contents of memory, set up registers, and even use registers to control "single stepping" of your target processor.  If desired, the rs232_syscon can be the sole master of the Wishbone bus, to perform "human-speed" tests on peripherals (set a value, check a result) without having to connect the peripheral to a processor.<br><br>The "ack_i" and "err_i" signals of the Wishbone bus are used to determine if the bus cycles are correctly executed.  The rs232_syscon module uses a "watchdog" timer to determine if "ack_i" has arrived too late, and if so, it sends an error indicator back to the host terminal.  If "err_i" occurs, it also sends back a bus error indicator.  The timeout value of the watchdog timer is configurable by parameters to whatever length is needed, and the bus cycles are automatically extended for as many clocks as needed until the "ack_i" signal is received.  If "ack_i" is not used, simply tie it high.<p>The design team of rs232_syscon welcomes any kind of help and feedback on this core.  If you are interested in further development of this project, please contact us.<br><br><BR><p>Current Status:<ul><li>This core now supports three basic commands: 'r' (read), 'w' (write) and 'i' (initialize = reset).</li><li>The read/write commands allow a quantity field, to specify multiple writes or reads (using consecutive addresses).<li>There are no technology-dependent elements used in this core.</li><li>The data bus is currently a tri-stated bus, although separate dat_i/dat_o buses could easily be supported.</li><li>The design consumes 400-700 Xilinx Virtex slices (depending on parameters)</li><li>The core runs at around 40MHz on Xilinx SpartanII, with about 8-12 registers and some dual-ported block RAM attached to the bus.</li><li>The interface is currently implemented as a large state-machine (no processor is involved.)</li><li>The command structure is very simple and "sparse."</ul><p>In the future, a version could be implemented using a small microcontroller core with some integrated software, which would probably be more compact and flexible, with a richer command set.  But, since we wanted to use this core to _develop_ microcontroller cores -- well, it was a case of "which came first, the chicken or the egg?"  We had to start somewhere!<p>Next Steps:<ul><li>Use rs232_syscon to build and debug a small microcontroller, which may form a better rs232_syscon in the future.</li><li>Extend the command set, to make it more useful.</li></ul> <p>Maintainer(s):<ul><a href="mailto:jclaytons@earthlink.net">John Clayton</a></ul><p>Mailing-list:<ul><a href=mailto:jclaytons@opencores.org>jclaytons@opencores.org</A></ul><!--# include virtual="/ssi/ssi_end.shtml" -->