Hi.
While testing latest osmo-trx in multi-trx mode I've noticed following errors:
sudo chrt -r 99 ./Transceiver52M/osmo-trx -c 2 -x -m
linux; GNU C++ version 6.2.0 20161005; Boost_106100; UHD_003.009.006-release
opening configuration table from path :memory:
Info: SSE3 support compiled in and supported by CPU
Info: SSE4.1 support compiled in and supported by CPU
Config Settings
Log Level............... NOTICE
Device args.............
TRX Base Port........... 5700
TRX Address............. 127.0.0.1
Channels................ 2
Tx Samples-per-Symbol... 4
Rx Samples-per-Symbol... 4
EDGE support............ Disabled
Reference............... External
C0 Filler Table......... Disabled
Multi-Carrier........... Enabled
Tuning offset........... 0
RSSI to dBm offset...... 0
Swap channels........... 0
-- Detected Device: B210
-- Operating over USB 2.
-- Initialize CODEC control...
-- Initialize Radio control...
-- Performing register loopback test... pass
-- Performing register loopback test... pass
-- Performing CODEC loopback test... pass
-- Performing CODEC loopback test... pass
-- Asking for clock rate 16.000000 MHz...
-- Actually got clock rate 16.000000 MHz.
-- Performing timer loopback test... pass
-- Performing timer loopback test... pass
-- Setting master clock rate selection to 'automatic'.
-- Asking for clock rate 51.200000 MHz...
-- Actually got clock rate 51.200000 MHz.
-- Performing timer loopback test... pass
-- Performing timer loopback test... pass
-- Setting B200/B210 4 SPS Multi-ARFCN
-- Transceiver active with 2 channel(s)
NOTICE 139729930782464 12:59:47.8 Transceiver.cpp:794:driveControl: Changing TSC from
0 to 7
NOTICE 139729930782464 12:59:47.8 Transceiver.cpp:243:start: Starting the transceiver
NOTICE 139729930749696 12:59:48.0 Transceiver.cpp:794:driveControl: Changing TSC from
7 to 7
ALERT 139729930749696 12:59:48.0 UHDDevice.cpp:611:setRxGain: Requested non-existent
channel 1
ALERT 139729930749696 12:59:48.0 UHDDevice.cpp:611:setRxGain: Requested non-existent
channel 1
...
This doesn't seem to have any visible effect but still makes me wonder what's
going
on here? If this is indeed critical error than what exactly is broken and how to test
it? If it's smth which could be safely ignored than why it's reported with alert
priority?
Any help clarifying it would be appreciated.
--
Max Suraev <msuraev(a)sysmocom.de>
http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte