Failed to use OpenBTS fuzzing IoT Module with LimeSDR

I’m a new limesdr player,while yesterday i trying to use OpenBTS with my LimeSDR , i met some problems can’t be overcome,anyone could help me?Thanks a million!
Details as Follows:

gogogo@ubuntu:~/sdr/dev/openbts/Transceiver52M$ sudo ./transceiver
[sudo] password for gogogo:
linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_003.010.002.000-3-g122bfae1

Using internal frequency reference
Using OpenUSRP
Gateware version mismatch!
Expected gateware version 2, revision 9
But found version 2, revision 8
Follow the FW and FPGA upgrade instructions:
Or run update on the command line: LimeUtil --update

Reference clock 30.720 MHz
LMS7002M cache /home/father/.limesuite/LMS7002M_cache_values.db
Rx Filter calibrated from cache
Tx Filter calibrated from cache
Rx Filter calibrated from cache
Tx Filter calibrated from cache
– Setting master clock rate selection to ‘manual’.
ALERT 30914:30969 2017-09-06T16:19:18.5 UHDDevice.cpp:709:check_rx_md_eremphasized textr: UHD: Receive timed out
ALERT 30914:30969 2017-09-06T16:19:18.5 UHDDevice.cpp:783:readSamples: UHD: Version
ALERT 30914:30969 2017-09-06T16:19:18.5 UHDDevice.cpp:784:readSamples: UHD: Unrecoverable error, exiting…
libusb: warning [libusb_exit] application left some devices open

I’m not aware of LimeSDR support having been added to OpenBTS.

However, support has been added to OsmoTRX:

Since OsmoTRX is based on the OpenBTS transceiver and maintains backwards compatibility, you should be able to use it in place of their transceiver.

In theory he should be able to use it with the USRP driver, wich is what he’s doing. I would suggest using the official USRP-Photos driver instead of OpenUSRP.

Yes, but the transceiver software component must have support added for the hardware, as different platforms all have different latencies etc. and GSM is highly timing sensitive. See the June/July commits to OsmoTRX to see how LimeSDR support was added to this:

The same changes would need to be made to the OpenBTS transceiver, else OsmoTRX used in place of this and with the remainder of that stack.

Yes, thanks. I will check this when I receive my board.