osmocom-bb/src/target/trx_toolkit
Vadim Yanitskiy 95025a2389 trx_toolkit: use 'TRXC' and 'TRXD' in logging messages
One can confuse TRX control interface with libosmoctrl's one.
TRX toolkit is not using libosmoctrl, and will never do. But,
in order to avoid this confusion, and potential confusion of
DATA interface, let's call them 'TRXC' and 'TRXD' in logging.

Change-Id: I67b1e850094cf8e279777c45c7544886be42a009
2019-01-14 23:52:31 +00:00
..
.gitignore Rename 'fake_trx' to 'trx_toolkit' 2018-03-13 02:10:02 +07:00
README trx_toolkit: use 'TRXC' and 'TRXD' in logging messages 2019-01-14 23:52:31 +00:00
app_common.py trx_toolkit: merge copyright.py into app_common.py 2018-12-08 02:10:50 +07:00
burst_fwd.py trx_toolkit/burst_fwd.py: fix trx_list cross-reference 2019-01-13 15:39:27 +07:00
burst_gen.py trx_toolkit: merge copyright.py into app_common.py 2018-12-08 02:10:50 +07:00
burst_send.py trx_toolkit/burst_send.py: exit if DATA dump parsing failed 2018-12-16 07:14:11 +07:00
clck_gen.py trx_toolkit: fix missing / useless imports 2018-12-16 07:14:11 +07:00
ctrl_cmd.py trx_toolkit: use 'TRXC' and 'TRXD' in logging messages 2019-01-14 23:52:31 +00:00
ctrl_if.py trx_toolkit: use 'TRXC' and 'TRXD' in logging messages 2019-01-14 23:52:31 +00:00
ctrl_if_trx.py trx_toolkit/{ctrl,data}_if.py: add init log message 2019-01-14 23:52:31 +00:00
data_dump.py trx_toolkit: use generic logging module instead of print() 2018-12-07 05:36:20 +07:00
data_if.py trx_toolkit: use 'TRXC' and 'TRXD' in logging messages 2019-01-14 23:52:31 +00:00
data_msg.py trx_toolkit/data_msg.py: add optional legacy message coding flag 2018-12-18 05:47:11 +07:00
fake_pm.py trx_toolkit/fake_trx.py: refactor global class hierarchy 2018-12-18 05:47:11 +07:00
fake_trx.py trx_toolkit/fake_trx.py: enrich TRX logging messages 2019-01-14 23:52:31 +00:00
gsm_shared.py Rename 'fake_trx' to 'trx_toolkit' 2018-03-13 02:10:02 +07:00
rand_burst_gen.py Rename 'fake_trx' to 'trx_toolkit' 2018-03-13 02:10:02 +07:00
transceiver.py trx_toolkit: use 'TRXC' and 'TRXD' in logging messages 2019-01-14 23:52:31 +00:00
trx_list.py trx_toolkit/transceiver.py: add support for child transceivers 2019-01-13 16:05:27 +07:00
trx_sniff.py trx_toolkit: fix missing / useless imports 2018-12-16 07:14:11 +07:00
udp_link.py trx_toolkit: Add cmdline arg to set bind addr 2018-04-04 17:14:26 +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. Currently
    only a single MS may work with a single BTS.

  - 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.