OpenBTS - EMERG: Received out of order packet

[storm]

Hi guys,

I've been following the instructions at https://github.com/Nuand/dev, compiled and installed evertying needed (I'm on Ubuntu 14.04LTS 64Bit, bladeRF x40).

When I'm running # sudo ./OpenBTS I'm getting the following EMERG alerts in OpenBTS's log below:

Starting the system...
ALERT 139925124089728 11:49:31.9 OpenBTS.cpp:439:main: starting the transceiver
EMERG 139910898964224 11:49:36.9 bladeRFDevice.cpp:343:readSamples: Received out of order packet0x7f3f800012c0
EMERG 139910898964224 11:49:36.9 bladeRFDevice.cpp:343:readSamples: Received out of order packet0x7f3f800012c0
1419004176.996603 139925124089728:
system ready

1419003151.946685 133925122089528:
use the OpenBTSCLI utility to access CLI

OpenBTS>
EMERG 139910898964224 11:49:37.0 bladeRFDevice.cpp:343:readSamples: Received out of order packet0x7f3f80002544
EMERG 139910898964224 11:49:37.0 bladeRFDevice.cpp:343:readSamples: Received out of order packet0x7f3f80002544
EMERG 139910898964224 11:49:37.0 bladeRFDevice.cpp:343:readSamples: Received out of order packet0x7f3f80002544
EMERG 139910898964224 11:49:37.0 bladeRFDevice.cpp:343:readSamples: Received out of order packet0x7f3f80002544
EMERG 139910898964224 11:49:37.0 bladeRFDevice.cpp:343:readSamples: Received out of order packet0x7f3f80002544
EMERG 139910898964224 11:49:37.0 bladeRFDevice.cpp:343:readSamples: Received out of order packet0x7f3f80002544

It continuously displaying that EMERG alerts...

Any thoughts?

[jynik]

I wonder if what you're seeing is the same underlying problem as what I just mentioned in this thread.

Although I haven't worked with OpenBTS or YateBTS much, I seen to recall their transceiver code being largely the same. If that's true, then the OpenBTS code probably needs the same patch, where the code to turn on FPGA timestamp is moved AFTER the call to bladerf_sync_config().

[storm]

You are correct!

It's the same issue, I've done as you suggested in your patch for YateBTS and it worked.

Attached is bladeRFDevice.cpp with a fix (path: dev/openbts/TransceiverRAD1).

Thanks!

[jynik]

Hey there, thanks checking back in and confirming! I'm sure other folks will appreciate being able to just quickly grabbed the patched file. I'll poke Rob soon about pulling that patch in.

Cheers!
Jon

[habib]

You are correct!

It's the same issue, I've done as you suggested in your patch for YateBTS and it worked.

Attached is bladeRFDevice.cpp with a fix (path: dev/openbts/TransceiverRAD1).

Thanks!

Hi strom
in my case , a bladeRFDevice.cpp file already in my desire location.now what should i have to do? copy paste of new bladeRFDevice.cpp file replacing with old one or edite the old one. i am confisued Attached is bladeRFDevice.cpp with a fix.i am not sure what do you mean by with a fix .As i am new , i have no idea about patch file. sorry for my stupid question.
Thanks

[storm]

Hi habib,

I should have uploaded a patch instead file with unrelated version, sorry for that

Here's a diff I made with my changes, as jynik mentioned and applied on his patch, enable of timestamps should occur after applying bladerf_sync_config for RX and TX, so all the change that need to be done is to take the lines which enable timestamps and bring them after bladerf_sync_config of RX and TX.

diff --git a/TransceiverRAD1/bladeRFDevice.cpp b/TransceiverRAD1/bladeRFDevice.cpp
index 7ab19c9..7a580b7 100755
--- a/TransceiverRAD1/bladeRFDevice.cpp
+++ b/TransceiverRAD1/bladeRFDevice.cpp
@@ -98,15 +98,6 @@ int bladeRFDevice::open()
}

sleep(1);
- bladerf_config_gpio_read(bdev, &val);
- val |= 0x10000; //enable timestamps, clears and resets everything on write
- bladerf_config_gpio_write(bdev, val);
- bladerf_config_gpio_read(bdev, &val);
- if (!(val & 0x10000)) {
- LOG(EMERG) << "Could not enable timestamps";
- return -1;
- }
- LOG(INFO) << "bladeRF timestamping enabled";

/* Stream defaults */
#define DEFAULT_STREAM_XFERS 64
@@ -117,7 +108,7 @@ int bladeRFDevice::open()
int status;
status = bladerf_sync_config(bdev,
BLADERF_MODULE_RX,
- BLADERF_FORMAT_SC16_Q12,
+ BLADERF_FORMAT_SC16_Q11,
DEFAULT_STREAM_BUFFERS,
DEFAULT_STREAM_SAMPLES,
1,
@@ -130,7 +121,7 @@ int bladeRFDevice::open()

status = bladerf_sync_config(bdev,
BLADERF_MODULE_TX,
- BLADERF_FORMAT_SC16_Q12,
+ BLADERF_FORMAT_SC16_Q11,
4,
DEFAULT_STREAM_SAMPLES,
1,
@@ -141,6 +132,17 @@ int bladeRFDevice::open()
LOG(EMERG) << "Failed to intialize TX sync handle" << bladerf_strerror(status);
}

+ sleep(1);
+ bladerf_config_gpio_read(bdev, &val);
+ val |= 0x10000; //enable timestamps, clears and resets everything on write
+ bladerf_config_gpio_write(bdev, val);
+ bladerf_config_gpio_read(bdev, &val);
+ if (!(val & 0x10000)) {
+ LOG(EMERG) << "Could not enable timestamps";
+ return -1;
+ }
+ LOG(INFO) << "bladeRF timestamping enabled";
+
samplesRead = 0;
samplesWritten = 0;
started = false;

Does that make sense?

[habib]

Thanks for your replay. i will try it later and tell you about my result.