FreeCalypso > hg > fc-magnetite

comparison doc/Pirelli-Howto @ 253:5b6159d76b09

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
doc/Pirelli-Howto: updated for the current situation
author Mychaela Falconia <falcon@freecalypso.org>
date Thu, 03 Aug 2017 17:28:25 +0000
parents 619a33e8425e
children 3608ce4a585a
comparison
equal deleted inserted replaced
252:1811c418461b 253:5b6159d76b09
1 Running FreeCalypso Magnetite firmware on the Pirelli DP-L10 1 Running FreeCalypso Magnetite firmware on the Pirelli DP-L10
2 ============================================================ 2 ============================================================
3 3
4 The Pirelli DP-L10 is a neat target for playing with FreeCalypso for two 4 The Pirelli DP-L10 is a neat target for playing with FreeCalypso for a few
5 reasons: 5 reasons:
6 6
7 1. It has a USB port connected to one of Calypso's UARTs through a built-in 7 1. It has a USB port connected to one of Calypso's UARTs through a built-in
8 CP2102 USB-serial adapter, eliminating the need for headset jack serial 8 CP2102 USB-serial adapter, eliminating the need for headset jack serial
9 cables. 9 cables.
10 10
11 2. The huge RAM on this phone (8 MiB) makes it possible to run experimental GSM 11 2. The huge RAM on this phone (8 MiB) makes it possible to run experimental GSM
12 firmware images entirely in RAM without flashing - and we have successfully 12 firmware images entirely in RAM without flashing - and we have successfully
13 implemented this capability in FC Magnetite similarly to Citrine. 13 implemented this capability in FC Magnetite similarly to Citrine.
14
15 3. Running an experimental firmware image on the Pirelli requires nothing more
16 than a laptop, a phone and a USB cable, and can therefore be done under
17 less-than-ideal conditions while away from your proper FreeCalypso hardware
18 lab with an FCDEV3B setup.
14 19
15 There is, however, one difference between our Citrine and Magnetite firmwares 20 There is, however, one difference between our Citrine and Magnetite firmwares
16 when it comes to running on the Pirelli without flashing: Citrine uses a 21 when it comes to running on the Pirelli without flashing: Citrine uses a
17 RAM-based fake FFS, whereas Magnetite always requires a real FFS in flash, even 22 RAM-based fake FFS, whereas Magnetite always requires a real FFS in flash, even
18 when the firmware code image itself is entirely RAM-based. However, just like 23 when the firmware code image itself is entirely RAM-based. However, just like
48 disabled, your Magnetite fw build will include those components. In the 53 disabled, your Magnetite fw build will include those components. In the
49 FreeCalypso environment where we are not doing WAP or MMS this functionality 54 FreeCalypso environment where we are not doing WAP or MMS this functionality
50 can only be exercised on targets that bring out a classic modem UART with the 55 can only be exercised on targets that bring out a classic modem UART with the
51 classic AT command interface to the external host, but the Pirelli is not one 56 classic AT command interface to the external host, but the Pirelli is not one
52 of those targets - hence on this target all FAX_AND_DATA and GPRS code is 57 of those targets - hence on this target all FAX_AND_DATA and GPRS code is
53 nothing but dead weight. We will only be able to remove this dead weight when 58 nothing but dead weight. Now that we have deblobbed all of L1 with the
54 we finish deblobbing L1: the few non-GPRS-specific L1 binary objects which we 59 exception of GPRS-specific modules, we could try building a hybrid config with
55 are still using have been built with IDS and L1_GPRS enabled, thus we cannot 60 GPRS and FAX_AND_DATA excluded, specifically for the benefit of Mot C1xx and
56 change these two configuration settings until those L1 modules have been 61 Pirelli targets, but these legacy hardware targets are no longer a priority for
57 deblobbed. We'll get there, but not yet. 62 the FreeCalypso family of projects.
58 63
59 Running on the target 64 Running on the target
60 ===================== 65 =====================
61 66
62 1. Connect a USB cable from your GNU/Linux PC/laptop to the phone. If the 67 1. Connect a USB cable from your GNU/Linux PC/laptop to the phone. If the
103 If you are not sure of the state of the Magnetite FFS flash area on your 108 If you are not sure of the state of the Magnetite FFS flash area on your
104 Pirelli, you can also run fc-fsio to examine it - so run fc-fsio either way. 109 Pirelli, you can also run fc-fsio to examine it - so run fc-fsio either way.
105 Run fc-fsio WITHOUT -p: let it connect to the rvinterf process you should 110 Run fc-fsio WITHOUT -p: let it connect to the rvinterf process you should
106 already have running from fc-xram. 111 already have running from fc-xram.
107 112
108 NOTE: the following instructions are based on the new version of fc-fsio that 113 [NOTE: you need to be running FreeCalypso host tools from the fc-host-tools-r5
109 has not yet made its way into a packaged fc-host-tools release as of this 114 release or later; earlier versions of fc-fsio won't work as described.]
110 writing. Therefore, please get the latest development version here:
111
112 https://bitbucket.org/falconian/freecalypso-tools
113 115
114 Once you are in fc-fsio, check the status of your FFS like this: 116 Once you are in fc-fsio, check the status of your FFS like this:
115 117
116 fsio> ls -l / 118 fsio> ls -l /
117 119