comparison doc/C1xx-VPM-usage @ 26:f98ca59c079d

doc/C1xx-VPM-usage: new article
author Mychaela Falconia <falcon@freecalypso.org>
date Sun, 11 Jun 2023 22:36:46 +0000
parents
children
comparison
equal deleted inserted replaced
25:afd760eb1f8d 26:f98ca59c079d
1 Once you have flashed a FreeCalypso VPM firmware build into your C1xx phone,
2 what do you do with it afterward? In order to play with this voice pseudo-
3 modem, you need to connect the headset jack serial cable between your host
4 computer and your phone-turned-VPM and run rvinterf. With rvinterf running on
5 the serial or USB-serial port connected to the target, press the red power
6 button on the phone - a momentary press is sufficient. On C11x and C139
7 subfamilies you will hear a chirp sound as the firmware boots - this chirp
8 (comes unchanged from TI, going back to at least C-Sample, if not earlier) is
9 emitted via the buzzer, which is missing on C155/156. You will see debug trace
10 output from the fw in the rvinterf terminal window, and your setup is ready to
11 play with using fc-shell.
12
13 Every 5 s our VPM firmware sends a keepalive query packet out the serial port
14 (it's a FreeCalypso-invented extension to RVTMUX), and rvinterf responds with
15 keepalive answer. If there is no rvinterf, i.e., if you press the power button
16 on a VPM-flashed phone with no host computer connected or if you kill rvinterf
17 or unplug the serial cable, the firmware will automatically power off in 15 to
18 20 s after not receiving keepalive responses. On buzzer-equipped C11x and C139
19 phones you will hear another brief sound (of lower frequency) when the firmware
20 executes its poweroff operation.
21
22 If you plug in the charging power source (which forces the Calypso+Iota chipset
23 to be switched on), the firmware will not power off on its own for as long as
24 it is plugged in (the stay-on condition is charging power present OR rvinterf
25 present). If battery charging configuration is present in FFS (and it is
26 present in FFS images generated by scripts in the present fc-am-toolkit), the
27 battery will also charge - but please see caveats about battery charging at the
28 end of C1xx-flashing article.
29
30 Bringing up GSM network connection with fc-shell
31 ================================================
32
33 Once you have rvinterf running and communicating with the VPM-flashed C1xx
34 phone over the serial cable, you need to open another terminal window and run
35 fc-shell. That second fc-shell terminal window will be the method by which you
36 issue AT commands to the GSM MS.
37
38 The sequence of AT commands which I (Mother Mychaela) typically use when
39 bringing up a test GSM MS is as follows:
40
41 AT+CMEE=2 -- enable verbose error responses
42 AT+CFUN=1 -- bring up SIM and enable radio functionality
43 AT+CREG=2 -- see registration status async responses
44 AT+CRC=1 -- extended RING async responses
45 AT+CLIP=1 -- show calling number on incoming calls
46 AT+CNMI=2,1 -- show indications of incoming SMS
47 AT+COPS=0 -- connect to the default operator
48
49 Once you are connected to the network, you can dial outgoing voice calls with
50 ATDnumber; (semicolon at the end is required - no CSD support in VPM), and you
51 can answer incoming calls with ATA. ATH in an active call will hang up.
52
53 If you receive incoming SMS, they will be written into SIM storage (no ME
54 storage has been implemented in FreeCalypso yet), and if you did the AT+CNMI=2,1
55 step, you will see a +CMTI notification. You can then read them out with
56 fcup-smdump -R (the -R option tells fcup-* utilities to connect via rvinterf),
57 and you can decode the retrieved SMS PDUs with sms-pdu-decode. You can send
58 outgoing SMS with fcup-smsend -R - see documentation in FC host tools package.
59
60 Once you are done with your GSM play session, do a clean shutdown (IMSI detach
61 etc) with AT+CFUN=0, and then power down the VPM phone with fc-shell poweroff.