Flashing GSM firmware

[Steve " 'dillo" Okay]

On Feb 23, 2009, at 04:48 , community-request at lists.openmoko.org wrote:

> Send community mailing list submissions to
> 	community at lists.openmoko.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.openmoko.org/mailman/listinfo/community
> or, via email, send a message with subject or body 'help' to
> 	community-request at lists.openmoko.org
>
> You can reach the person managing the list at
> 	community-owner at lists.openmoko.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of community digest..."
> Today's Topics:
>
>    1. Updated WM8753 routing diagram with ALSA control names (was:
>       Re:	[FSO] Any luck with bluetooth headsets?) (Paul Fertser)
>    2. Re: Recommended SIM for Italy ? (Paul Fertser)
>    3. Re: Voicenote - new software (Francesco de Virgilio)
>    4. Re: [SHR Unstable + Qi]: WSOD (Andy Green)
>    5. Re: [FSO] Any luck with bluetooth headsets? (Andy Green)
>    6. [ubuntu host] NetworkManager improvements (Joel Newkirk)
>    7. Re: [ubuntu host] NetworkManager improvements (Denis Johnson)
>    8. opkg problem (Adam Jimerson)
>
> From: Paul Fertser <fercerpav at gmail.com>
> Date: February 23, 2009 1:48:56 AM GMT+01:00
> To: community at lists.openmoko.org
> Subject: Updated WM8753 routing diagram with ALSA control names  
> (was: Re: [FSO] Any luck with bluetooth headsets?)
> Reply-To: List for Openmoko community discussion  
> <community at lists.openmoko.org>
>
>
> Paul Fertser <fercerpav at gmail.com> writes:
>> Simon Kagstrom <simon.kagstrom at gmail.com> writes:
>>> From looking at the diagram, I think that would make sense at  
>>> least. I
>>> haven't figured out how to affect these still from looking in the  
>>> state
>>> file and in the driver though.
>>
>> I'm going to prepare a routing diagram with alsa control names  
>> printed
>> over it "real soon" (today/tomorrow), as i'm already familiar with  
>> the
>> driver code, so it's just work to be done.
>
> Man, it was tough:
> http://wiki.openmoko.org/wiki/Neo_1973_audio_subsystem#ALSA_Channels
>
> All alsa control names that affect routing are now printed over the
> diagram.
>
> I can provide Inkscape source file on demand.
>
> The controls that are not mentioned either affect ADC/DAC in various
> not routing-related ways (and to use them one most probably needs to
> look at the datasheet anyway) or affect power management in
> freerunner-specific way (and therefore their names are self- 
> explanatory).
>
> -- 
> Be free, use free (http://www.gnu.org/philosophy/free-sw.html)  
> software!
> mailto:fercerpav at gmail.com
>
>
>
>
>
>
> From: Paul Fertser <fercerpav at gmail.com>
> Date: February 23, 2009 2:09:45 AM GMT+01:00
> To: community at lists.openmoko.org
> Subject: Re: Recommended SIM for Italy ?
> Reply-To: List for Openmoko community discussion  
> <community at lists.openmoko.org>
>
>
> "GNUtoo" <GNUtoo at no-log.org> writes:
>> it's a bug in the GSM modem's firmware...it can be updated but I  
>> advise
>> you against doing it because there is some command to type and if you
>> makes a typo it can brick your gsm modem
>
> That's a lie.
>
> You can't brick your modem at all, as it has a ROM bootloader.
>
> Dedicated person can damage calibration data and that'd be a
> practically irrecoverable action (CMU-2000 and special soft are needed
> for calibration). BUT it's not as simple as making a typo.
>
> Damaging one's modem by typo is practically impossible, moreover, the
> new moko11 firmware contains quite an important fixes related to
> hardware flow control and resuming from call/sms. As it also fixes all
> known issues with any sim cards, it's worth updating.

Okay, I am pretty stuck here.
I've tried the procedure on the  Wiki here:
http://wiki.openmoko.org/wiki/GSM/Flashing
and here:
http://lists.openmoko.org/nabble.html#nabble-td1565196|a1566012

to no effect.

I run the fluid command and it just sits there at:
Bootloader: (reset target)

In the other terminal window, I'm repeatedly doing
echo 0 >/sys/bus/platform/devices/neo1973-pm-gsm.0/power_on
echo 1 >/sys/bus/platform/devices/neo1973-pm-gsm.0/power_on

to no effect.

I thought I might have downloaded the firmware in the wrong format  
(ASCII instead of binary), so I ran file and got :
gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-moko11-beta1.m0:  
Motorola S-Record; binary data in text format

So I'm stuck.
I don't think I "bricked" the GSM modem because it doesn't seem like  
I've uploaded anything to it.

Further thoughts or suggestions are most welcome.
Any further update on getting this FW into an image ?

Thanks,
-----Steve