Project

General

Profile

Software Getting Started » History » Version 18

tsaitgaist, 02/19/2016 10:49 PM
add libosmocore

1 1
== OsmocomBB Getting Started Guide ==
2
3
This page will describe how to compile the firmware, the host utilities and how to use them.
4 10
If you haven't do so already, checkout [wiki:PreliminaryRequirements]
5 1
6
=== Compiling osmocomBB ===
7
osmocomBB consists out of software that is intended to be run on the phone (target) and the host system.
8
9 6 steve-m
==== Dependencies for the host ====
10 1
11 18 tsaitgaist
osmocomBB requires GNU autoconf, automake, libtool, pkg-config, make and GCC to compile.
12
You will also need to use git to access and update the sources.
13
The name of these packages depend on the distribution used.
14 1
For Debian the package names are:
15
{{{
16
sudo aptitude install libtool shtool autoconf git-core pkg-config make gcc
17
}}}
18 18 tsaitgaist
19
For osmocomBB, as for several other osmocom projects, you will also need [wiki:libosmocore].
20
21 1
22 9
==== Dependencies for the target ====
23 1
24 15 tsaitgaist
To compile osmocomBB or SIMtrace for the target we need a GNU [wiki:toolchain] for ARM.
25 13
26 2
==== Getting and updating the source ====
27 1
{{{
28
git clone git://git.osmocom.org/osmocom-bb.git
29 2
}}}
30
31
{{{
32 8
$ cd osmocom-bb
33 1
$ git pull --rebase
34 9
}}}
35
36
==== Verify the `PATH` environment variable ====
37
38
Please ensure that the cross-compiler is available in your `PATH`, for example by adding the following command to your shell's startup script (e.g. `.bashrc`) or typing it in the terminal you use to build:
39
40
{{{
41
export $PATH:$HOME/install/gnuarm-3.4.3/bin
42 2
}}}
43
44 11
Or on Ubuntu you might want to try:
45
46
{{{
47
export PATH=$PATH:$HOME/install/gnuarm-3.4.3/bin
48
}}}
49
50 12
(presuming it's in your home directory, if you have changed to root it probably wont be :))
51 2
==== Building the source ====
52
Compiling both the target and the host code will happen with the following command. It assumes that the '''arm-elf-gcc'''
53
is inside the current path.
54
55
{{{
56
$ cd src
57
$ make
58
}}}
59 1
60 4
If your GCC binary that produces ARM code is not called '''arm-elf-gcc''' you will need to invoke the following statement
61
and provide the basename of the toolchain with the ending '''-'''.
62 2
63
{{{
64
$ cd src
65
$ make -e CROSS_TOOL_PREFIX=arm-OTHER_NAME-
66 1
}}}
67 4
68
If no error has occured you will have the firmware binaries in ''src/target/firmware/board/compal_e88/*.bin'' that can be
69
used with the Motorola C123. You also have the binaries to run on your host in ''src/host/osmocon/osmocon'', in 
70
''src/host/layer23/src/misc'' and ''layer23/src/mobile''.
71 5
72
73
=== Running osmocomBB ===
74
The original bootloader of Compal and others are built in a way to load code via the serial interface. The [wiki:osmocon]
75
utility implements this protocol and can upload the firmware. Please the [wiki:osmocon] for the details of how to use
76
it properly.
77
78
After the firmware has been loaded the [wiki:osmocon] application will print the output of the serial console
79
and it provides a unix domain socket that another layer of software can connect to. In the case of osmocomBB
80 16
this higher layer software is called [wiki:ccch_scan] and is actually a group of binaries providing different functionality. Please
81
see [wiki:ccch_scan] for the details.
Add picture from clipboard (Maximum size: 48.8 MB)