Flashing GSM firmware
joerg at openmoko.org
Mon Mar 9 22:46:47 CET 2009
Am Mo 9. März 2009 schrieb Rask Ingemann Lambertsen:
> On Thu, Mar 05, 2009 at 10:25:40AM +0300, Paul Fertser wrote:
> > All this steps except starting fluid.exe are not strictly necessary
> > and i'd recommend to start fluid like that:
> > FLUID_PORT=/dev/ttySAC0 fluid.exe -oo -od13,13 -f <path_to_moko11_bin>
> > Notice i use ROM bootloader and moko11 firmware.
> I flashed the moko11 GSM firmware today and found the same thing: -oo
> without FLUID_FLOWCONTROL works.
option -oo is recommended standard operating procedure for now. There's no
particular advantage in trying to use firmware-bootloader first.
> I couldn't not get any of the other
> combinations to work.
> I first backed up the old firmware, then flashed the
> new one:
> # time FLUID_PORT=/dev/ttySAC0 fluid.exe -oo -r 0x00000000..0x00400000 -f
> (real 6m28.286s user 0m11.200s sys 0m4.315s)
> # time FLUID_PORT=/dev/ttySAC0 fluid.exe -oo -f
> (real 2m56.764s user 0m16.070s sys 0m0.990s)
> I did need two power off/on cycles between the two fluid invocations,
> though. I did not use "s3c24xx-gpio b7=0" as according to the schematics,
> pin GPIOB7 is just the MODEM_ON signal.
This doesn't exactly explain anything. For relation of SoC GPIO-b7 and and PMU
GPIO2 see discussion of gsm sysfs node fix in [hw].
If you were lucky to successfully flash without using "s3c24xx-gpio b7=0" you
probably used a recent kernel with sysfs node fix.
Anyway not following the quite accurate and detailed instructions on
gsm/flashing might explain why you didn't see any success on "the other
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://lists.openmoko.org/pipermail/community/attachments/20090309/e8914be4/attachment.pgp
More information about the community