Hi.
I've got following problem while trying to make osmotrx work in multitrx setting on USRP B210: sudo chrt 20 ./Transceiver52M/osmo-trx -c 2 sudo chrt 15 ./src/osmo-bts-trx/osmo-bts-trx -t 2 -c ~/.config/osmocom/osmo-bts-mtrx.cfg -d DRTP:DCC:DRSL:DOML:DL1C:DTRX
The bts quits from trx_if.c after checking "if (tcm->critical) {...". The command sequence seems to be the same for both phy0.0 and phy0.1 However 0.0 one accepts SETTSC command and 0.1 rejects it: trx_if.c:380 transceiver (phy0.1) rejected TRX command with response: 'RSP SETTSC 1 7'
So far I fail to see where this difference comes from.
Full log: <0001> oml.c:1249 Initializing OML attribute definitions <000b> trx_if.c:560 Open transceiver for phy0.0 <000b> trx_if.c:222 Adding new control 'CMD POWEROFF' <000b> trx_if.c:169 Sending control 'CMD POWEROFF' to phy0.0 <000b> trx_if.c:560 Open transceiver for phy0.1 <000b> trx_if.c:348 Response message: 'RSP POWEROFF 0' <0001> oml.c:547 Ignoring T200[0] (150 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:547 Ignoring T200[1] (180 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:547 Ignoring T200[2] (180 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:547 Ignoring T200[3] (1680 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:547 Ignoring T200[4] (520 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:547 Ignoring T200[5] (165 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:547 Ignoring T200[6] (1680 ms) as sent by BSC due to suspected LAPDm bug! <000b> trx_if.c:222 Adding new control 'CMD POWEROFF' <000b> trx_if.c:169 Sending control 'CMD POWEROFF' to phy0.0 <000b> trx_if.c:348 Response message: 'RSP POWEROFF 0' <0001> oml.c:884 ADM state already was Unlocked <000b> trx_if.c:222 Adding new control 'CMD RXTUNE 1783400' <000b> trx_if.c:169 Sending control 'CMD RXTUNE 1783400' to phy0.0 <000b> trx_if.c:222 Adding new control 'CMD TXTUNE 1878400' <000b> trx_if.c:222 Adding new control 'CMD SETTSC 7' <000b> trx_if.c:222 Adding new control 'CMD POWERON' <000b> trx_if.c:222 Adding new control 'CMD SETRXGAIN 1' <000b> trx_if.c:222 Adding new control 'CMD SETPOWER 0' <000b> trx_if.c:222 Adding new control 'CMD SETSLOT 0 4' <0005> paging.c:545 Paging: BS_AG_BLKS_RES = 0 != 1 not fully supported <000b> trx_if.c:348 Response message: 'RSP RXTUNE 0 1783400' <000b> trx_if.c:169 Sending control 'CMD TXTUNE 1878400' to phy0.0 <000b> trx_if.c:348 Response message: 'RSP TXTUNE 0 1878400' <000b> trx_if.c:169 Sending control 'CMD SETTSC 7' to phy0.0 <000b> trx_if.c:348 Response message: 'RSP SETTSC 0 7' <000b> trx_if.c:169 Sending control 'CMD POWERON' to phy0.0 <0005> paging.c:545 Paging: BS_AG_BLKS_RES = 0 != 1 not fully supported <000b> trx_if.c:222 Adding new control 'CMD SETSLOT 1 7' <000b> trx_if.c:222 Adding new control 'CMD SETSLOT 2 13' <000b> trx_if.c:222 Adding new control 'CMD SETSLOT 3 13' <000b> trx_if.c:222 Adding new control 'CMD SETSLOT 4 13' <000b> trx_if.c:348 Response message: 'RSP POWERON 0' <000b> trx_if.c:169 Sending control 'CMD SETRXGAIN 1' to phy0.0 <000b> trx_if.c:348 Response message: 'RSP SETRXGAIN 0 1' <000b> trx_if.c:169 Sending control 'CMD SETPOWER 0' to phy0.0 <000b> trx_if.c:348 Response message: 'RSP SETPOWER 0 0' <000b> trx_if.c:169 Sending control 'CMD SETSLOT 0 4' to phy0.0 <000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 0 4' <000b> trx_if.c:169 Sending control 'CMD SETSLOT 1 7' to phy0.0 <000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 1 7' <000b> trx_if.c:169 Sending control 'CMD SETSLOT 2 13' to phy0.0 <000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 2 13' <000b> trx_if.c:169 Sending control 'CMD SETSLOT 3 13' to phy0.0 <000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 3 13' <000b> trx_if.c:169 Sending control 'CMD SETSLOT 4 13' to phy0.0 <000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 4 13' <000b> trx_if.c:222 Adding new control 'CMD SETSLOT 5 13' <000b> trx_if.c:169 Sending control 'CMD SETSLOT 5 13' to phy0.0 <000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 5 13' <000b> trx_if.c:222 Adding new control 'CMD SETSLOT 6 13' <000b> trx_if.c:169 Sending control 'CMD SETSLOT 6 13' to phy0.0 <000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 6 13' <000b> trx_if.c:222 Adding new control 'CMD SETSLOT 7 13' <000b> trx_if.c:169 Sending control 'CMD SETSLOT 7 13' to phy0.0 <000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 7 13' <0001> oml.c:884 ADM state already was Unlocked <000b> trx_if.c:222 Adding new control 'CMD RXTUNE 1783800' <000b> trx_if.c:169 Sending control 'CMD RXTUNE 1783800' to phy0.1 <000b> trx_if.c:222 Adding new control 'CMD TXTUNE 1878800' <000b> trx_if.c:222 Adding new control 'CMD SETTSC 7' <000b> trx_if.c:222 Adding new control 'CMD SETSLOT 0 7' <000b> trx_if.c:348 Response message: 'RSP RXTUNE 0 1783800' <000b> trx_if.c:169 Sending control 'CMD TXTUNE 1878800' to phy0.1 <000b> trx_if.c:348 Response message: 'RSP TXTUNE 0 1878800' <000b> trx_if.c:169 Sending control 'CMD SETTSC 7' to phy0.1 <000b> trx_if.c:348 Response message: 'RSP SETTSC 1 7' <000b> trx_if.c:380 transceiver (phy0.1) rejected TRX command with response: 'RSP SETTSC 1 7' <0001> bts.c:203 Shutting down BTS 0, Reason TRX-CTRL-MSG: CRITICAL <000b> trx_if.c:222 Adding new control 'CMD POWEROFF' <000b> trx_if.c:169 Sending control 'CMD POWEROFF' to phy0.0 <000b> trx_if.c:348 Response message: 'RSP POWEROFF 0' <0001> oml.c:547 Ignoring T200[0] (150 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:547 Ignoring T200[1] (180 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:547 Ignoring T200[2] (180 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:547 Ignoring T200[3] (1680 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:547 Ignoring T200[4] (520 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:547 Ignoring T200[5] (165 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:547 Ignoring T200[6] (1680 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:884 ADM state already was Unlocked <000b> trx_if.c:222 Adding new control 'CMD POWERON' <000b> trx_if.c:169 Sending control 'CMD POWERON' to phy0.0 <000b> trx_if.c:222 Adding new control 'CMD SETRXGAIN 1' <000b> trx_if.c:222 Adding new control 'CMD SETPOWER 0' <000b> trx_if.c:222 Adding new control 'CMD SETSLOT 0 4' <000b> trx_if.c:222 Adding new control 'CMD SETSLOT 1 7' <000b> trx_if.c:222 Adding new control 'CMD SETSLOT 2 13' <000b> trx_if.c:222 Adding new control 'CMD SETSLOT 3 13' <000b> trx_if.c:222 Adding new control 'CMD SETSLOT 4 13' <000b> trx_if.c:222 Adding new control 'CMD SETSLOT 5 13' <000b> trx_if.c:222 Adding new control 'CMD SETSLOT 6 13' <000b> trx_if.c:222 Adding new control 'CMD SETSLOT 7 13' <0001> oml.c:884 ADM state already was Unlocked <0001> oml.c:884 ADM state already was Unlocked <0001> oml.c:884 ADM state already was Unlocked <0001> oml.c:884 ADM state already was Unlocked <000b> trx_if.c:348 Response message: 'RSP POWERON 0' <000b> trx_if.c:169 Sending control 'CMD SETRXGAIN 1' to phy0.0 <000b> trx_if.c:348 Response message: 'RSP SETRXGAIN 0 1' <000b> trx_if.c:169 Sending control 'CMD SETPOWER 0' to phy0.0 <000b> trx_if.c:348 Response message: 'RSP SETPOWER 0 0' <000b> trx_if.c:169 Sending control 'CMD SETSLOT 0 4' to phy0.0 <000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 0 4' <000b> trx_if.c:169 Sending control 'CMD SETSLOT 1 7' to phy0.0 <000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 1 7' <000b> trx_if.c:169 Sending control 'CMD SETSLOT 2 13' to phy0.0 <000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 2 13' <000b> trx_if.c:169 Sending control 'CMD SETSLOT 3 13' to phy0.0 <000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 3 13' <000b> trx_if.c:169 Sending control 'CMD SETSLOT 4 13' to phy0.0 <000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 4 13' <000b> trx_if.c:169 Sending control 'CMD SETSLOT 5 13' to phy0.0 <000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 5 13' <000b> trx_if.c:169 Sending control 'CMD SETSLOT 6 13' to phy0.0 <000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 6 13' <000b> trx_if.c:169 Sending control 'CMD SETSLOT 7 13' to phy0.0 <000b> trx_if.c:348 Response message: 'RSP SETSLOT 0 7 13' <0001> oml.c:884 ADM state already was Unlocked <0001> oml.c:884 ADM state already was Unlocked <0001> oml.c:884 ADM state already was Unlocked <0001> oml.c:884 ADM state already was Unlocked <000b> trx_if.c:222 Adding new control 'CMD SETSLOT 0 7' <000b> trx_if.c:222 Adding new control 'CMD SETSLOT 1 1' <000b> trx_if.c:222 Adding new control 'CMD SETSLOT 2 1' <000b> trx_if.c:222 Adding new control 'CMD SETSLOT 3 1' <000b> trx_if.c:222 Adding new control 'CMD SETSLOT 4 1' <000b> trx_if.c:222 Adding new control 'CMD SETSLOT 5 1' <000b> trx_if.c:222 Adding new control 'CMD SETSLOT 6 1' <000b> trx_if.c:222 Adding new control 'CMD SETSLOT 7 1' <0001> oml.c:884 ADM state already was Unlocked <0001> oml.c:884 ADM state already was Unlocked <0001> oml.c:884 ADM state already was Unlocked <0001> oml.c:884 ADM state already was Unlocked <0001> oml.c:884 ADM state already was Unlocked <0001> oml.c:884 ADM state already was Unlocked <0001> oml.c:884 ADM state already was Unlocked <0001> oml.c:884 ADM state already was Unlocked <000b> trx_if.c:138 Clock indication: fn=999376 <000b> trx_if.c:470 TX burst tn=0 fn=999396 pwr=0 <000b> trx_if.c:470 TX burst tn=1 fn=999396 pwr=0 <000b> trx_if.c:470 TX burst tn=2 fn=999396 pwr=0 ...
Hi Max,
On Wed, Jun 22, 2016 at 7:29 AM, Max msuraev@sysmocom.de wrote:
I've got following problem while trying to make osmotrx work in multitrx setting on USRP B210: sudo chrt 20 ./Transceiver52M/osmo-trx -c 2 sudo chrt 15 ./src/osmo-bts-trx/osmo-bts-trx -t 2 -c ~/.config/osmocom/osmo-bts-mtrx.cfg -d DRTP:DCC:DRSL:DOML:DL1C:DTRX
The bts quits from trx_if.c after checking "if (tcm->critical) {...". The command sequence seems to be the same for both phy0.0 and phy0.1 However 0.0 one accepts SETTSC command and 0.1 rejects it: trx_if.c:380 transceiver (phy0.1) rejected TRX command with response: 'RSP SETTSC 1 7'
Please try the updated osmotrx master.
TSC rejection was based on legacy behavior where the SETTSC command would instantiate internal DSP resources, so the allowed timing of the command was restricted. That restriction no longer exists.
Note that OsmoTRX only supports one TSC value for all channels. SETTSC will only error if sent to a TRX channel other than 0 with a TSC value that differs from the internal TSC value.
-TT