Project

General

Profile

Actions

Feature #5516

open

BladeRF 2.0 Support

Added by akibsayyed almost 2 years ago. Updated about 1 year ago.

Status:
In Progress
Priority:
High
Assignee:
Category:
-
Target version:
-
Start date:
04/07/2022
Due date:
% Done:

0%

Spec Reference:

Description

Dear OSMOCOM Community

I was looking to purchase LimeSDR/Mini but it's been discontinued and coming up with a newer 2.0 version

Can we put efforts in adding support for bladerf as well.

Link for new LimeSDR Mini Page
https://www.crowdsupply.com/lime-micro/limesdr-mini-2-0


Related issues

Is duplicate of OsmoTRX - Feature #2430: osmo-trx support bladerfNew08/10/2017

Actions
Actions #1

Updated by fixeria almost 2 years ago

Actions #2

Updated by laforge almost 2 years ago

Dear akib,

as you know, open source is a collaborative effort. Everyone can put effort according to their own priorities, and users of certain hardware are most welcome to implement whatever hardware support they require. We are always most happy to receive contributions for supporting any additional hardware.

Actions #3

Updated by akibsayyed almost 2 years ago

Thank you Laforge

I am happy to help in the implementation. But need right direction in same.

On Thu, Apr 7, 2022 at 4:39 PM laforge <> wrote:

Issue #5516 has been updated by laforge.

Dear akkib,

as you know, open source is a collaborative effort. Everyone can put
effort according to their own priorities, and users of certain hardware are
most welcome to implement whatever hardware support they require. We are
always most happy to receive contributions for supporting any additional
hardware.

Actions #4

Updated by laforge over 1 year ago

  • Status changed from New to In Progress
  • Assignee set to Hoernchen
  • Priority changed from Normal to High

Hoernchen, i know out-of-band that you've been wokring on this. Where are the branches and/or gerrit patches?

Actions #5

Updated by Hoernchen over 1 year ago

The blade support patch has been a part of https://gitea.osmocom.org/cellular-infrastructure/osmo-trx/commits/branch/synctoy for months because 1) sample rate is always off due to non gsm rate master clock, which makes it a bad target for "proper" operation 2) tx loses samples depending on how small the transfer buffers are 3) gain settings differ and it's not important for anything else I'm working on right now.

Actions #6

Updated by gomme600 about 1 year ago

Hoernchen wrote in #note-5:

The blade support patch has been a part of https://gitea.osmocom.org/cellular-infrastructure/osmo-trx/commits/branch/synctoy for months because 1) sample rate is always off due to non gsm rate master clock, which makes it a bad target for "proper" operation 2) tx loses samples depending on how small the transfer buffers are 3) gain settings differ and it's not important for anything else I'm working on right now.

Hi,

I have built that branch from source and now have osmo-trx-ms-blade and osmo-trx-syncthing-blade. However, there is no osmo-trx-blade. Is this normal ?

When running osmo-trx-ms-blade I get an error :

unable to lock refclk!
failed to init dev!

Is this expected as the bladeRF isn't officially supported yet or is there something wrong with my setup ?

I am trying to make a docker image compatible with both the limesdr and bladerf so it's important that I find a solution that supports both boards.

I have also tried using osmo-trx-uhd and soapyUHD. I also get an error but it doesn't make sense to me as uhd_find_devices does find the bladeRF and another piece of software detects it as a UHD device.

Here is the error :

Tue Feb 14 13:41:55 2023 DDEV <0005> UHDDevice.cpp:570 No UHD devices found with address ''
Tue Feb 14 13:41:55 2023 DMAIN <0000> osmo-trx.cpp:593 Failed to create radio device
Tue Feb 14 13:41:55 2023 DMAIN <0000> osmo-trx.cpp:564 Shutting down transceiver...

Any help would be appreciated!

Thanks,
Sebastian

Actions #7

Updated by gomme600 about 1 year ago

After further investigation it seems that the master branch currently supports the bladeRF and after compiling I have the osmo-trx-blade binary. Unfortunately I'm still getting an error saying :

Tue Feb 14 13:59:25 2023 DDEV <0005> bladerf.cpp:372 unable to lock refclk!
Tue Feb 14 13:59:25 2023 DMAIN <0000> osmo-trx.cpp:593 Failed to create radio device
Tue Feb 14 13:59:25 2023 DMAIN <0000> osmo-trx.cpp:564 Shutting down transceiver...

I am using the bladeRF 2.0 xA9 and I saw in the changenotes that the xA4 is supported. Maybe this is the problem ?

Actions #8

Updated by gomme600 about 1 year ago

Ok so for anyone interested I was able to get my bladeRF working by modifying the bladerf.cpp file and removing the return -1 line from line 373 :

if (!is_locked) {
LOGC(DDEV, ALERT) << "unable to lock refclk!";
return -1;
}

I then used the configuration files provided here : https://github.com/nickvsnetworking/osmocom-config

I used the osmo-trx-lms.cfg file for the osmo-trx-blade program.

My phone sees the network Test PLMN 1-1 2G !

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)