nuand/bladerf-wiphy

bladeRF-wiphy is an open-source IEEE 802.11 compatible software defined radio VHDL modem

bladerf-wiphy's Issues

Stability issues with latest Quartus version

I am using Quartus Prime 20.1.1. What version of Quartus was used to build the FPGA design? I am experiencing stability issues when I so much as add a .qip file for a new top level Platform Designer System intended to be at the top level alongside the NIOS system that comes with the design. I don't even have to instantiate anything in the top level VHDL file. Just adding the .qip file is enough to cause the resulting build to quit detecting packets after a random short interval of time.

If I build the unmodified ~/wiphy-build/bladeRF/hdl/fpga/platforms/bladerf-micro/bladerf-wlan.qip I can see a continuous printout of packets scrolling in the Linux terminal window where I am running bladeRF-linux-mac80211 in verbose mode.

I would say that works just fine. However, if I so much as add a .qip file for a new subsystem to the main bladerf-wlan.qip file and rebuild, the resulting modem quits after detecting a few packets. I have been able to correlate this to the version number of the components in the Platform Designer System .qip file; it's 20.1.

Update dependencies

bladeRF-mac80211_hwsim requires flex and bison to build successfully. Please add these to the dependency list in the install instructions.

wlanxA9-latest.rbf Version firmware appears “Detected potentially incorrect FPGA file ”

When I download the "wlanxA9-latest.rbf" firmware, a message is displayed indicating that "incorrect FPGA file" should be displayed. What should I do to solve the problem? Thank you

Update README with basic WiFi 4/5/6 details

Looking through the README and the more extensive documentation at Nuand, it seems like this might be a full implementation of WiFi 4 (802.11n). I see the channel size seems to max out at 20 MHz and the modulation max out at OFDM-64-QAM. Does this mean this stack supports WiFi 5/6 as long as you are using that 20 MHz channels with (FDM-64-QAM? Any updates to the documentation to specify this would be great!

BTW, excellent work! Thank you for your efforts!

wave.do is missing

I was following along the instructions on how to Simulate bladeRF-wiphy in Modelsim on this page: https://www.nuand.com/bladeRF-wiphy-simulation but could not find wave.do anywhere.

Reference CSV file (rx-0.csv) is missing.

When I try to access https://nuand.com/downloads/rx-0.csv, I get:
Not Found
The requested URL was not found on this server.

bladeRF 2.0 micro xA4

Does it also work on the smaller bladeRF, the bladeRF 2.0 micro xA4?

[question] Is ad-hoc supported?

Does bladerf-wiphy support ad-hoc mode? It appeared so, but I don’t seem to get any activity with it all running. Just curious to know if it’s even something that should work before I dig deeper.

matlab files

1. There is no example on how to use the matlab files. in wlan_rx.m the input signal "x" is never initialized. It would be nice to have an example file read in for x or a data capture that is used for x.

2. Acquisition of the signal is probably the very most important part of any receiver design. This function is totally skipped. Does acquisition work in the HDL design in the FPGA? Why is there no model for it?

how to see signal in tx mode?

Tx vector setting for QPSK with 12Mbps

Hi rghilduta
I am simulation the vhdl code for QPSK with 12Mbps.
What parameter should i set in TX Vector for above setting and what does length signify? I am seeing that in each packet one data symbol with 48 bit is adding am i right?
Regards
J S Hyanki

Some code apparently missing

Hi, thanks for uploading an interesting project. It looks like some code is missing, could you check?

1. DSSS transmitter completely missing
2. FEC viterbi decoder and interleaver missing for DSSS receiver
3. Matlab files incomplete

Hard coded 32 in fft.vhd

Thanks for this great project. It's awesome!
There is a hard coded 32 on Line 478 and line 502 of fft.vhd.
I tried to compute an FFT of a size other than 64, and it did not work. I got don't cares in a simulator. I replaced the hard coded 32 with (N/2). Now it works for other power of 2 FFT sizes. I only checked a few (16, 32, 64 and 128).