Re: No GSM. Suspect dead Calypso. What to do?
danek dan...@digsoc.com writes: 4. Since it took a while to get socat sorted, and I wasn't sure what you meant when you said Calypso goes to sleep very fast (goes to sleep after being powered on? in between commands? didn't know.) I If you give a pause when entering the commands it sleeps. The next command will then wake it up but it won't parse that first command. Neo: AT-Command Interpreter ready Me: ATE1 Neo: //nothing ... Me: ATE1 Neo: ATE1 OK Me: AT+CFUN=1 Neo: AT+CFUN=1 // pause for a couple of seconds ERROR // at this point, i don't know what has gone wrong, so I keep giving commands anyway... Me: AT+CPIN=4747 // i don't normally use a SIM pin, but i do like the number 47, so I set this SIM pin on my dumbphone. When I enter it when QPE asks me, it's happy. When I enter something else, it's not. So I'm assuming the Neo is working correctly with the PIN. Neo: AT+CPIN=4747 OK Me: AT+CPIN? Neo: AT+CPIN? +CPIN: READY OK Me: AT+COPS Neo: AT+COPS OK AT-Command Interpreter ready //It looks like it reset itself. I try dialing anyway... Everything looks normal here except the reset. Can you double check that you don't have any other software that could write to the power_on (or pwron) node of gsm in /sys? If this indeed is a real reboot of the calypso chip then we'd really like to see calypso debug output (you need to construct a cable to capture it, do you have electronics experience?). Me: ATD+1XXXYYY // this is a US telephone number, phone sitting next to me Yeah after reset it obviously looses registration to network. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: No GSM. Suspect dead Calypso. What to do?
Everything looks normal here except the reset. Can you double check that you don't have any other software that could write to the power_on (or pwron) node of gsm in /sys? I tried this in Om2008.12 and the latest fso-image-om-gta02 from unstable at downloads.openmoko.org/distro/unstable/NeoFreerunner. I made sure qpe and zhone, respectively, were stopped on the phone before power cycling the modem. This is off a fresh boot in all instances. As far as I know, qpe on Qtopia-based distributions and zhone on FSO-based distributions should be the only processes that normally access the modem. If there's something else I should try to ensure that nothing else might be accessing the modem, let me know. (When I get home later today, for example, I could try flashing a very basic image like fso-console-image-om-gta02, if you think it would be helpful. That way we can be more certain that nothing else is taking over the Calypso.) I should probably add that the apparent reset comes in immediately after the modem says AT+COPS\r\nOK\r\n -- if I change the timing of how quickly I enter commands by a second or so it will still reset immediately after I give AT+COPS, suggesting that it probably is related to whatever AT+COPS does, and not something that periodically resets the modem at some set interval. Also, is it normal for the modem to give AT+CFUN=1\r\nERROR\r\n when trying to set telephony mode? As I mentioned, this happens every time, and there's no indication what ERROR means exactly. Like I said before, if I do AT+CFUN? after doing AT+CFUN=1 and getting ERROR from the Calypso, I get +CFUN: 0 as a reply. If this part is working, shouldn't I be getting +CFUN: 1 to tell me it has successfully entered phone mode? If this indeed is a real reboot of the calypso chip then we'd really like to see calypso debug output (you need to construct a cable to capture it, do you have electronics experience?). I'm happy to do just about anything as long as it doesn't involve SMT. Will I need a ribbon cable to plug into the JTAG header on Neo's board? If so, where do you recommend getting one? -- View this message in context: http://n2.nabble.com/No-GSM.-Suspect-dead-Calypso.-What-to-do--tp2614421p2620308.html Sent from the Openmoko Support mailing list archive at Nabble.com. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: No GSM. Suspect dead Calypso. What to do?
In FSO images Zhone/ophonekitd are only GUI. You have to stop frameworkd. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: No GSM. Suspect dead Calypso. What to do?
danek dan...@digsoc.com writes: Also, is it normal for the modem to give AT+CFUN=1\r\nERROR\r\n when trying to set telephony mode? As I mentioned, this happens every time, and there's no indication what ERROR means exactly. yes. Like I said before, if I do AT+CFUN? after doing AT+CFUN=1 and getting ERROR from the Calypso, I get +CFUN: 0 as a reply. If this part is working, shouldn't I be getting +CFUN: 1 to tell me it has successfully entered phone mode? Haven't tried AT+CFUN? I'm happy to do just about anything as long as it doesn't involve SMT. Will I need a ribbon cable to plug into the JTAG header on Neo's board? If so, where do you recommend getting one? You need a 2.5mm 3-pole plug and then something to listen to the 115200 8N1 serial data coming the middle pole. This is 0..3V so you can't just plug into serial port of your PC (which is -5..5V afaik). I am trying to use my AVR microcontroller to do that but I was told a MAX232 chip can do the conversion for you. Please read the whole #1024 thread at http://lists.openmoko.org/pipermail/hardware/2009-April/thread.html -- it mentions how this cable can be built. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: No GSM. Suspect dead Calypso. What to do?
On Fri, Apr 10, 2009 at 08:17:17PM -0700, danek wrote: 4. Since it took a while to get socat sorted, and I wasn't sure what you meant when you said Calypso goes to sleep very fast (goes to sleep after being powered on? in between commands? didn't know.) Both. Also, from the GSM 07.07 document: 9.1 Report Mobile Equipment error +CMEE [...] Defined values n: 0 disable +CME ERROR: err result code and use ERROR instead 1 enable +CME ERROR: err result code and use numeric err values (refer next subclause) 2 enable +CME ERROR: err result code and use verbose err values (refer next subclause) The first few commands to send are these: AT AT%SLEEP=2 ATE1 AT+CMEE=2 Me: AT+COPS Neo: AT+COPS OK AT-Command Interpreter ready //It looks like it reset itself. I try dialing anyway... Perhaps the modem loses power? Which power sources are you connecting (charger/USB/battery)? Does the battery connector and the battery both have clean contact points? Are you using a battery of the same length as the original battery? -- Rask Ingemann Lambertsen Danish law requires addresses in e-mail to be logged and stored for a year ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: No GSM. Suspect dead Calypso. What to do?
9.1 Report Mobile Equipment error +CMEE Ah, brilliant; thank you very much for this tip. I set AT+CMEE=2 and it turned out the error I was getting after AT+CFUN=1 was simply that the SIM was locked with a PIN. After giving the PIN with +CPIN i did AT+CFUN? and got +CFUN: 1, which means that it *does* set phone mode correctly, and that the ERROR was nothing to worry about after all. It did, however, still reset and give me AT-Command Interpreter ready after doing AT+COPS, and setting CMEE=2 didn't give me any more information when that happened. I suppose I'll have to capture the output of the debug serial line. Perhaps the modem loses power? Which power sources are you connecting (charger/USB/battery)? Does the battery connector and the battery both have clean contact points? Are you using a battery of the same length as the original battery? An interesting idea, but I don't have much reason to believe so. USB is connected when I do this, as I am doing it through ssh over USB Ethernet. The battery (original battery) is usually fully charged or very near fully charged when I do so. All three contacts on both sides are clean. The phone powers up fine on battery alone, and I haven't noticed any perceptible drop in the battery's runtime, though I suppose it is possible that some sort of damage to the battery is rendering it unable to provide enough current to the modem. A bit of a long shot, and also something I can't test well, as I don't have a known good Neo or known good battery to swap with. -- View this message in context: http://n2.nabble.com/No-GSM.-Suspect-dead-Calypso.-What-to-do--tp2614421p2622773.html Sent from the Openmoko Support mailing list archive at Nabble.com. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: No GSM. Suspect dead Calypso. What to do?
You need a 2.5mm 3-pole plug and then something to listen to the 115200 8N1 serial data coming the middle pole. This is 0..3V so you can't just plug into serial port of your PC (which is -5..5V afaik). I am trying to use my AVR microcontroller to do that but I was told a MAX232 chip can do the conversion for you. Please read the whole #1024 thread at http://lists.openmoko.org/pipermail/hardware/2009-April/thread.html -- it mentions how this cable can be built. Unless I'm not looking carefully enough, all I can see is a pinout to the headers on the debug board (which I don't have) -- I'm assuming I can just wire this up to a DB-9 connector using the standard RS-232 pins for TX and RX, though you say that the voltage won't work... I'm assuming this would go for my USB-Serial adapter as well, since it is meant to take the place of a PC serial port. :( I will have a look at the docs for MAX232... though if you have a link to detailed info (pinouts, plus schematic for any supporting components for MAX232, etc.) from anybody who has built a suitable cable using this IC it would be helpful. Thanks again for your help and suggestions. -- View this message in context: http://n2.nabble.com/No-GSM.-Suspect-dead-Calypso.-What-to-do--tp2614421p2622798.html Sent from the Openmoko Support mailing list archive at Nabble.com. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] FSO unfunded?
Am Mi 8. April 2009 schrieb Craig Woodward: What does this mean? That FIC/OM don't have anyone working on it anymore? FIC isn't OM! /j signature.asc Description: This is a digitally signed message part. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO 5.1] Preventing screen blanking
Am Mi 8. April 2009 schrieb Nicola Mfb: Suppose now that tangoGPS or navit, or other gps tools may do simply a couple of call to org.freesmartphone.Usage.RequestResource at startup, when the application exits the fso daemon automagically releases the resources: you obtain a on-click-and-do-not-suspend-dim-navigation-system-restoring-all-at-exit :)) please see and support http://trac.freesmartphone.org/ticket/393 /j signature.asc Description: This is a digitally signed message part. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Call volume
Am Mi 8. April 2009 schrieb bburde...@comcast.net: Hi all; With SHR-testing the phone seems to be fairly usable. Battery life is even pretty decent. However, one thing that is a dealbreaker for me as far as using my freerunner as my main phone is the call volume. I can make calls just fine from my living room, but in a noisy cafe or inside a car I can't hear very well at all. I've adjusted the volume before from text config files, but you walk the line between usable call volume and bad echo problems for whoever you're talking to. Has anyone been able to address this for themselves? This is maybe the last major issue that keeps the FR from being my main phone. But unless this is addressed I can't really recommend the phone to anyone but hobbyists. Despite everybody else in this thread answered on how to adjust earpiece level, I get it your real problem is echo. please look here: http://wiki.openmoko.org/wiki/Neo_1973_and_Neo_FreeRunner_gsm_modem#Eliminating_echo_on_the_non-neo_end_.28far_end.29_of_phone_calls /j signature.asc Description: This is a digitally signed message part. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: No GSM. Suspect dead Calypso. What to do?
Am Sa 11. April 2009 schrieb Timo Juhani Lindfors: danek dan...@digsoc.com writes: 4. Since it took a while to get socat sorted, and I wasn't sure what you meant when you said Calypso goes to sleep very fast (goes to sleep after being powered on? in between commands? didn't know.) I If you give a pause when entering the commands it sleeps. The next command will then wake it up but it won't parse that first command. Give r...@om-gta02:~# mickeyterm -c --- Mickey's Term V2.9.1 @ /dev/pts/1 --- AT-Command Interpreter ready ATE1 (((this one invisible, you need to type blind. repeat if you don't get OK))) OK at%sleep=1 EXT: I OK ATE1 is enabling instant echo from calypso, which I find much more convenient (same as the char-wise input by -c parameter to mickeyterm) at%sleep=1 stops the annoying 10sec timeout that makes you enter every command twice. All this on GSM-flashing uSD-image booted from uSD, login via ssh. you might want to r...@om-gta02:~# ps x 1645 ?S 0:00 /bin/sh /etc/rc5.d/S99flash-moko start r...@om-gta02:~# kill 1645 to stop the gsm-flashing process (if you're sure FLUID isn't just about to flash the GSM-FW. I.e: if it shows either Bootloader: (reset target) or Program: (0 sectors, 0*8k=0k) () ok it's absolutely safe to kill the flashing process) Everything looks normal here except the reset. Can you double check that you don't have any other software that could write to the power_on (or pwron) node of gsm in /sys? If this indeed is a real reboot of the calypso chip then we'd really like to see calypso debug output (you need to construct a cable to capture it, do you have electronics experience?). Me: ATD+1XXXYYY // this is a US telephone number, phone sitting next to me Yeah after reset it obviously looses registration to network. I really wonder whether your battery is ok. You know modem is powered from battery and when it starts to transmit for registering to the network it demands quite some power from bat that can't be provided by bat-charger chip PMU. So it's very likely modem would reset due to brownout as soon as it tries to register to network. Please try and find a spare bat (see wiki for compatible bat e.g. from nokia if you can't manage to get a GTA02-bat). See if modem behaviour changes significantly with new bat. I'm really sorry you have such an extended period of problems with your FR's modem. Hope we will track it down now. HTH cheers jOERG signature.asc Description: This is a digitally signed message part. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: No GSM. Suspect dead Calypso. What to do?
Am So 12. April 2009 schrieb danek: You need a 2.5mm 3-pole plug and then something to listen to the 115200 8N1 serial data coming the middle pole. This is 0..3V so you Please DO NOT quote msgs without clearly marking them as quote (e.g. like above) I skip absolutely every msg I encounter that is fooling me like this. Thanks /j signature.asc Description: This is a digitally signed message part. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
