diff doc/Pirelli-Howto @ 998:7d3f0910aeb2

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
line wrap: on
line diff
--- a/doc/Pirelli-Howto	Sat Mar 05 05:10:49 2016 +0000
+++ b/doc/Pirelli-Howto	Sat Mar 05 20:50:37 2016 +0000
@@ -4,9 +4,9 @@
 Our experimental FC GSM fw can now run on the Pirelli DP-L10 target.  Our fw
 cannot yet operate this phone in a useful manner, i.e., it is not currently
 possible to replace Pirelli's proprietary fw with ours and use the phone as an
-end user.  Our gsm-fw is close to having working voice call functionality when
-controlled by an external host via AT commands, but we haven't even started
-working on the on-board user interface part yet.
+end user.  Our current gsm-fw has working SMS functionality (voice calls are
+still broken) when controlled by an external host via AT commands, but we
+haven't even started working on the on-board user interface part yet.
 
 One very useful special feature of the Pirelli DP-L10 is its very large RAM:
 8 MiB.  Having such large RAM allows us to run our experimental fw on this
@@ -23,8 +23,8 @@
 If you are ready to play with our experimental GSM pseudo-modem fw on your
 Pirelli, the steps are as follows:
 
-1. Build the firmware in the pirelli-gsm configuration - see the Compiling
-   document for more details.
+1. Build the firmware in the pirelli-gsm-rvtat configuration - see the
+   Compiling document for more details.
 
 2. Connect a USB cable from your GNU/Linux PC/laptop to the phone.  If the
    phone was off but the battery is present, it will go through a charger-plug
@@ -71,10 +71,11 @@
 Our fw is currently able to exercise all SIM interface functions (at least the
 obvious ones which I've tested), register with a live commercial GSM network
 using a legitimate SIM, and send and receive SMS using standard GSM 07.05 AT
-commands.  Voice calls don't work yet; dialing a MO call with the ATD command
-or placing a MT call to the device under test from the network side results in
-the firmware going haywire.  The latter misbehaviour is next to be investigated
-and (hopefully) fixed.
+commands.  Voice calls don't work yet: you can dial a MO call with the ATD
+command and you can place a MT call to the device under test from the network
+side and then answer it with ATA, these calls connect successfully, but the
+voice audio fails to pass through: nothing but noise is heard in the earpiece
+speaker.  See the Firmware_Status write-up for more information.
 
 When you are done playing with our experimental fw, you can either yank the
 battery and kill the host side rvinterf and fc-shell processes, or you can