I have managed to run my setup with "tx-sps 1" and "rx-sps 1" in osmo-trx.cfg, but now I have new issue: when everything running on the same machine - i can get phones registered, sms pass well, voice works but very poor... But, when I run osmo-trx-usrp1 and osmo-bts-trx on the another machine attached to the same network as machine with osmo-bsc and other software - phones are registered well, sms messages are going well, but there is no voice communication at all - calls are passed, but silence instead of voice.

The same story with nanoBTS connected to the same network - phones register well, sms messages going well, calls going well - but no voice at all. Silence.

----- Original Message -----
From: laforge@gnumonks.org
To: sergey.mayzus@uwcfx.com
Sent: 2019.01.11 22:50
Subject: Re: Re: OsmoTRX - osmo-trx-usrp-1 Aborted :: Assertion 'px != 0' failed

Hi Sergey,

On Thu, Jan 10, 2019 at 10:38:00PM +0000, Sergey Mayzus wrote:
> I copied file usrp1_fw.ihx from /usr/share/uhd/images/ to /usr/local/share/usrp
> /rev4 and renamed it to std.ihx but it does not fix the problem. Furthermore, I
> compiled and installed OpenBTS with configure option --with-usrp1
> --with-singledb. Tested it and it works properly. Recompiled osmo-trx with the
> same options --with-usrp1 --with-singledb but it does not fix the problem.
> Tried different USRP1 devices (with single borad and double boards). And again,
> the same problem.

thanks for your comprehensive testing.

> osmo-trx-usrp1: /usr/local/include/boost/smart_ptr/shared_ptr.hpp:424: T*
> boost::shared_ptr<T>::operator->() const [with T = usrp_standard_rx]: Assertion
> `px != 0' failed.

This indeed is caused by the no-longer-used skipRx, as you found out in one of
your later posts. I've removed skipRx in https://gerrit.osmocom.org/#/c/osmo-trx/+/12533/
which is pending review.

Using this patch, as well as a patch in osmo-bts-trx to increase the permitted
window of missing CLOCK indications...

-#define TRX_LOSS_FRAMES 400
+#define TRX_LOSS_FRAMES 1600

... I can get osmo-trx and osmo-bts-trx significantly further. However, after a few seconds I get a neverending flood of "chan 0 dumping STALE burst in TRX->USRP interface (5:1410316 vs 6:1410316), retrans=0" messages.

So still not working, but at least a step closer to it, I hope.

--
- Harald Welte <laforge@gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)