comparison doc/Loadtools-usage @ 556:9a53f62c9990

doc/Loadtools-usage: updated for Leonardo and Tango support
author Mychaela Falconia <falcon@freecalypso.org>
date Sun, 05 Jan 2020 23:04:22 +0000
parents 018488f6343b
children e9d3fd3389e6
comparison
equal deleted inserted replaced
555:0093bf43c813 556:9a53f62c9990
14 XRAM, respectively, induce a transfer of control to the 14 XRAM, respectively, induce a transfer of control to the
15 loaded code, and then drop into a serial line pass-thru 15 loaded code, and then drop into a serial line pass-thru
16 mode for the operator to interact with the thus loaded 16 mode for the operator to interact with the thus loaded
17 target code. 17 target code.
18 18
19 The currently supported target devices are (in the order of decreasing 19 The currently supported target devices are:
20 preference) official Calypso development boards (TI's D-Sample and our own 20
21 FCDEV3B), Openmoko GTA01/02 and Huawei GTM900 GSM/GPRS modems, and two "alien" 21 1) All Calypso devices (preferably with Iota ABB so we can cleanly power off
22 Calypso phone families: Motorola C1xx and Sony Ericsson J100 by Compal and 22 after we are done) that have Calypso boot ROM (version 0200 or 0300) enabled
23 Pirelli DP-L10 by Foxconn. Any other "alien" Calypso target that has the boot 23 by nIBOOT strapping on the board. This category includes TI and FreeCalypso
24 ROM enabled (e.g., Mot W220 by Chi-Mei) can also be easily added. 24 development boards, several modems (Openmoko GTA01/02, Huawei GTM900, Tango)
25 and other devices.
26
27 2) Motorola C1xx and Sony Ericsson J100 phones made by Compal: these phones do
28 NOT have Calypso boot ROM enabled, but they provide a different way of
29 gaining serial code download access which is supported by our tools.
25 30
26 All tools in the FreeCalypso loadtools suite work by feeding pieces of code to 31 All tools in the FreeCalypso loadtools suite work by feeding pieces of code to
27 the target device as it boots, preventing the booting of its regular firmware 32 the target device as it boots, preventing the booting of its regular firmware
28 and diverting control to these externally-loaded code pieces. These pieces of 33 and diverting control to these externally-loaded code pieces. These pieces of
29 ARM7 target code need to be installed on the host system running loadtools, 34 ARM7 target code need to be installed on the host system running loadtools,
82 Mot W220 -h w220 87 Mot W220 -h w220
83 Openmoko GTA02 -h gta02 88 Openmoko GTA02 -h gta02
84 Pirelli DP-L10 -h pirelli 89 Pirelli DP-L10 -h pirelli
85 Sony Ericsson J100 -h compal -c 1004 90 Sony Ericsson J100 -h compal -c 1004
86 TI D-Sample -h dsample 91 TI D-Sample -h dsample
92 TI Leonardo -h leonardo
93 Tango modem -h tango
87 94
88 3. Cause the target device to execute its boot path. TI/Openmoko/FreeCalypso 95 3. Cause the target device to execute its boot path. TI/Openmoko/FreeCalypso
89 and Pirelli targets have the Calypso boot ROM enabled, and will interrupt 96 and other sensible targets have the Calypso boot ROM enabled, and will
90 and divert their normal boot path when they "hear" the beacons which 97 interrupt and divert their normal boot path when they "hear" the beacons
91 fc-loadtool will be sending down the serial line. Compal phones have this 98 which fc-loadtool will be sending down the serial line. Compal phones have
92 boot ROM disabled at the board level, but their standard firmware includes a 99 this boot ROM disabled at the board level, but their standard firmware
93 flash-resident bootloader that offers a different way of interrupting the 100 includes a flash-resident bootloader that offers a different way of
94 boot path and loading code over the serial line; fc-loadtool will be set up 101 interrupting the boot path and loading code over the serial line;
95 to speak the latter protocol when run with the corresponding options from 102 fc-loadtool will be set up to speak the latter protocol when run with the
96 the table above. 103 corresponding options from the table above.
97 104
98 You will see messages showing fc-loadtool's progress with feeding first 105 You will see messages showing fc-loadtool's progress with feeding first
99 compalstage (if needed), then loadagent (always needed) to the target device, 106 compalstage (if needed), then loadagent (always needed) to the target device,
100 followed by some target-specific initialization done via loadagent commands. 107 followed by some target-specific initialization done via loadagent commands.
101 If all of the above succeeds, you will land at a loadtool> prompt. Type 108 If all of the above succeeds, you will land at a loadtool> prompt. Type