Project

General

Profile

Osmocon » History » Version 8

Anonymous, 02/19/2016 10:49 PM
Rewrote main text.

1 2 laforge
[[PageOutline]]
2 6 laforge
= osmocon =
3 1 laforge
4 8 laforge
Osmocon is a console tool for our baseband implementation.
5
6
It is used to download a firmware or bootloader into the phone over the serial interface, which is currently implemented for the CompalE88 and the CompalE99.
7
8
After uploading a firmware, it turns into an HDLC mux/demux, allowing multichannel communication with the device.
9
10
The phones console is on one such channel and will be redirected to the terminal on which osmocom runs.
11
12
Several other HDLC channels are accessible by means of the following unix domain sockets:
13
 * /tmp/osmocom_l2 for the [wiki:L1A_L23_Interface]
14
 * /tmp/osmocon_loader for the [wiki:Bootloader]
15
16 1 laforge
17
== Usage ==
18
19
 * Connect your Compal phone to a serial port of your PC, using a [wiki:CalypsoSerialCable] (3.3V RS232 on 2.5mm headphone jack)
20 6 laforge
 * Start the osmocon program like this
21 1 laforge
{{{
22 6 laforge
$ ./osmocon -m c123xor -p /dev/ttyUSB0 /path/to/your/object_code.bin
23 1 laforge
}}}
24
 * Push the power-on button of your phone (short push, not like a regular phone boot!)
25
 * Observe the following output:
26
{{{
27
got 1 bytes from modem, data looks like: 04 
28
got 1 bytes from modem, data looks like: 81 
29
got 1 bytes from modem, data looks like: 1b 
30
got 1 bytes from modem, data looks like: f6 
31
got 1 bytes from modem, data looks like: 02 
32
got 1 bytes from modem, data looks like: 00 
33
got 1 bytes from modem, data looks like: 41 
34
got 1 bytes from modem, data looks like: 01 
35
got 1 bytes from modem, data looks like: 40 
36
Received PROMPT1 from phone, responding with CMD
37
got 1 bytes from modem, data looks like: 1b 
38
got 1 bytes from modem, data looks like: f6 
39
got 1 bytes from modem, data looks like: 02 
40
got 1 bytes from modem, data looks like: 00 
41
got 1 bytes from modem, data looks like: 41 
42
got 1 bytes from modem, data looks like: 02 
43
got 1 bytes from modem, data looks like: 43 
44
Received PROMPT2 from phone, starting download
45
got 1 bytes from modem, data looks like: 1b 
46
got 1 bytes from modem, data looks like: f6 
47
got 1 bytes from modem, data looks like: 02 
48
got 1 bytes from modem, data looks like: 00 
49
got 1 bytes from modem, data looks like: 41 
50
got 1 bytes from modem, data looks like: 03 
51
got 1 bytes from modem, data looks like: 42 
52
Received DOWNLOAD ACK from phone, your code is running now!
53
}}}
54
 * Observe further output of the serial port generated by the code you have downloaded
55
{{{
56
Hello World from C program code
57
======================================================================
58
Device ID code: B4FB
59
Device Version code: 0000
60
ARM ID code: FFF3
61
cDSP ID code: 0128
62
Die ID code: 6397191EFA039BE7
63
======================================================================
64
REG_DPLL=2002
65
CNTL_ARM_CLK=F081
66
CNTL_CLK=FF51
67
CNTL_RST=FFF7
68
CNTL_ARM_DIV=FFF9
69
======================================================================
70
REG_DPLL=2193
71
CNTL_ARM_CLK=F081
72
CNTL_CLK=FF51
73
CNTL_RST=FFF7
74
CNTL_ARM_DIV=FFF9
75
======================================================================
76
Releasing DSP from Reset
77
Loading initial DSP bootcode
78
Releasing DSP from Reset
79
Setting some api_ndb values
80
Setting API NDB parameters
81
DSP Download Status: 0001
82
DSP API Version: 0DC4 6308
83
Finishing download phase
84
DSP Download Status: 0002
85
DSP API Version: 3606 0000
86
}}}
87
88
== Known Problems ==
89 4 roh
90 5 laforge
For some USB-Serial converters (most notably FTDI based cables), you might need the {{{-m c123}}} mode, not the {{{-m c123xor}}} mode.
Add picture from clipboard (Maximum size: 48.8 MB)