OpenBSC running on an Odroid-XU

[John Baker]

Hi,

I have an Odroid-XU I have setup with Debian Wheezy and a USRP B200.
After building the UHD drivers from source, I followed the "network from
scratch" page. I also configured and built osmo-trx with the
--with-neon-vfpv4 option. Things are running OK, a whole lot better than
my attempt with OpenBTS actually. I"m able to connect to the network
with my Samsung S4 phone, but after an hour or so of the BTS running, I
get a UHD recieved time out error (see below). I wonder what could be
causing this? I have the B200 plugged into the USB 3.0 port, along with
external power.

Thanks in advance for any help.


***@odroid-wheezy:~# osmo-trx
linux; GNU C++ version 4.6.3; Boost_104900; UHD_003.007.002-94-ge56809a0

Config Settings
Log Level............... NOTICE
Device args.............
TRX Base Port........... 5700
TRX Address............. 127.0.0.1
Channels................ 1
Samples-per-Symbol...... 1
External Reference...... Disabled
C0 Filler Table......... Disabled
Diversity............... Disabled
Tuning offset........... 0

-- Loading firmware image:
/usr/local/share/uhd/images/usrp_b200_fw.hex... done
-- Loading FPGA image: /usr/local/share/uhd/images/usrp_b200_fpga.bin...
done
-- Operating over USB 3.
-- Detecting internal GPSDO.... No GPSDO found
-- not found
-- Initialize CODEC control...
-- Initialize Radio control...
-- Performing register loopback test... pass
-- Performing CODEC loopback test... pass
-- Asking for clock rate 32.000000 MHz
-- Actually got clock rate 32.000000 MHz
-- Performing timer loopback test... pass
-- Asking for clock rate 26.000000 MHz
-- Actually got clock rate 26.000000 MHz
-- Performing timer loopback test... pass
-- Setting B200 1 SPS
-- Transceiver active with 1 channel(s)
ALERT 3030074464 23:06:10.4 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:10.5 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:10.6 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:10.7 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:10.8 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:10.9 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:11.0 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:11.1 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:11.2 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:11.3 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:11.4 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:11.5 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:11.6 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:11.7 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:11.9 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:12.0 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:12.1 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:12.2 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:12.3 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:12.4 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:12.5 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:12.6 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:12.7 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:12.8 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:12.9 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:13.0 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:13.1 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:13.2 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:13.3 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:13.4 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:13.5 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:13.6 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:13.7 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:13.8 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:13.9 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:14.0 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:14.1 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
ALERT 3030074464 23:06:14.2 UHDDevice.cpp:832:check_rx_md_err: UHD:
Receive timed out
terminate called after throwing an instance of 'uhd::assertion_error'
what(): AssertionError: accum_timeout < _timeout
in uint64_t radio_ctrl_core_3000_impl::wait_for_ack(bool)
at /root/uhd/host/lib/usrp/cores/radio_ctrl_core_3000.cpp:232

[Tom Tsou]

I have an Odroid-XU I have setup with Debian Wheezy and a USRP B200. After
building the UHD drivers from source, I followed the "network from scratch"
page. I also configured and built osmo-trx with the --with-neon-vfpv4
option. Things are running OK, a whole lot better than my attempt with
OpenBTS actually. I"m able to connect to the network with my Samsung S4
phone, but after an hour or so of the BTS running, I get a UHD recieved time
out error (see below). I wonder what could be causing this? I have the B200
plugged into the USB 3.0 port, along with external power.

Is there any any specific activity that occurs at the time? or is the
system completely idle during the timeout?

-TT