Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • O openlab_wiki
  • Project information
    • Project information
    • Activity
    • Members
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
Collapse sidebar
  • openlab
  • openlab_wiki
  • Wiki
  • OpenLab_osci_FPGA_imp2

OpenLab_osci_FPGA_imp2 · Changes

Page history
try to fix OpenLab_osci_FPGA_imp2.asciidoc authored Mar 09, 2017 by Patrick Schmitt's avatar Patrick Schmitt
Hide whitespace changes
Inline Side-by-side
OpenLab_osci_FPGA_imp2.asciidoc
View page @ ce6b1818
......@@ -46,13 +46,20 @@ It can be used in order to detect corrupted data packets, but uses bandwidth and
Depending on the configuration of the UART interface, the stop bit can be 1, 1.5 or 2 bits long. The data rate depends on the selected baud rate.
It declares the frequency at which one bit is transfered. Regarding the OpenLab oscilloscope, the UART communication is configured to use a 8 bit wide word, no parity bit and 1 stop bit.
{empty} +
== Receive Component
The receiving part of the UART implementation is directly connected to the RX line of the Transistor-Transistor Logic (TTL) serial adapter cable.
This component detects incoming data by checking continually the status of the RX line.
If it detects an falling edge, data is being sent to the FPGA. This is also known as the start bit of the serial communication, which is described in section 5.3.1.
For correctly interpreting the sequence of bits, the FPGA has to store the information at the frequency of the baud rate.
For example, to receive data at 1 MBaud, the system clock of the OpenLab FPGA design
hast to be clocked down to 1 MHz. This is done by implementing a simple clock divider. At
each clock cycle one bit of the received data package is stored into a register. After the stop bit
was received, the "FINISHED" flag is set and the data is ready for further processing.
{empty} +
== Transmit Component
......@@ -60,6 +67,8 @@ This component is structured in a similar way as the receiving part, explained i
To prevent corrupted data, the transfer will only start after the "START" input signal is high.
During transfer the "BUSY" line will be high to indicate that the transmitter is currently in use and the output data of the transmitter is not yet valid.
{empty} +
== Transfer Rate and Data Integrity
The maximum achievable stable transfer rate of the SERIAL_COM_8N1 component, is 2 MBaud. However, the FPGA is theoretical capable of much higher data rates.
......@@ -69,4 +78,6 @@ In order to prevent this, the baud rate of the UART communication component can
The baud rate can be selected between 1.2 MBaud, 1.5 MBaud and 2 MBaud.
As the default setting, 1.5 MBaud was chosen to be the most reliable transfer speed in relation to different kinds of PCs and operating systems.
{empty} +
== https://es.technikum-wien.at/openlab/openlab_wiki/wikis/home[Home] | https://es.technikum-wien.at/openlab/openlab_wiki/wikis/board_TIVAC[<Microcontroller-based TIVAC] | https://es.technikum-wien.at/openlab/openlab_wiki/wikis/sig_proc_osci_hardware[Signal Processing Front-End (XMC,TIVAC,DE0-Oscilloscope)>]
Clone repository
  • ETS_theory
  • OpenLab_RCL_uC_imp
  • OpenLab_SignalToolkit
  • OpenLab_UI_source_uC_imp
  • OpenLab_firm_ip_intro
  • OpenLab_logic_uC_imp
  • OpenLab_osci_FPGA_imp
  • OpenLab_osci_FPGA_imp1
  • OpenLab_osci_FPGA_imp2
  • OpenLab_osci_FPGA_imp3
  • OpenLab_osci_FPGA_imp4
  • OpenLab_osci_LPC_imp
  • OpenLab_osci_TIVAC_imp
  • OpenLab_osci_XMC_imp
  • OpenLab_siggen_ATMEL_imp
View All Pages