https://github.com/jhshi/openofdm

Sythesizable, modular Verilog implementation of 802.11 OFDM decoder.
https://github.com/jhshi/openofdm

802-11 ofdm verilog

Last synced: 3 months ago
JSON representation

Sythesizable, modular Verilog implementation of 802.11 OFDM decoder.

• Host: GitHub
• URL: https://github.com/jhshi/openofdm
• Owner: jhshi
• License: apache-2.0
• Created: 2017-04-26T18:32:11.000Z (about 7 years ago)
• Default Branch: master
• Last Pushed: 2023-01-29T05:08:45.000Z (over 1 year ago)
• Last Synced: 2024-01-17T19:52:59.102Z (6 months ago)
• Topics: 802-11, ofdm, verilog
• Language: Verilog
• Homepage: http://openofdm.rtfd.io
• Size: 26.8 MB
• Stars: 325
• Watchers: 23
• Forks: 172
• Open Issues: 13
• Metadata Files:
  • Readme: Readme.rst
  • License: LICENSE.txt

Lists

• awesome-opensource-hardware - openofdm
• awesome-stars - jhshi/openofdm - Sythesizable, modular Verilog implementation of 802.11 OFDM decoder. (Verilog)
• awesome-opensource-hardware-repos - openofdm

README

        
OpenOFDM

========

This project contains a Verilog implementation of 802.11 OFDM PHY decoder.

Features are:

 - Fully synthesizable (tested on Ettus Research USRP N210 platform)

 - Full support for legacy 802.11a/g

 - Support 802.11n for MCS 0 - 7 @ 20 MHz bandwidth

 - Cross validation with included Python decoder 

 - Modular design for easy modification and extension

See full documentation at http://openofdm.readthedocs.io.

Environment Setup

-----------------

This project has the following dependencies:

 - `Icarus Verilog `_: for compiling Verilog files and simulation.

 - `GtkWave `_: for wave form visualization.

Input and Output

----------------

In a nutshell, the top level ``dot11`` Verilog module takes 32-bit I/Q samples

(16-bit each) as input, and output decoded bytes in 802.11 packet. The sampling

rate is 20 MSPS and the clock rate is 100 MHz. This means this module expects

one pair of I/Q sample every 5 clock ticks.

License

-------

`Apache License 2.0 `_

FAQs

----

**Q: Is there any need to change host driver UHD to incorporate new changes in

FPGA?**

A: No. In fact OpenOFDM relies on the current UHD-USRP communication mechanism.

However, since the logic of the FPGA is changed in OpenOFDM, its behavior is

also different. For instance, utilities such as ``rx_samples_to_file`` do not

work as expected since the FPGA in OpenOFDM does not dumping RF signals back to

host.

**Q: Any example code to communicate with OFDM core in FPGA from host?**

A: OpenOFDM FPGA module is configurable via USRP user setting registers

(``set_user_reg`` function). The

register address definition is in `common_params.v

`_. The

whole OpenOFM FPGA module takes 32 bit I/Q samples and outputs decoded bytes. It

is supposed to be placed in the receive chain of the USRP (e.g.,

``custom_dsp_rx.v``.

**Q: Is there any change in ZPU firmware?**

A: No.