Re: Flashing GSM firmware
Rask Ingemann Lambertsen r...@sygehus.dk writes: I did need two power off/on cycles between the two fluid invocations, though. I found by experimentation that with -od13,13 fluid was able to connect to the bootloader every time i tried power-cycling. But yes, without it it's like 1 out of 20 when it fails. I did not use s3c24xx-gpio b7=0 as according to the schematics, pin GPIOB7 is just the MODEM_ON signal. And that MODEM_ON is a push-button (literally). Looks like every time it's pressed for like 200ms the modem restarts (or starts if it wasn't powered before). Pressing is transition from b7=0 to b7=1. BTW, modem reset line is not connected on GTA02. With any new kernel all that gpio pmu tricks are not necessary anymore (at least on GTA02) as it reliably powers off/on the modem if you use sysfs interface. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Flashing GSM firmware
On Thu, 5 Mar 2009, Joerg Reisenweber wrote: rootfs is a standard FSO-console MS5 patched to fix doesn't boot on r/o mounted fs issue. Kernel is recent Andy tracking with GSM sysfs node patch created originally by PaulFerster based on my suggestions. then, thank you to all of those people. MOKO11 was a corporate work involving quite a number of people on IRC, mainly PaulFerster, Werner, Lindi (iirc), and me. Dieter checked for the bugs we spotted and fixed them in calypso's FW. that's interesting, i hadn't realised that any people in openmoko had access to the calypso firmware source; i thought the project was still dependent on TI fixing bugs as the community found them. good to hear this is not so, and thanks to those above who are improving it! The uSD image was entirely created, tested and published by me. Original idea: roh. then thanks to the both of you, too. one of my showing-off points for the 'moko is the way that custom distributions can be created to do specific, complex tasks; this is a perfect example. and to paul fertser: i happily concede that it's perfectly possible to do the firmware upgrade using the very precise and helpful instructions on the wiki, and thanks for reminding people that this works fine. the attraction of the SD-based method to me was that neither the tools (nor any dependencies they may drag in during the install) have to live on my 'moko in normal operation, with their attendant (though doubtless small) risk of destabilising it; i run the phone environment when it's a phone, and the upgrading environment when it's upgrading the firmware, and ne'er the twain shall meet. thanks to tar (to back the card up before the dd) and fdisk+tar (to restore it after flashing), it doesn't need a spare SD card. also, i have two mokos, and it's quite a time-efficient way to do a bunch of them. as a user, i was given a choice of ways to do a complex but desirable task, and i was able to pick the one that best suited my temperament and situation; i got freedom, is what i got. thank you all for it! -- Tom Yates - http://www.teaparty.net ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Flashing GSM firmware
On Mar 9, 2009, at 00:44 , Tom Yates wrote: On Thu, 5 Mar 2009, Joerg Reisenweber wrote: rootfs is a standard FSO-console MS5 patched to fix doesn't boot on r/o mounted fs issue. Kernel is recent Andy tracking with GSM sysfs node patch created originally by PaulFerster based on my suggestions. then, thank you to all of those people. MOKO11 was a corporate work involving quite a number of people on IRC, mainly PaulFerster, Werner, Lindi (iirc), and me. Dieter checked for the bugs we spotted and fixed them in calypso's FW. that's interesting, i hadn't realised that any people in openmoko had access to the calypso firmware source; i thought the project was still dependent on TI fixing bugs as the community found them. good to hear this is not so, and thanks to those above who are improving it! The uSD image was entirely created, tested and published by me. Original idea: roh. then thanks to the both of you, too. one of my showing-off points for the 'moko is the way that custom distributions can be created to do specific, complex tasks; this is a perfect example. and to paul fertser: i happily concede that it's perfectly possible to do the firmware upgrade using the very precise and helpful instructions on the wiki, and thanks for reminding people that this works fine. the attraction of the SD-based method to me was that neither the tools (nor any dependencies they may drag in during the install) have to live on my 'moko in normal operation, with their attendant (though doubtless small) risk of destabilising it; i run the phone environment when it's a phone, and the upgrading environment when it's upgrading the firmware, and ne'er the twain shall meet. I would like to add to this that, while it's not desirable to have the tools and SD image on your phone, it is possible. When I found out about the SD-based method, I was surrounded by Macs and my nearest Linux system with an SD-card reader was either in my pocket or 7K miles back home :) So I cleaned out some stuff on my GTA02 and was able to download the SD image onto it and dd that onto the uSD in my FR and reboot. The flashing procedure was successful and now all my SIMs work. Steve ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Flashing GSM firmware
Hello, On Thu, Mar 5, 2009 at 4:22 PM, Tom Yates madhat...@teaparty.net wrote: if anyone else is minded to try it, there are a few more details at http://wiki.openmoko.org/wiki/GSM/Flashing#uSD-card_Image . Will this image work on a Neo 1973 as well? -- Regards, Torfinn Ingolfsen ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Flashing GSM firmware
Torfinn Ingolfsen tin...@gmail.com writes: On Thu, Mar 5, 2009 at 4:22 PM, Tom Yates madhat...@teaparty.net wrote: if anyone else is minded to try it, there are a few more details at http://wiki.openmoko.org/wiki/GSM/Flashing#uSD-card_Image . Will this image work on a Neo 1973 as well? Not yet. But the manual instructions at the OM wiki were verified to work on Neo1973. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Flashing GSM firmware
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. 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 0x..0x0040 -f ~rask/download/firmware/calypso-firmware-backup.m0 (real 6m28.286s user0m11.200s sys 0m4.315s) # time FLUID_PORT=/dev/ttySAC0 fluid.exe -oo -f ~rask/download/firmware/calypso-moko11.m0 (real 2m56.764s user0m16.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. -- Rask Ingemann Lambertsen Danish law requires addresses in e-mail to be logged and stored for a year ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Flashing GSM firmware
On Thu, 5 Mar 2009, Paul Fertser wrote: Alternatively, try Joerg's uSD automated image: http://people.openmoko.org/joerg/calypso_moko_FW/moko11/flash-moko11_uSD-image.tar.gz It works and reliably flashes the firmware for you. yaaay joerg and thank you! i just safely and efficiently upgraded both my freerunners with that image. if you are not aged 22 and thus do not have the eyes of an eagle (i'm not, and i don't) you may need a magnifying glass to read the screen properly, esp. when the text goes blue-on-blue. you may wish to get the magnifying glass ready first, instead of going into a panic when it's already running, like i did. if anyone else is minded to try it, there are a few more details at http://wiki.openmoko.org/wiki/GSM/Flashing#uSD-card_Image . -- Tom Yates - http://www.teaparty.net ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Flashing GSM firmware
Tom Yates madhat...@teaparty.net writes: On Thu, 5 Mar 2009, Paul Fertser wrote: Alternatively, try Joerg's uSD automated image: http://people.openmoko.org/joerg/calypso_moko_FW/moko11/flash-moko11_uSD-image.tar.gz It works and reliably flashes the firmware for you. yaaay joerg and thank you! i just safely and efficiently upgraded I can't resist to note that this is as safe as upgrading by hand, so for those who don't have a spare uSD handy or time to download 90M image and feel confident enough in killing unnecessary processes (for SHR it's ophonekitd, for FSO it's Zhone or whatever dialer you use) i can still suggest to use the manual method (i recommend to follow the instructions given in my previous letter in this thread, where ROM bootloader is used from the beginning, and don't forget to cd /usr/sbin before starting fluid.exe ;) ). -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Flashing GSM firmware
Am Do 5. März 2009 schrieb Andy Green: Somebody in the thread at some point said: | On Thu, 5 Mar 2009, Paul Fertser wrote: | | Alternatively, try Joerg's uSD automated image: | http://people.openmoko.org/joerg/calypso_moko_FW/moko11/flash-moko11_uSD-image.tar.gz | | It works and reliably flashes the firmware for you. | | yaaay joerg and thank you! i just safely and efficiently upgraded both my I think there's a little confusion going on here, AIUI Werner did the rootfs end and Deiter the GSM firmware upgrade and deserve the thanks for that. You haven't understood it quite right, and obviously there *is* some confusion going on *somewhere*. rootfs is a standard FSO-console MS5 patched to fix doesn't boot on r/o mounted fs issue. Kernel is recent Andy tracking with GSM sysfs node patch created originally by PaulFerster based on my suggestions. MOKO11 was a corporate work involving quite a number of people on IRC, mainly PaulFerster, Werner, Lindi (iirc), and me. Dieter checked for the bugs we spotted and fixed them in calypso's FW. The uSD image was entirely created, tested and published by me. Original idea: roh. So all those people deserve a special thank you, and Andy deserves a special acknowledge for sedulous mobbing as soon as joerg is mentioned somewhere. :( /j signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Flashing GSM firmware
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | I think there's a little confusion going on here, AIUI Werner did the | rootfs end and Deiter the GSM firmware upgrade and deserve the thanks | for that. | | You haven't understood it quite right, and obviously there *is* some confusion | going on *somewhere*. I'm not quite sure when you stopped working for Openmoko / will stop working for us, but talking of confusion the openmoko.org address either doesn't or won't help. | rootfs is a standard FSO-console MS5 patched to fix doesn't boot on r/o | mounted fs issue. | Kernel is recent Andy tracking with GSM sysfs node patch created originally by | PaulFerster based on my suggestions. | MOKO11 was a corporate work involving quite a number of people on IRC, mainly | PaulFerster, Werner, Lindi (iirc), and me. Dieter checked for the bugs we | spotted and fixed them in calypso's FW. | The uSD image was entirely created, tested and published by me. | Original idea: roh. | | So all those people deserve a special thank you, and Andy deserves a special | acknowledge for sedulous mobbing as soon as joerg is mentioned somewhere. | | :( Just saying joerg's image would be totally misleading. Glad you agree. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmwPnMACgkQOjLpvpq7dMrTJQCbBje6BK0p95cGooXj2PHlw+x8 Q10Anj3BgrYSh4klNddHuYFZDEBg/qmr =XRTu -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Flashing GSM firmware
On Mar 5, 2009, at 19:26 , Joerg Reisenweber wrote: Am Do 5. März 2009 schrieb Andy Green: Somebody in the thread at some point said: | On Thu, 5 Mar 2009, Paul Fertser wrote: | | Alternatively, try Joerg's uSD automated image: | http://people.openmoko.org/joerg/calypso_moko_FW/moko11/flash- moko11_uSD-image.tar.gz | | It works and reliably flashes the firmware for you. This actually did it for me. I gave up on doing it by hand last week and just went out and got a SIM for Wind, it was just quicker. When I saw this message though, I thought I should give it one more try. It works. The Vodaphone SIM that was giving me so much trouble now registers properly in Zhone and Qtopia. FFR, the flash-moko11_uSD-image file just barely fits onto the main flash of the FR so you can dd it from there onto your uSD. Thanks for all your help, Steve ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Flashing GSM firmware
Steve 'dillo Okay armad...@roadknightlabs.com writes: I'm trying to flash my GSM firmware and running into a problem. I get to the point where I run the fluid command line and it just sits there. Basically the idea is that in one terminal you run fluid with right parameters, and in the other you powercycle the modem. Sometimes powercycling is needed more than once (while fluid still stays at (reset target)). And make sure no app accesses GSM. Also i'd recommend to use the latest stable or any recent andy-tracking kernel, but it's not strictly necessary. Here's the output of what I'm typing in the main window: r...@om-gta02:/usr/sbin# echo 0 /sys/bus/platform/devices/neo1973-pm- gsm.0/power_on r...@om-gta02:/usr/sbin# echo 1 /sys/bus/platform/devices/neo1973-pm- gsm.0/power_on r...@om-gta02:/usr/sbin# s3c24xx-gpio b7=0 r...@om-gta02:/usr/sbin# echo a...@poff /dev/ttySAC0 r...@om-gta02:/usr/sbin# FLUID_PORT=/dev/ttySAC0 FLUID_FLOWCONTROL=h fluid.exe \ -oO -b 115200\ -f /home/root/gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0- moko10.m0 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. In the other terminal something like this should be enough: r...@om-gta02:/usr/sbin# echo 0 /sys/bus/platform/devices/neo1973-pm- gsm.0/power_on r...@om-gta02:/usr/sbin# echo 1 /sys/bus/platform/devices/neo1973-pm- gsm.0/power_on r...@om-gta02:/usr/sbin# s3c24xx-gpio b7=0 If fluid doesn't pass the (reset target) state, repeat this steps. Basically it's like i described. Alternatively, try Joerg's uSD automated image: http://people.openmoko.org/joerg/calypso_moko_FW/moko11/flash-moko11_uSD-image.tar.gz It works and reliably flashes the firmware for you. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Flashing GSM firmware
On Feb 23, 2009, at 04:48 , community-requ...@lists.openmoko.org wrote: Send community mailing list submissions to community@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-requ...@lists.openmoko.org You can reach the person managing the list at community-ow...@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 fercer...@gmail.com Date: February 23, 2009 1:48:56 AM GMT+01:00 To: community@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@lists.openmoko.org Paul Fertser fercer...@gmail.com writes: Simon Kagstrom simon.kagst...@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:fercer...@gmail.com From: Paul Fertser fercer...@gmail.com Date: February 23, 2009 2:09:45 AM GMT+01:00 To: community@lists.openmoko.org Subject: Re: Recommended SIM for Italy ? Reply-To: List for Openmoko community discussion community@lists.openmoko.org GNUtoo gnu...@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 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Flashing GSM firmware (was Re: Recommended SIM for Italy ?)
2009/2/23 Steve 'dillo Okay armad...@roadknightlabs.com: r...@om-gta02:/usr/sbin# echo 0 /sys/bus/platform/devices/neo1973-pm- gsm.0/power_on r...@om-gta02:/usr/sbin# echo 1 /sys/bus/platform/devices/neo1973-pm- gsm.0/power_on r...@om-gta02:/usr/sbin# echo a...@poff /dev/ttySAC0 r...@om-gta02:/usr/sbin# FLUID_PORT=/dev/ttySAC0 fluid.exe -oo -b 115200 -f /home/root/gsm_ac_gp_fd_pu_em_cph_ ds_vc_cal35_ri_36_amd8_ts0-moko10.m0 FLUID Revision 2.27, (23 Aug 2004). Copyright Texas Instruments, 2001-2004. Reading image file: '/home/root/ gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-moko10.m0' (2138kB) ok Bootloader: (reset target) Help ? How long should I wait for the Bootloader to respond to the s3c24xx- gpio b7=1 command ? Hi Steve, after you see Bootloader: (reset target) you have to do r...@om-gta02:~# s3c24xx-gpio b7=1 in the second session. This worked for me with moko11-b1 :) Best Peter ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Flashing GSM firmware
Steve \ 'dillo\ Okay armad...@roadknightlabs.com writes: 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 estimate the probability of this not working for the first time as 0.1. So, after the second try it will most certainly work. Are you sure nothing is accessing your modem at that time? Use lsof to check. Also, it's possible that your kernel version has power_on sysfs node in another place, make sure the node actually exists there. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Flashing GSM firmware
On Feb 24, 2009, at 11:01 , Paul Fertser wrote: Steve \ 'dillo\ Okay armad...@roadknightlabs.com writes: 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 estimate the probability of this not working for the first time as 0.1. So, after the second try it will most certainly work. Are you sure nothing is accessing your modem at that time? Use lsof to check. Also, it's possible that your kernel version has power_on sysfs node in another place, make sure the node actually exists there. I'm using the fso-console image recommended in the GSM Flashing wiki page. downloaded from here: http://people.openmoko.org/mickey/images/openmoko-fso-console-image- glibc-ipk--20081028-om-gta02.rootfs.jffs2.summary http://people.openmoko.org/mickey/images/uImage-2.6.24+r10+gitr75999 +54524f4531c8b262431b794fea610d81bb351c86-r10-om-gta02.bin The /sys/bus/platform entry is a symbolic link to /sys/devices/ platform and contains: r...@om-gta02:/sys/devices/platform/neo1973-pm-gsm.0# pwd /sys/devices/platform/neo1973-pm-gsm.0 r...@om-gta02:/sys/devices/platform/neo1973-pm-gsm.0# ls -l -rw-r--r--1 root root 4096 Feb 24 11:05 download lrwxrwxrwx1 root root0 Feb 24 11:05 driver - ../../../bus/platform/drivers/neo1973-pm-gsm -rw-r--r--1 root root 4096 Feb 24 11:05 flowcontrolled -r--r--r--1 root root 4096 Feb 24 11:05 modalias drwxr-xr-x2 root root0 Feb 24 11:05 power -rw-r--r--1 root root 4096 Feb 24 11:05 power_on -rw-r--r--1 root root 4096 Feb 24 11:05 reset lrwxrwxrwx1 root root0 Feb 24 11:05 subsystem - ../../../bus/platform -rw-r--r--1 root root 4096 Feb 24 11:04 uevent r...@om-gta02:/sys/devices/platform/neo1973-pm-gsm.0# So it looks like the power_on node is there. The default value at boot of the power_on node is 0. I'll try writing to it directly rather than going through the link, although I don't know why that would make any difference. lsof reveals nothing interesting. I ran the gsm0710muxd start script and it shows that the gsm daemon isn't running: r...@om-gta02:/# /etc/init.d/gsm0710muxd stop no process in pidfile '/var/run/gsm0710muxd.pid' found; none killed r...@om-gta02:/# What you're saying makes sense, i.e. that something is using the GSM modem, but it does look it's shut off. Thanks for your help, Steve ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Flashing GSM firmware
So fluid is still not flashing the image, but I noticed the following messages on the console after my latest attempt: The error message: rxerr: port ch=0x00, rxs=0x000c shows up in dmesg after I send the command: echo a...@poff /dev/ttySAC0 Looking back through dmesg, this seems to be a pretty consistent error message: modem wakeup interruptresult of echo 1 / sys/devices/platform/neo1973-pm-gsm.0/power_on rxerr: port ch=0x88, rxs=0x0004 ---result of echo a...@poff / dev/ttySAC0 rxerr: port ch=0x00, rxs=0x000c rxerr: port ch=0x14, rxs=0x0004 rxerr: port ch=0x61, rxs=0x0004 rxerr: port ch=0x12, rxs=0x0004 This happens consistently as a result of the following command sequence: r...@om-gta02:/usr/sbin# echo 0 /sys/devices/platform/neo1973-pm-gsm. 0/power_on r...@om-gta02:/usr/sbin# echo 1 /sys/devices/platform/neo1973-pm-gsm. 0/power_on r...@om-gta02:/usr/sbin# s3c24xx-gpio b7=0 r...@om-gta02:/usr/sbin# echo a...@poff /dev/ttySAC0 r...@om-gta02:/usr/sbin# This is referenced in this bug report: http://docs.openmoko.org/trac/ticket/2180 So it looks like my attempt to apply the fix for this bug may be getting stomped on by the bug itself :) Steve ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Flashing GSM firmware (was Re: Recommended SIM for Italy ?)
From: Paul Fertser fercer...@gmail.com Date: February 23, 2009 2:09:45 AM GMT+01:00 To: community@lists.openmoko.org Subject: Re: Recommended SIM for Italy ? Reply-To: List for Openmoko community discussion community@lists.openmoko.org GNUtoo gnu...@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. Thanks Paul, I'm trying to flash my GSM firmware and running into a problem. I get to the point where I run the fluid command line and it just sits there. Here are the steps I'm taking for doing the flashing. I'm following the docs on the wiki at: http://wiki.openmoko.org/wiki/GSM/Flashing. After I get the Bootloader: (reset target) message, I run s3c24xx-gpio b7=1 in another xterm, ssh'ed into the FR. and the main window just sits there. Here's the output of what I'm typing in the main window: r...@om-gta02:/usr/sbin# echo 0 /sys/bus/platform/devices/neo1973-pm- gsm.0/power_on r...@om-gta02:/usr/sbin# echo 1 /sys/bus/platform/devices/neo1973-pm- gsm.0/power_on r...@om-gta02:/usr/sbin# s3c24xx-gpio b7=0 r...@om-gta02:/usr/sbin# echo a...@poff /dev/ttySAC0 r...@om-gta02:/usr/sbin# FLUID_PORT=/dev/ttySAC0 FLUID_FLOWCONTROL=h fluid.exe \ -oO -b 115200\ -f /home/root/gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0- moko10.m0 FLUID Revision 2.27, (23 Aug 2004). Copyright Texas Instruments, 2001-2004. Reading image file: '/home/root/ gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-moko10.m0' (2138kB) ok Bootloader: (reset target) r...@om-gta02:/usr/sbin# echo 0 /sys/bus/platform/devices/neo1973-pm- gsm.0/power_on r...@om-gta02:/usr/sbin# echo 1 /sys/bus/platform/devices/neo1973-pm- gsm.0/power_on r...@om-gta02:/usr/sbin# s3c24xx-gpio b7=0 r...@om-gta02:/usr/sbin# echo a...@poff /dev/ttySAC0 r...@om-gta02:/usr/sbin# FLUID_PORT=/dev/ttySAC0 FLUID_FLOWCONTROL=h fluid.exe -oo -b 57600 -f /home/root/gsm_ ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-moko10.m0 FLUID Revision 2.27, (23 Aug 2004). Copyright Texas Instruments, 2001-2004. Reading image file: '/home/root/ gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-moko10.m0' (2138kB) ok Bootloader: (reset target) r...@om-gta02:/usr/sbin# echo 0 /sys/bus/platform/devices/neo1973-pm- gsm.0/power_on r...@om-gta02:/usr/sbin# echo 1 /sys/bus/platform/devices/neo1973-pm- gsm.0/power_on r...@om-gta02:/usr/sbin# echo a...@poff /dev/ttySAC0 r...@om-gta02:/usr/sbin# FLUID_PORT=/dev/ttySAC0 fluid.exe -oo -b 115200 -f /home/root/gsm_ac_gp_fd_pu_em_cph_ ds_vc_cal35_ri_36_amd8_ts0-moko10.m0 FLUID Revision 2.27, (23 Aug 2004). Copyright Texas Instruments, 2001-2004. Reading image file: '/home/root/ gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-moko10.m0' (2138kB) ok Bootloader: (reset target) Help ? How long should I wait for the Bootloader to respond to the s3c24xx- gpio b7=1 command ? The documentation makes it sound like it should happen right away. Thanks, -Steve ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
