BLADERF Open Air Interface DC Cal issues

Having issues with the site, hardware, source code, or any other issues?

Moderator: robert.ghilduta

Post Reply
mattdahm
Posts: 2
Joined: Wed Nov 28, 2018 1:18 pm

BLADERF Open Air Interface DC Cal issues

Post by mattdahm » Wed Nov 28, 2018 1:29 pm

I have a bladeRFx40 and am trying to get my eNB basestation going from openairinterface. I am running 16.04 Ubuntu. My issue is every time I try to run my lte-softmodem with my bladerfx40 config I get the following error.

[DEBUG @fpga_common/src/lms.c:2756] Bad DC_REGVAL detected. DC cal failed.
[DEBUG @fpga_common/src/lms.c:2843] DC Cal retry limit reached
[WARNING @ fpga_common/src/lms.c:3000] DC Calibration (module=1) failed to converge.
Failed to calibrate TX DC: An unexpected error occurred
Aborted (core dumped)

bladeRF> version
bladeRD-cli version: 1.7.0-2018.10-rc1-1-ppaxenial
libbladeRD version: 2.1.0-2018.10-rc1-1-ppaxenial

Firmware version 2.3.1
FPGA version: 0.9.0 (configured by USB host)


On a side note I followed steps at https://github.com/Nuand/bladeRF/wiki/D ... Correction top generate my calibration table and moved the file to the corresponding folder before hand.

Any help and/or troubleshooting is greatly appreciated.

Thanks guys,

Matt

mattdahm
Posts: 2
Joined: Wed Nov 28, 2018 1:18 pm

Re: BLADERF Open Air Interface DC Cal issues

Post by mattdahm » Thu Nov 29, 2018 10:04 am

I have found issue is stemming from the openairinterface interacting with the BLADERF.

Response copied below:

Hi Matt

I'm glad if you can use it as a reference.

We have used BladeRF x115 and had same issue.

The issue was improved with the combination of the following versions

BladeRF:
  bladeRF-cli version: 1.4.0-git-unknown
  libbladeRF version: 1.7.2-git-unknown
  Firmware version: 2.0.0
  FPGA version: 0.6.0

Best regards
Tanaka

Dear Matt,

use the branch 'develop' and
have a look at the file targets/ARCH/BLADERF/README if you didn't already do it.

You may also try ubuntu 18.04.

On our side we also see this kind of errors sometimes. We just rerun the softmodem until it works (so there may be some real problems here, but we couldn't identify them).

Regards.

Post Reply