Calypso firmware update (work in progress)

Joerg Reisenweber joerg at openmoko.org
Sun Nov 16 06:37:11 CET 2008


Am So  16. November 2008 schrieb Joel Newkirk:
> On Sun, 16 Nov 2008 11:13:41 +0800, Joerg Reisenweber <joerg at openmoko.org>
> wrote:
> > Am So  16. November 2008 schrieb Joel Newkirk:
> >> Is this firmware update expected to fix the 'bouncing calypso' (bug
> > #1024)
> >> issue as well?  
> > Not moko10 yet. We are still investigating this one.
> > 
> >> That's been killing me (either missing phone calls or 
> >> killing battery, depending on whether software 'fix' is enabled to
> > prevent
> >> deep sleep) since I received a V6 unit under warranty exchange.
> > 
> > You say you didn't see this problem at all with your previous device, and
> > now 
> > with the replacement it shows all the time?
> > Would be a great hint to find more details on this nasty #1024.
> > cheers
> > jOERG
> 
> That's correct.  On V5 hardware (first retail run, ordered from OM store
> early July) the GSM was fine.  Since I received V6 hardware after warranty
> exchange it loses GSM constantly, missing calls in the process. Apart from
> that I've been quite happy with the V6 hardware vis V5 - no SD corrupts,
> GPS reliable and swift, dead battery issue gone.  And my understanding is
> that the problem stems from firmware, not hardware?
> 
> mdbus retrieves: 'revision': '"HW: GTA02BV5, GSM:
> gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko8"' (although
> /proc/cpuinfo lists revision 0360 - why does dbus think it's V5?)
> 
> I'm willing for any nondestructive testing that would help.  (no debug
> board though, if that matters) Software or firmware or hardware rework.  (I
> have access to a Pace IR3000 rework station as well as handheld smd tools)

first of all it would be of interest to find out about exact serial# and 
GSM-FW revision of (your current and) former device, so we could possibly 
trace back the manufacturing process and scrutinize the logs, as well as 
FW-version etc.
Can you give any more details (pointer to ticket, reseller, dunno what) 
please.

Did you run the tests with same kernel and rootfs on both devices, and still 
different results for GSM?

Which SIM/provider are you using? 

Regards
jOERG
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part.
Url : http://lists.openmoko.org/pipermail/devel/attachments/20081116/93cf19c5/attachment.pgp 


More information about the devel mailing list