вт, 28 мар. 2023 г. в 23:58, Keith E. Fleming <[email protected]>: > I have been trying to get osmo-trx-uhd to work with my Ettus B200. Where it > gets stuck is: > > ┌──(root💀kali)-[~/osmo/src/osmo-trx] > └─# osmo-trx-uhd -C ./doc/examples/osmo-trx-uhd/osmo-trx-uhd.cfg > Tue Mar 28 12:39:48 2023 DLGLOBAL <0008> cpu_sched_vty.c:471 Setting SCHED_RR > priority 18 > Tue Mar 28 12:39:48 2023 DLGLOBAL <0008> telnet_interface.c:88 Available via > telnet 127.0.0.1 4237 > Tue Mar 28 12:39:48 2023 DLCTRL <000f> control_if.c:1014 CTRL at 127.0.0.1 > 4236 > [INFO] [UHD] linux; GNU C++ version 12.2.0; Boost_107400; UHD_4.3.0.0+ds1-4+b2 > Tue Mar 28 12:40:06 2023 DMAIN <0000> osmo-trx.cpp:607 -- Transceiver active > with 1 channel(s) > Tue Mar 28 12:40:06 2023 DLSTATS <0011> stats.c:169 Stats timer > expire_count=4: We missed 3 timers > Tue Mar 28 12:40:06 2023 DLGLOBAL <0008> rate_ctr.c:350 Stats timer > expire_count=17: We missed 16 timers
Why do you think it gets stuck? Does osmo-bts-trx complain that osmo-trx-uhd is not responding? The line "Transceiver active with 1 channel(s)" tells that the SDR device is initialized and ready to be used, I see nothing suspicious here. > That line in red, above, should be followed by: > > [INFO] [B200] Detected Device: B200 > [INFO] [B200] Operating over USB 3. > [INFO] [B200] Initialize CODEC control... > [INFO] [B200] Initialize Radio control... > ...................etc.. Well, you may need to increase logging verbosity to see these messages. The default logging policy is 'set-all notice', so if you do 'logging level set-all info' in the config file you'll likely see these messages (and many more). Best regards, Vadim.
