I am following this link of bladeRF to set the sampling rate up to 100 MHz - https://www.nuand.com/2023-02-release-1 ... bandwidth/
I am receiving signals with osmocom source, so in the device parameter I am writing "bladerf=0,sample_format=8,feature=oversample", as is explained in the link. But, this is not working because it appears the error RuntimeError: set_sample_rate: Failed to set sample rate: Provided parameter was out of the allowable range (-2).
I don't know if someone knows what it is happening because I am following the steps of the official page of bladerf.
Thanks!
Failed to expand sample rate up to 100 MHz.
-
benjamindrake
- Posts: 1
- Joined: Tue Nov 04, 2025 8:15 pm
- Contact:
Re: Failed to expand sample rate up to 100 MHz.
I’m running into the same issue when trying to set the sampling rate to 100 MHz using the parameters from the official Nuand post. The device string bladerf=0,sample_format=8,feature=oversample causes a “Provided parameter was out of the allowable range (-2)” error in GNU Radio (osmocom source).
It seems that even with the new firmware, the oversampling mode might not be properly exposed through the osmocom source or the underlying driver version. Could the bladeRF devs confirm whether the latest libbladeRF and FPGA image support 100 MHz rates through the osmocom blocks, or if we need to configure this manually via bladeRF-cli first?
It seems that even with the new firmware, the oversampling mode might not be properly exposed through the osmocom source or the underlying driver version. Could the bladeRF devs confirm whether the latest libbladeRF and FPGA image support 100 MHz rates through the osmocom blocks, or if we need to configure this manually via bladeRF-cli first?
-
radiomuxer
- Posts: 4
- Joined: Tue Nov 26, 2024 9:59 am
Re: Failed to expand sample rate up to 100 MHz.
It's likely that gnuradio-companion is not linking to an updated gr-osmosdr build. Our PR for supporting the new sample formats and oversample feature just made it upstream in gr-osmosdr. If not already completed, install gr-osmosdr from source.
You may have to `sudo apt remove gr-osmosdr` or `sudo apt remove libgnuradio-osmosdr0.2.0t64:amd64` since gnuradio-companion may prioritize the apt installed versions.
Here's the multi-installed gr-osmosdr lib issue I was dealing with.
We should see log messages containing feature and sample format assignments when linked to the supported gr-osmosdr version.
Code: Select all
git clone https://gitea.osmocom.org/sdr/gr-osmosdr
# or git clone https://github.com/osmocom/gr-osmosdr
cd gr-osmosdr
mkdir build && cd build
cmake .. && make -j
sudo make install
Here's the multi-installed gr-osmosdr lib issue I was dealing with.
Code: Select all
# gnuradio-companion still links to usr/lib version here
└> ldconfig -p | grep osmosdr
libgnuradio-osmosdr.so.0.2.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libgnuradio-osmosdr.so.0.2.0
libgnuradio-osmosdr.so.0.2.0 (libc6,x86-64) => /usr/local/lib/x86_64-linux-gnu/libgnuradio-osmosdr.so.0.2.0
libgnuradio-osmosdr.so (libc6,x86-64) => /usr/local/lib/x86_64-linux-gnu/libgnuradio-osmosdr.so
└> sudo apt remove libgnuradio-osmosdr0.2.0t64:amd64
└> sudo ldconfig
# Fixed
└> ldconfig -p | grep osmosdr
libgnuradio-osmosdr.so.0.2.0 (libc6,x86-64)
=> /usr/local/lib/x86_64-linux-gnu/libgnuradio-osmosdr.so.0.2.0
libgnuradio-osmosdr.so (libc6,x86-64)
=> /usr/local/lib/x86_64-linux-gnu/libgnuradio-osmosdr.so
[bladeRF source] init: Opening Nuand bladeRF with device identifier string '*:instance=0'
[bladeRF source] Device: Nuand bladeRF 2.0 Serial # 95e0...7d1f FW v2.6.0 FPGA v0.16.0
[bladeRF source] init: OVERSAMPLE feature enabled
[bladeRF source] init: Sample format set to 8bit
[bladeRF source] init: Buffers: 512, samples per buffer: 4096, active transfers: 32
[bladeRF source] bladerf_source_c: DEBUG: initialization complete