Project

General

Profile

Bug #1963

multiplexing trx is not working

Added by msuraev over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
03/03/2017
Due date:
% Done:

0%

Spec Reference:

Description

With latest osmo-trx 2dee3e996e777b67aa3185f7456c041765f0d71f I've got following error when using multi-trx:

sudo ./Transceiver52M/osmo-trx -l INFO -m -c 2 -x
linux; GNU C++ version 6.2.0 20161005; Boost_106100; UHD_003.009.006-release

opening configuration table from path :memory:
Config Settings
   Log Level............... INFO
   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
   Diversity............... Disabled
   Tuning offset........... 0
   Tuning offset........... 0
   RSSI to dBm offset...... 0
   Swap channels........... 0

INFO 140560941390720 13:11:22.1 UHDDevice.cpp:788:open: Using discovered UHD device type=b200,name=MyB210,serial=30AC26A,product=B210
-- 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'.
INFO 140560941390720 13:11:24.2 UHDDevice.cpp:745:parse_dev_type: Using USRP1 type transmit window for B-Series Device B210
-- Asking for clock rate 3.200000 MHz...
UHD Warning:            
    The requested master_clock_rate 3.200000 MHz exceeds bounds imposed by UHD.
    The master_clock_rate has been forced to 5.000000 MHz.

-- Actually got clock rate 5.000000 MHz.
-- Performing timer loopback test... pass
-- Performing timer loopback test... pass
ALERT 140560941390720 13:11:25.4 UHDDevice.cpp:548:set_master_clk: Failed to set master clock rate
ALERT 140560941390720 13:11:25.4 UHDDevice.cpp:548:set_master_clk: Failed to set master clock rate
ALERT 140560941390720 13:11:25.4 UHDDevice.cpp:549:set_master_clk: Requested clock rate 3.2e+06
ALERT 140560941390720 13:11:25.4 UHDDevice.cpp:549:set_master_clk: Requested clock rate 3.2e+06
ALERT 140560941390720 13:11:25.4 UHDDevice.cpp:550:set_master_clk: Actual clock rate 5e+06
ALERT 140560941390720 13:11:25.4 UHDDevice.cpp:550:set_master_clk: Actual clock rate 5e+06
ALERT 140560941390720 13:11:25.4 osmo-trx.cpp:530:main: Failed to create radio device

ALERT 140560941390720 13:11:25.4 osmo-trx.cpp:530:main: Failed to create radio device
Shutting down transceiver...


Related issues

Blocks OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxClosed03/11/2016

History

#1 Updated by msuraev over 2 years ago

  • Blocks Feature #1648: Verify Multi-TRX support for osmo-bts-trx added

#2 Updated by msuraev over 2 years ago

  • Status changed from New to Resolved

Fixed by a93f789e50e9fc4fd7bcf7d7bc6e2cd31cc1e042 in osmo-trx.

#3 Updated by laforge over 2 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)