OpenCores
URL https://opencores.org/ocsvn/wbuart32/wbuart32/trunk

Subversion Repositories wbuart32

[/] [wbuart32/] [trunk/] [bench/] [verilog/] [README.md] - Diff between revs 5 and 13

Go to most recent revision | Show entire file | Details | Blame | View Log

Rev 5 Rev 13
Line 1... Line 1...
This directory contains three basic configurations for testing your UART
This directory contains three basic configurations for testing your UART
and proving that it works:
and proving that it works:
- helloworld: Displays the familiar "Hello, World!" message over and over.  Tests the transmit UART port.
- [helloworld](helloworld.v): Displays the familiar "Hello, World!" message over and over.  Tests the transmit UART port.
- linetest: Reads a line of text, then parrots it back.  Tests both receive and transmit UART.
- [echotest](echotest.v): Echoes any characters received directly back to the transmit port.  Two versions of this exist: one that processes characters and regenerates them, and another that just connects the input port to the output port.  These are good tests to be applied if you already know your transmit UART works.  If the transmitter works, then this will help to verify that your receiver works.  It's one fault is that it tends to support single character UART tests, hence the test below.
- speechfifo: Recites the Gettysburg address over and over again.  This can be used to test the transmit UART port, and particularly to test receivers to see if they can receive 1400+ characters at full speed without any problems.
- [linetest](linetest.v): Reads a line of text, then parrots it back.  Tests both receive and transmit UART.
 
- [speechfifo](speechfifo.v): Recites the [Gettysburg address](../cpp/speech.txt) over and over again.  This can be used to test the transmit UART port, and particularly to test receivers to see if they can receive 1400+ characters at full speed without any problems.
 
 
Each of these configurations has a commented line defining OPT_STANDALONE within
Each of these configurations has a commented line defining OPT_STANDALONE within
it.  If you uncomment this line, the configurations may be run as stand alone
it.  This option will automatically be defined if built within Verilator,
configurations.  (You will probably want to adjust the baud clock divider, to
allowing the Verilator simulation to set the serial port parameters.  Otherwise,
be specific to the baud rate you wish to generate as well as the clock rate
you should be able to run these files as direct top level design files.  (You
you will be generating this from.)
will probably want to adjust the baud clock divider if so, so that you can set
 
to the baud rate you wish to generate as well as the clock rate you will be
 
generating this from.)
 
 
If you leave OPT_STANDALONE commented, these demo programs should work quite
 
nicely with a Verilator based simulation.
 

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.