Crash of UmTRX transceiver with dual TRX

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/UmTRX@lists.osmocom.org/.

Thomas Tsou tom at tsou.cc
Mon Jul 8 13:58:38 UTC 2013


On Mon, Jul 8, 2013 at 3:33 PM, Andreas Eversberg <andreas at eversberg.eu> wrote:
> Andreas Eversberg wrote:
>> just made osmo-bts ignore that. now i can provision both trx with
>> similar setting, except slot type and and ARFCN. it seems to work now,
>> but i get no rf power on second trx. i use ARFCN and 869 and 877.
>>
> i do also get no reception from the phone at second trx (late
> assignment, my tester showed me power on TS0 uplink). seems that rx and
> tx does not work for some reason.

If the slots aren't enabled, then both uplink and downlink will be
disabled. This patch should cause Tx slot setting to be ignored and
will send whatever core submits. We need the slot setting to set the
TSC / RACH correlation, so Rx is not as simple.

> also i found that the transceiver leaks about 2 megabytes every second.
> after some minutes my test machine runs out of mem space.

Should be resolved in the same patch.

  Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Transceiver52M-Disable-dynamic-filler-table-setting-.patch
Type: application/octet-stream
Size: 1675 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/umtrx/attachments/20130708/aebe372f/attachment.obj>


More information about the UmTRX mailing list