FreeCalypso > hg > freecalypso-sw

comparison doc/Pirelli-Howto @ 998:7d3f0910aeb2

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
doc: Firmware_Status written, Freerunner-Howto & Pirelli-Howto updated
author Mychaela Falconia <falcon@ivan.Harhan.ORG>
date Sat, 05 Mar 2016 20:50:37 +0000
parents 7c5b129573f6
children 8b52011dc66a
comparison
equal deleted inserted replaced
997:c7ca69bf84f3 998:7d3f0910aeb2
2 ============================================================= 2 =============================================================
3 3
4 Our experimental FC GSM fw can now run on the Pirelli DP-L10 target. Our fw 4 Our experimental FC GSM fw can now run on the Pirelli DP-L10 target. Our fw
5 cannot yet operate this phone in a useful manner, i.e., it is not currently 5 cannot yet operate this phone in a useful manner, i.e., it is not currently
6 possible to replace Pirelli's proprietary fw with ours and use the phone as an 6 possible to replace Pirelli's proprietary fw with ours and use the phone as an
7 end user. Our gsm-fw is close to having working voice call functionality when 7 end user. Our current gsm-fw has working SMS functionality (voice calls are
8 controlled by an external host via AT commands, but we haven't even started 8 still broken) when controlled by an external host via AT commands, but we
9 working on the on-board user interface part yet. 9 haven't even started working on the on-board user interface part yet.
10 10
11 One very useful special feature of the Pirelli DP-L10 is its very large RAM: 11 One very useful special feature of the Pirelli DP-L10 is its very large RAM:
12 8 MiB. Having such large RAM allows us to run our experimental fw on this 12 8 MiB. Having such large RAM allows us to run our experimental fw on this
13 target entirely from RAM, without touching the flash. When you compile a 13 target entirely from RAM, without touching the flash. When you compile a
14 FreeCalypso gsm-fw image for the Pirelli target, by default a ramImage will be 14 FreeCalypso gsm-fw image for the Pirelli target, by default a ramImage will be
21 normally when you are not in the middle of a FreeCalypso firmware experiment. 21 normally when you are not in the middle of a FreeCalypso firmware experiment.
22 22
23 If you are ready to play with our experimental GSM pseudo-modem fw on your 23 If you are ready to play with our experimental GSM pseudo-modem fw on your
24 Pirelli, the steps are as follows: 24 Pirelli, the steps are as follows:
25 25
26 1. Build the firmware in the pirelli-gsm configuration - see the Compiling 26 1. Build the firmware in the pirelli-gsm-rvtat configuration - see the
27 document for more details. 27 Compiling document for more details.
28 28
29 2. Connect a USB cable from your GNU/Linux PC/laptop to the phone. If the 29 2. Connect a USB cable from your GNU/Linux PC/laptop to the phone. If the
30 phone was off but the battery is present, it will go through a charger-plug 30 phone was off but the battery is present, it will go through a charger-plug
31 power-on event; if the flash contains Pirelli's original fw, it will boot in 31 power-on event; if the flash contains Pirelli's original fw, it will boot in
32 the charging mode. If the battery is not present, the Calypso won't power 32 the charging mode. If the battery is not present, the Calypso won't power
69 AT+COPS=0 -- register to the default GSM network 69 AT+COPS=0 -- register to the default GSM network
70 70
71 Our fw is currently able to exercise all SIM interface functions (at least the 71 Our fw is currently able to exercise all SIM interface functions (at least the
72 obvious ones which I've tested), register with a live commercial GSM network 72 obvious ones which I've tested), register with a live commercial GSM network
73 using a legitimate SIM, and send and receive SMS using standard GSM 07.05 AT 73 using a legitimate SIM, and send and receive SMS using standard GSM 07.05 AT
74 commands. Voice calls don't work yet; dialing a MO call with the ATD command 74 commands. Voice calls don't work yet: you can dial a MO call with the ATD
75 or placing a MT call to the device under test from the network side results in 75 command and you can place a MT call to the device under test from the network
76 the firmware going haywire. The latter misbehaviour is next to be investigated 76 side and then answer it with ATA, these calls connect successfully, but the
77 and (hopefully) fixed. 77 voice audio fails to pass through: nothing but noise is heard in the earpiece
78 speaker. See the Firmware_Status write-up for more information.
78 79
79 When you are done playing with our experimental fw, you can either yank the 80 When you are done playing with our experimental fw, you can either yank the
80 battery and kill the host side rvinterf and fc-shell processes, or you can 81 battery and kill the host side rvinterf and fc-shell processes, or you can
81 issue a 'tgtreset' command at the fc-shell prompt. The latter will cause the 82 issue a 'tgtreset' command at the fc-shell prompt. The latter will cause the
82 target to reset and boot back into its regular firmware. 83 target to reset and boot back into its regular firmware.