OsmocomBB MS-side GSM Protocol stack (L1, L2, L3) including firmware https://osmocom.org/projects/baseband
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
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
|5 months ago|
|.gitignore||5 years ago|
|README||4 years ago|
|app_common.py||12 months ago|
|burst_fwd.py||12 months ago|
|burst_gen.py||12 months ago|
|burst_send.py||12 months ago|
|clck_gen.py||12 months ago|
|codec.py||12 months ago|
|ctrl_cmd.py||12 months ago|
|ctrl_if.py||12 months ago|
|ctrl_if_trx.py||5 months ago|
|data_dump.py||12 months ago|
|data_if.py||12 months ago|
|data_msg.py||12 months ago|
|fake_pm.py||12 months ago|
|fake_trx.py||5 months ago|
|gsm_shared.py||12 months ago|
|rand_burst_gen.py||12 months ago|
|test_codec.py||12 months ago|
|test_data_dump.py||12 months ago|
|test_data_msg.py||12 months ago|
|transceiver.py||5 months ago|
|trx_list.py||12 months ago|
|trx_sniff.py||12 months ago|
|trxd_proto.py||12 months ago|
|udp_link.py||12 months ago|
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.