osmocom-bb/src/target/trx_toolkit
Vadim Yanitskiy 15247989f5 trx_toolkit: do not auto power on/off child MS Transceivers
By default, powering on/off a parent transceiver (child_idx=0) will
automatically power on/off its child transceivers (if any).  This
behavior is desirable for the BTS, but not for the MS Transceivers.

Additional MS Transceivers are going to be used by ttcn3-bts-test
for spawning multiple DCCH components in parallel.  We don't want
situations when one component powers off transceivers of the other
DCCH components - they must be independent.

Change-Id: I0cd6bac616273bed0e246ad48edc44fff484c589
2022-07-26 23:48:19 +07:00
..
.gitignore Rename 'fake_trx' to 'trx_toolkit' 2018-03-13 02:10:02 +07:00
README trx_toolkit/README: update fake_trx.py description 2019-01-14 23:52:31 +00:00
app_common.py treewide: remove FSF address 2021-12-14 12:52:04 +00:00
burst_fwd.py treewide: remove FSF address 2021-12-14 12:52:04 +00:00
burst_gen.py treewide: remove FSF address 2021-12-14 12:52:04 +00:00
burst_send.py treewide: remove FSF address 2021-12-14 12:52:04 +00:00
clck_gen.py treewide: remove FSF address 2021-12-14 12:52:04 +00:00
codec.py treewide: remove FSF address 2021-12-14 12:52:04 +00:00
ctrl_cmd.py treewide: remove FSF address 2021-12-14 12:52:04 +00:00
ctrl_if.py treewide: remove FSF address 2021-12-14 12:52:04 +00:00
ctrl_if_trx.py trx_toolkit: simplify Transceiver.power_event_handler() 2022-07-26 23:48:19 +07:00
data_dump.py treewide: remove FSF address 2021-12-14 12:52:04 +00:00
data_if.py treewide: remove FSF address 2021-12-14 12:52:04 +00:00
data_msg.py treewide: remove FSF address 2021-12-14 12:52:04 +00:00
fake_pm.py treewide: remove FSF address 2021-12-14 12:52:04 +00:00
fake_trx.py trx_toolkit: do not auto power on/off child MS Transceivers 2022-07-26 23:48:19 +07:00
gsm_shared.py treewide: remove FSF address 2021-12-14 12:52:04 +00:00
rand_burst_gen.py treewide: remove FSF address 2021-12-14 12:52:04 +00:00
test_codec.py treewide: remove FSF address 2021-12-14 12:52:04 +00:00
test_data_dump.py treewide: remove FSF address 2021-12-14 12:52:04 +00:00
test_data_msg.py treewide: remove FSF address 2021-12-14 12:52:04 +00:00
transceiver.py trx_toolkit: do not auto power on/off child MS Transceivers 2022-07-26 23:48:19 +07:00
trx_list.py treewide: remove FSF address 2021-12-14 12:52:04 +00:00
trx_sniff.py treewide: remove FSF address 2021-12-14 12:52:04 +00:00
trxd_proto.py treewide: remove FSF address 2021-12-14 12:52:04 +00:00
udp_link.py treewide: remove FSF address 2021-12-14 12:52:04 +00:00

README

TRX toolkit is a set of tools intended for hacking and debugging
a TRX interface between both transceiver and L1 software, and
emulating a virtual Um-interface between OsmocomBB and OsmoBTS.

Brief description of available applications:

  - fake_trx.py - main application, that allows to connect both
    OsmocomBB and OsmoBTS without actual RF hardware. It's also
    possible to emulate more than two transceivers, so multiple
    MS and/or BTS instances can be connected.

  - clck_gen.py - a peripheral tool aimed to emulate TDMA frame
    clock generator. Could be used for testing and clock
    synchronization of multiple applications. It should be noted,
    that one relays on generic system timer (via Python), so
    a random clock jitter takes place.

  - ctrl_cmd.py - another peripheral tool, which could be used
    for sending CTRL commands directly in manual mode, and also
    for application fuzzing.

  - burst_gen.py - a tool for sending GSM bursts either to L1
    (OsmoBTS or OsmocomBB) or to TRX (OsmoTRX and GR-GSM TRX).
    Currently it is only possible to generate random bursts of
    different types: NB, FB, SB, AB.

  - burst_send.py - a tool for sending existing bursts from a
    capture file either to L1 (OsmoBTS or OsmocomBB) or to
    TRX (e.g. OsmoTRX or GR-GSM TRX).

  - trx_sniff.py - Scapy-based TRX protocol sniffer. Allows one
    to observe a single connection between TRX and L1, and vice
    versa. Also provides some capabilities for filtering bursts
    by direction, frame and timeslot numbers, and for recording
    captured messages to a binary file.

Please note that TRX toolkit is not using libosmocore's CTRL
interface, so 'CTRL' in scope of this code base actually means
control interface of TRX or control protocol. In order to avoid
possible confusion, we use 'TRXC' and 'TRXD' in logging.