how to quote replies in nabble.com [Re: No GSM. Suspect dead Calypso. What to do?]
Hi, (top posting on purpose so that you see the whole message.) is there some way to notice when you are quoting somebody and when you are writing yourself? I was first about to ignore this email since I thought it was my own email. Usually people mark quotations by prefixing lines with . I'm writing this to mailing list since perhaps it's a common problem with nabble.com and somebody who uses it could help. best regards, Timo Lindfors danek dan...@digsoc.com writes: 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 ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: No GSM. Suspect dead Calypso. What to do?
On Sat, 2009-04-11 at 22:11 -0700, Joerg Reisenweber (via Nabble) wrote: 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 Oh dear... I'm terribly sorry about that. I didn't realize Nabble's e-mail version of the message didn't get any visible quote marking. I have been using Nabble for some time now, since I subscribe to the list in digest mode, and when I used to reply to messages from the digest it would break threads. How terrible that my trying to behave with better e-mail etiquette (preserving threads) ended up causing such a serious problem! Nabble does send me mail by default whenever somebody replies to a message I posted via Nabble, so from now on I will reply to messages in my mail client and let it handle the quoting instead of replying in Nabble. I don't know why I assumed that Nabble's quote feature would be e-mail friendly; maybe I was lulled into trusting it because in general it behaves very smartly. If you click on the Nabble link to see my messages, you will see that the lack of quote indicators was not due to any lack of effort on my part... Again I'm terribly sorry, and perhaps it's time for me to file a bug with Nabble, as this really is very bad behavior. -- View this message in context: http://n2.nabble.com/No-GSM.-Suspect-dead-Calypso.-What-to-do--tp2614421p2623857.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: how to quote replies in nabble.com [Re: No GSM. Suspect dead Calypso. What to do?]
On Sun, 2009-04-12 at 03:05 -0700, Timo Juhani Lindfors (via Nabble) wrote: Hi, (top posting on purpose so that you see the whole message.) is there some way to notice when you are quoting somebody and when you are writing yourself? I was first about to ignore this email since I thought it was my own email. Usually people mark quotations by prefixing lines with . I'm writing this to mailing list since perhaps it's a common problem with nabble.com and somebody who uses it could help. best regards, Timo Lindfors Unfortunately, it does appear to be Nabble's fault. I just looked at all of my messages from this thread in pipermail and realized to my horror that not a single one of them had any sort of marks for the quotes. I searched Nabble support just now, and didn't find anything that seemed relevant for e-mail quoting, so I posted something. I was very impressed with how smart and smooth Nabble is until I discovered this disturbing behavior... http://n2.nabble.com/Marking-quoted-text-in-e-mail-td2623929.html -- View this message in context: http://n2.nabble.com/No-GSM.-Suspect-dead-Calypso.-What-to-do--tp2614421p2623954.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?
On Sun, 2009-04-12 at 06:05 +0100, Joerg Reisenweber wrote: Give r...@om-gta02:~# mickeyterm -c 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) Thanks, I will try the GSM-flash uSD image and mickeyterm. And if you agree, I think it's probably safest to stop the flashing process by removing S99flash-moko from /etc/rc5.d since the rootfs is on uSD and therefore can be modified without powering the phone. (I guess same could be said about the .jffs2 images which you can mount via loopback on the big computer before flashing Neo.) 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. Another comment about the battery... I guess I have taken for granted the amount of power GSM needs. I did know that GSM needed more power than the 2.5W from USB; I discovered this the first time I saw a USB WWAN stick and wondered why it had a LiIon battery. I thought to myself, How silly... why not just USB power? I wonder it has the battery so it can function autonomously when unplugged from the computer? Then I did RTFM which said it needed the battery to supply additional power to the GSM chipset. I guess I assumed that if it had enough juice to boot (as booting also requires more power than USB alone can provide) then it had enough juice for the modem. Anyway, I do have a Nokia phone *somewhere* (it has been some time since I've known exactly where) that I used a couple of times to jump start Neo when I stupidly let its battery run down and couldn't boot as a result. I will see if I can find the Nokia battery and will hope for the best. (If it does turn out to be simply the battery, I will be extremely happy, and will buy a couple of extras... Glad to see that they are available separately now, and not only in the spares kit, as I already have pouch and headset from the group buy.) -- View this message in context: http://n2.nabble.com/No-GSM.-Suspect-dead-Calypso.-What-to-do--tp2614421p2623963.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?
Am So 12. April 2009 schrieb danek: On Sun, 2009-04-12 at 06:05 +0100, Joerg Reisenweber wrote: Give r...@om-gta02:~# mickeyterm -c 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) Thanks, I will try the GSM-flash uSD image and mickeyterm. And if you agree, I think it's probably safest to stop the flashing process by removing S99flash-moko from /etc/rc5.d ... Sure. The perfect way. If you are familiar with electronics you also could test the bat by probing for voltage and temporarily attaching a 1R2..1R5 (0.5W! better a 2W) during watching the voltage. (0.5sec). Or use a incandescent lightbulb that's drawing ~2A @ 3V5, instead of the resistor. You probably need a fast DVM or an analog voltmeter or 'scope for this. Bat voltage must not drop below say 3V. Well testing with a spare bat for sure is much simpler and yields more reliable results anyway. 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?
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: 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
Re: No GSM. Suspect dead Calypso. What to do?
danek dan...@digsoc.com writes: - A couple of weeks later I contacted the list for suggestions. Someone suggested looking at the output of logread, which showed a +CME ERROR: 100 when trying to talk to the So do I understand it right, calypso answers to AT commands and is thus not completely dead? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: No GSM. Suspect dead Calypso. What to do?
Yes, I should clarify that... Calypso seems to be present, but will not register the GSM network no matter what. Calypso is dead for certain values of dead. I should add that when I tried to use GSM manually it would hang when trying to connect to the modem. (Logdump does show quite a bit of ATChat, so I admit I may not have been connecting to the modem properly, but I did try following a couple of different guides on the subject.) If you can make more sense of ATChat logs than I can (my knowledge of AT is small, and is limited to having dialed ISPs on POTS modems many years ago; I have no knowledge of GSM) please have a look at my trac ticket http://docs.openmoko.org/trac/ticket/2229 where I have attached a few different logs. Another possibility is that something is wrong with the antenna, but again, I don't know how to read AT well enough to tell if registration fails because of a problem with the modem (which I suspect, because it really did just die suddenly out of the blue -- it was sitting on a table doing nothing between the last time I used it and the first time I couldn't use it anymore) or because of lack of signal. -- View this message in context: http://n2.nabble.com/No-GSM.-Suspect-dead-Calypso.-What-to-do--tp2614421p2616000.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?
danek dan...@digsoc.com writes: Another possibility is that something is wrong with the antenna, but again, I don't know how to read AT well enough to tell if Dec 19 22:53:09 om-gta02 user.notice root: AtChat : W : %CSQ: 16, 99, 1 shows that the signal gsm signal is there so it is not an antenna problem. Please try to register to network manually with socat. First stop all processes that access ttySAC0 and then echo 0 /sys/devices/platform/neo1973-pm-gsm.0/power_on echo 1 /sys/devices/platform/neo1973-pm-gsm.0/power_on socat - file:/dev/ttySAC0,crtscts,crnl,b115200 and then type (mind your own pin instead of ) ATE1 AT+CFUN=1 AT+CPIN= AT+CPIN? AT+COPS AT+COPS? and tell us the output. Note that you might want to send those commands multiple times since calypso will go to sleep very fast and when it wakes up it won't handle the first command it receives. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: No GSM. Suspect dead Calypso. What to do?
Timo, Thanks for the tip. I just got home and tried this, and it worked much better than the methods I had tried before for talking to Calypso manually (cu would hang and not accept any AT commands IIRC), but unfortunately I was still unable to register. Of course I was using 2007.2 (or 2008.4, depending on what you call it) because the instructions I found were ancient. I did as you said: 1. Stop anything using the /dev/TTYSAC0 -- I was using Om2008.12, so as far as I knew, this was just qpe. I did killall qpe, then when the error popped up on the Neo screen I told it not to relaunch. Then, for good measure, I stopped xserver-nodm too. 2. Power cycle the GSM modem. 3. socat ... this was not installed by default. I managed to find the package at opkg.org, but it depended on libssl 0.9.8 and libcrypto 0.9.8. I couldn't find packages for either. Opkg update; opkg upgrade did nothing. I noticed that I had version 0.9.7 of both, and figured that talking to the Calypso shouldn't involve any kind of encryption anyway, so I decided to do an ugly hack and symlink the 0.9.7 SOs to 0.9.8 so I could install socat. I just now realized that I probably didn't have / couldn't get 0.9.8 because I installed stable, and should probably switch to testing or something else, so that I can try this again as intended. I'll do that after I send this message and report back (not expecting much to happen). 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 figured it would be a good idea to power cycle the modem again. 5. OK, now we run socat with the parameters you gave: 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... Me: ATD+1XXXYYY // this is a US telephone number, phone sitting next to me Neo: //hang... //hang... //hang... i try ATH anyway Me: ATH Neo: ATH OK //phone doesn't ring Since it gave me an error at AT+CFUN=1 before, I tried again, just pasting AT+CFUN=1 over and over again, but it kept saying ERROR, whatever that error is. I didn't know what AT+CFUN=1 did, so I looked up Hardware:AT_Commands in the wiki and saw that AT+CFUN=1 sets the modem to phone mode. I saw that AT+CFUN? could be used to query what mode the modem was operating in, so I initialized the modem again and did AT?CFUN? and got +CFUN: 0 So if I understand what is happening correctly (and I might not, because this is my first time talking directly to a GSM device) it seems that the modem never goes into phone mode. Is there anything else you would try at this point? Thanks again, Daniel -- View this message in context: http://n2.nabble.com/No-GSM.-Suspect-dead-Calypso.-What-to-do--tp2614421p2619428.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?
OK, I just flashed the latest daily image from unstable so that I could test again, using socat with the correct versions of libssl and libcrypto. First let me say I'm very impressed with the great work being done with the software since I last used the phone... Anyway, an interesting thing happened when I tried to use socat. I booted the phone, made sure zhone wasn't running, power cycled the modem, installed and ran socat... what started happening is that the modem kept repeatedly saying OK OK OK... etc ad infinitum. Then I realized I hadn't installed the modules when I flashed the kernel and rootfs. I did this and repeated the procedure, and got the same results as I did when I was running Om2008.12 with socat linked with the wrong versions of libssl and libcrypto, which was more or less what I expected. -- View this message in context: http://n2.nabble.com/No-GSM.-Suspect-dead-Calypso.-What-to-do--tp2614421p2619601.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
No GSM. Suspect dead Calypso. What to do?
Hi support list, I posted previously about my problem on this list, and have not made any progress in my situation despite many repeated attempts at getting my modem to work. I tried everything I could think of, and when that didn't work, many people on the list had helpful suggestions, which I also tried to no avail. To recap briefly from my previous posts: - I started using the FreeRunner when I got it in August '08. I started using it as my daily phone pretty much right away, suffering for a while, before I got things working more or less the way I wanted them to. - In early December, it suddenly stopped working. I hadn't changed anything on the phone for several days before it stopped working. One minute I was making and receiving calls, and the next I couldn't dial out, and people couldn't reach me. I rebooted and it still didn't work. I switched my SIM to my dumbphone so I could look at the problem later when I got home. - I got home and reflashed my kernel and rootfs. No change. I tried several different combinations of kernel and rootfs, all of which worked fine with my phone and SIM before. I knew the SIM was fine, because it worked with my dumbphone. I tried some other SIMs anyway, which also were known to work with my phone before the GSM stopped working. Nothing. It was a busy week for me so I put the Neo down and kept using my dumbphone for a little while. - A couple of weeks later I contacted the list for suggestions. Someone suggested looking at the output of logread, which showed a +CME ERROR: 100 when trying to talk to the modem. Setting a PIN was also recommended; the phone prompted me for a PIN, meaning it was able to see my SIM, even though it couldn't register the network. It also rejected incorrect PIN entries and accepted correct ones, further demonstrating that the SIM was recognized. - Somebody also suggested flashing moko10. I did this, and the update took fine, but did nothing for my problem. - Elsewhere on the list, I read a tip about logging into the USB console to fix a broken u-boot environment. About a month or two before the GSM stopped working, my u-boot environment broke and I could only successfully boot from the NOR u-boot, not the NAND. I was able to successfully fix u-boot and boot from NAND once again, but my GSM was still broken. - I noticed that there was a beta moko11 firmware. In desperation, I flashed this. The update went fine, but still no GSM. - I have continued trying different images and SIMs and other things, hoping the phone would magically come back to life, but no luck. I can still use the FR for non-phone stuff (GPS still works like a champ), but would REALLY like to get GSM working again sometime soon. At this point I am convinced that something broke in the hardware somehow, and would like to know what I can do about getting the unit repaired and what the associated costs would be. -- View this message in context: http://n2.nabble.com/No-GSM.-Suspect-dead-Calypso.-What-to-do--tp2614421p2614421.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
