Project

General

Profile

OsmocomBB Firmware » History » Version 7

jolly, 02/19/2016 10:48 PM
Add "menu" and "EMI" applications.

1 1
2
[[PageOutline]]
3
4 2 nion
= Background =
5
The OsmocomBB source code comes with several applications for various purposes.
6
Those applications can be devided into two separate classes, applications:
7
 * running on the baseband chip of the phone
8
 * running on a PC, communicating with the baseband firmware over serial
9 1
10 2 nion
Applications running on the PC can further be partitioned into:
11
 * Firmware management software (loading, flashing, ...)
12 3 nion
 * GSM Layer 2/3 applications
13 1
14 2 nion
The following will provide you a rough overview of the most commonly used software pieces.
15 1
16
17
18 2 nion
= Baseband firmware =
19
20
Binary location: src/target/firmware/board/*/*.bin
21
Source locations: src/target/firmware/, particularly apps and layer1
22
23 1
== layer1 ==
24 5 nion
[wiki:layer1.bin] is a simple GSM layer 1 proxy, communicating over the [wiki:L1A_L23_Interface].
25 1
26
This allows you to run a full-blown GSM implementation on your host machine, communicating through the phones radio interface.
27 5 nion
28
== loader ==
29
[wiki:loader.bin] is our flash loader, dumper and second stage bootloader
30
31 1
== l1test ==
32
33
Layer 1 development application.
34
35
This application does what layer1 does, but automatically tunes to the strongest ARFCN it can find.
36
37
It can be used for stand-alone-testing of the phones radio.
38
39
== loader ==
40
41
Our [wiki:Bootloader], available in various build configurations.
42
43
== compal_dsp_dump ==
44
45
Application for dumping the contents of the DSP in the Calypso chip.
46
47
== compal_dumper ==
48
49
The old compal device dumper. Use [wiki:Bootloader] instead once it is available.
50
51
== hello_world ==
52
53
The initial obligatory "Hello, world!" application.
54
55
Currently, this does more than say hello. Intended as a template for new applications.
56 2 nion
57 7 jolly
== menu ==
58
59
Boot menu application to select and load apps that are stored in flash memory. See [wiki:flashing_new].
60
61 2 nion
== rssi ==
62
63
The [blog:rssi-firmware] can be used to monitor the received signal indication (RSSI) of ARFCNs or the entire spectrum.
64 7 jolly
65
== EMI ==
66
67
The EMI (electro magnetic interference) simulator application can be used to generate RF interference caused by GSM networks an mobile station. See [wiki:emi-firmware].
68 2 nion
69
70
71
= Firmware management software =
72
Location (source and binary): src/host/osmocon
73
74
== osmocon ==
75
[wiki:osmocon] is a console tool for interfacing our baseband firmware on the phone with applications on the host PC.
76 4 nion
77 2 nion
It is responsible for downloading a baseband firmware or bootloader into the phone and relay communication between Layer 3 applications and baseband firmwares over serial.
78
79 1
== osmoload ==
80 4 nion
[wiki:osmoload] is used to write, dump and examine flash memory of supported phones.
81
82 2 nion
You will need this program for example if you intent [wiki:flashing] an application to the phone (the software is usually loaded into RAM).
83 1
84 3 nion
== calypso_pll == 
85
The [wiki:calypso_pll] tool can be used to calculate Calypso DPLL multiplier+divider.
86 1
87 3 nion
== rita_pll ==
88
The [wiki:rita_pll] tool can be used to calculate the Rita PLL multiplier/divider.
89 1
90 3 nion
91
= GSM Layer 2/3 applications = 
92 2 nion
Location (source and binary): src/host/layer23/*
93
94 3 nion
Layer 3 applications implement various functionality based on GSM Layer 3 in combination with Layer 2 (LAPDm).
95 2 nion
96
== mobile ==
97 1
[wiki:mobile] is the most sophisticated OsmocomBB application so far.
98 4 nion
99 2 nion
It implements most of the behavior of a regular GSM telephone, but is extended in many ways with features interesting to researchers.
100
101
== cell_log ==
102 1
The cell_log application scans through valid available carrier frequencies, attempts to sync to them and dumps information gathered from the BCCH.
103 4 nion
104 2 nion
It is usually used to create a list of used ARFCNs and information such as their reception levels, MNC, MCC, and System Information.
105
106
== ccch_scan ==
107
The ccch_scan application can sync to a carrier ARFCN and logs power measurement and CCCH information (paging requests and Immediate Assignments).
108
109
== bcch_scan ==
110
bcch_scan is basically a predecessor of cell_log and logs information as observed on the BCCH (System Information).
111
112
== cbch_sniff ==
113
cbch_sniff dumps cell broadcast channel information such as, e.g., GPS location of the cell.
Add picture from clipboard (Maximum size: 48.8 MB)