FreeCalypso > hg > freecalypso-sw
comparison README @ 897:e8bdd3d0c4c2
top README: status update
author | Space Falcon <falcon@ivan.Harhan.ORG> |
---|---|
date | Wed, 01 Jul 2015 06:29:55 +0000 |
parents | 78c894c7c471 |
children | 36e3f6bf0156 |
comparison
equal
deleted
inserted
replaced
896:7c5b129573f6 | 897:e8bdd3d0c4c2 |
---|---|
65 | 65 |
66 What we've done | 66 What we've done |
67 =============== | 67 =============== |
68 | 68 |
69 By a process of painstaking reintegration piece by piece, we have put together | 69 By a process of painstaking reintegration piece by piece, we have put together |
70 our own firmware suite for the Calypso that builds into a flashable image (but | 70 our own firmware suite for the Calypso that builds into a flashable or |
71 doesn't work properly yet - see below) and has the following essential | 71 RAM-loadable image and has the following essential features/qualities/ |
72 features/qualities/attributes: | 72 attributes: |
73 | 73 |
74 * Targets Calypso rather than LoCosto. This decision is somewhat controversial, | 74 * Targets Calypso rather than LoCosto. This decision is somewhat controversial, |
75 i.e., one could make a valid argument that we should have gone with LoCosto | 75 i.e., one could make a valid argument that we should have gone with LoCosto |
76 instead. But in our defense, we already have several pre-existing devices | 76 instead. But in our defense, we already have several pre-existing devices |
77 with the Calypso chipset on which we would like to run libre firmware; as for | 77 with the Calypso chipset on which we would like to run libre firmware; as for |
102 * The version of Nucleus we use comes from a non-TI source; all TI GSM fw | 102 * The version of Nucleus we use comes from a non-TI source; all TI GSM fw |
103 sources we found have their Nucleus in binary-only libs. | 103 sources we found have their Nucleus in binary-only libs. |
104 | 104 |
105 * To reiterate: our compiler is gcc, *not* TI's proprietary TMS470! | 105 * To reiterate: our compiler is gcc, *not* TI's proprietary TMS470! |
106 | 106 |
107 Current status (2015-05) | 107 Current status (2015-06-30) |
108 ======================== | 108 =========================== |
109 | 109 |
110 We are currently using the Calypso GSM modem in the Openmoko GTA02 smartphone | 110 Our current firmware can be built for two targets: Openmoko's Calypso modem |
111 as our bring-up vehicle. This target has been chosen as the BUV because it is | 111 built into their GTA01 and GTA02 smartphones (target gtamodem) and the Pirelli |
112 very close to TI's reference hardware platform (Leonardo) on which TI's TCS211 | 112 DP-L10 feature phone. The functionality is the same on both targets: a modem |
113 reference firmware was designed to run. Because our own firmware, despite | 113 or pseudo-modem controlled by AT commands (no local UI on the Pirelli), and |
114 having been reintegrated and rebuilt by us, is still based on TI's reference | 114 only the voice+SMS subset, i.e., no CSD, fax or GPRS yet. The firmware is able |
115 design and is only slowly diverging from that origin, it makes the most sense | 115 to register successfully to a live commercial GSM network (using a legitimate |
116 to bring our fw up on the most "vanilla" hw platform first, and only then port | 116 SIM of course), and SMS sending and receiving both work; all SIM interface |
117 to other hw targets of interest (Motorola and Pirelli phones) that exhibit | 117 functions also work as far as we've tested them. But voice calls don't work |
118 noticeable differences from TI's "canon". | 118 yet; making them work is our next task. |
119 | |
120 Our current gcc-built GSM firmware image runs on this gtamodem target. But it | |
121 doesn't work properly yet: getting this firmware *built* was the first half of | |
122 the project (took a year and a half), and now we enter the second stage: | |
123 debugging problems one by one until we make it work. Right now one can flash | |
124 our firmware image into a GTA02 modem and boot it; the modem running our fw | |
125 will then present a working AT command interface: one can exercise trivial | |
126 functions like version queries and even bring up SIM communication; one can | |
127 successfully query the SIM for its IMSI and phone numbers, for example. But | |
128 attempting to bring the radio interface up fails. There is also some weird | |
129 interaction with a hardware power cycling issue which we still need to | |
130 characterize further. | |
131 | |
132 We are confident that we can fix whatever issues currently prevent our gcc-built | |
133 firmware from working, and get it to work no worse than the original half-src, | |
134 half-binary TCS211 - at least in the voice+SMS functional subset, without CSD, | |
135 fax or GPRS. Once we reach that point, we will then port our FreeCalypso fw to | |
136 our non-Openmoko targets of interest (Motorola C1xx and Pirelli DP-L10), and | |
137 start reintegrating TI's reference UI code - our current fw is controlled by AT | |
138 commands only. Then later re-add CSD, fax and GPRS. | |
139 | 119 |
140 We have also produced some host tools for loading firmware into Calypso GSM | 120 We have also produced some host tools for loading firmware into Calypso GSM |
141 devices, for communicating with running firmwares over the RVTMUX interface, | 121 devices, for communicating with running firmwares over the RVTMUX interface, |
142 and for manipulating TI's flash file system. See README.hosttools for the | 122 and for manipulating TI's flash file system. See README.hosttools for the |
143 details. | 123 details. |