Re: [Gta04-owner] GTA04A4 starts shipping tomorrow
Am 31.01.2012 um 11:53 schrieb Dr. H. Nikolaus Schaller: > > Am 31.01.2012 um 15:30 schrieb Gennady.Kupava: >> As i were always wondering about SD reading issues in GTA02, which rises >> voltage in driver with reduced clock at beginning, and is not working at > > This is a patch in the GTA02 kernel to reduce noise *without* capacitor. > Only GTA02A6 boards have it. > >> 25MHz at all. I wonder can it be related to that capacitor? Are GTA04 >> users going to experience same speed issues with SD like in GTA02? > > No. It works at full speed, even with capacitor. Here: Last login: Wed Feb 1 06:58:19 2012 from 192.168.0.200 gta04:~# hdparm -t /dev/mmcblk0 /dev/mmcblk0: Timing buffered disk reads: 56 MB in 3.09 seconds = 18.12 MB/sec gta04:~# So it appears that the SD clock is even running at 50 MHz (SD is a 4 bit bus). ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Installing v35
Could it be that the AUX button is jammed closed. If powered on while AUX is pressed is how I get to a NOR boot. On Wed, Feb 1, 2012 at 6:07 AM, Liz wrote: > On Tue, 31 Jan 2012 14:22:06 +0100 > Radek Polak wrote: > > > > > > RED flash could mean that qi is started. > > > > Does it also vibrate? > > No > > > > Can you hold POWER button for long time? Qi should start kernel with > > verbose log then. > > > I get NOR > > > Another thing you can try is SD card installer mentioned here [1] > > I will try it, thanks > > > > Regards > > > > Radek > > > > [1] http://wiki.openmoko.org/wiki/QtMoko#OpenMobile.nl_Download > > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Re: New $200 tablet?
On Monday, January 30, 2012 11:36:37 PM Neil Jerram wrote: > "Gay, John (GE Energy Services, Non-GE)" writes: > > http://aseigo.blogspot.com/2012/01/reveal.html > > I hope it will be capable of running mainline kernels and any GNU/Linux > ecosystem software, not just KDE. > > I think Plasma Active looks pretty nice and interesting, and look > forward to being able to try it, but all the same I hope this tablet > will not be in some way _tied_ to KDE, or to a system image that only > the manufacturer can provide. (cf. Maemo.) > > Neil A lot of the base questions that the list has had seem to be answered on the blog post today: http://aseigo.blogspot.com/2012/01/open-beyond-licensing.html The TL;DR version to your question: yes you can. "For instance, the boot loader isn't locked so you can boot your own OS if you wish. You can install your own apps, you can even provide your own app delivery system." ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Gta04-owner] QtMoko v38 for GTA04 with suspend and GSM calls
On Tue, 31 Jan 2012 19:00:13 +0100 "Denis 'GNUtoo' Carikli" wrote: > hi, > how did you get suspend working reliabily? > personally I've that: > [ 406.115966] platform l3_main.0: LATE power domain suspend > > [ 406.121612] platform iva.0: LATE power domain suspend > > [ 406.126892] platform mpu.0: LATE power domain suspend > > [ 406.132171] omap_l3_smx omap_l3_smx.0: LATE power domain suspend > > [ 406.138458] reg-dummy reg-dummy: LATE suspend > > [ 406.143035] PM: late suspend of devices complete after 682.739 msecs > > [ 406.149688] Checking wakeup interrupts > > [ 406.876373] Successfully put all powerdomains to target state > > [ 406.882507] reg-dummy reg-dummy: EARLY resume > > [ 406.887115] omap_l3_smx omap_l3_smx.0: EARLY power domain resume > > [ 406.893402] platform mpu.0: EARLY power domain resume > > [ 406.898681] platform iva.0: EARLY power domain resume > > [ 406.903961] platform l3_main.0: EARLY power domain resume > > Should the userspace suspend/resume work in a way that is similar to > android(but in userspace): > The display would be powered off etc and the phone would try to suspend all > the time and would fully resume when he get a good reason to do so(like a > phone call or an user pressing the resume button). = There are lots of things that can wake up the phone. So are: - 3G chip signalling that something important happened - character arriving on a UART (from console, bluetooth, GPS) - power button, aux button, screen tap - USB plugged in/out Your wakeup happened 626 milliseconds after it went to sleep. Was the GPS chip on? That would do it (it reports every second I think). If so, you need to turn it off or tell it to stop reporting when you go into suspend mode (or generally when you don't care what it is saying). Of course it might be something else... Hope this helps. NeilBrown signature.asc Description: PGP signature ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Installing v35
On Tue, 31 Jan 2012 14:22:06 +0100 Radek Polak wrote: > > RED flash could mean that qi is started. > > Does it also vibrate? No > > Can you hold POWER button for long time? Qi should start kernel with > verbose log then. > I get NOR > Another thing you can try is SD card installer mentioned here [1] I will try it, thanks > > Regards > > Radek > > [1] http://wiki.openmoko.org/wiki/QtMoko#OpenMobile.nl_Download ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: openBmap: API troubles
Hi Michael, could you check your config file, and if the URLs point at realtimeblog.free.fr, replace them by openbmap.org. http://realtimeblog.free.fr/upload/upl.php5 becomes http://openbmap.org/upload/upl.php5 http://realtimeblog.free.fr/getInterfacesVersion.php becomes http://openbmap.org/getInterfacesVersion.php5 This is fixed in the trunk, but still has to be released. Let me know if this helps, Onen On 30/01/12 09:45, q...@gmx.de wrote: Hi, I'm just trying to access your API as described at http://openbmap.org/api/getGPSfromWifi.html but with no success. These are the RAW data I send to realtimeblog.free.fr: POST /api/getGPSfromWifiAPBSSID.php5 HTTP/1.1 Host: realtimeblog.free.fr Accept: text/xml, application/xml, */* Content-Type: application/x-www-form-urlencoded Content-Length: 18 bssid=0EFEFF7D2194 It should be a valid POST-request but I don't get back anything, no HTTP response, nothing, the host just closes the connection. What could be wrong in my request? Michael ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Installing v35
On Tue, 31 Jan 2012 13:35:43 +0100 Patryk Benderz wrote: > > > one has v35 on it from those downloads and exact same commands. > If that is true, this would mean that definitely something is wrong > with the device, not the flashing procedure itself. Are you sure that > both FR are the same revision (A4,A5,A6, buzz-fixed or not)? One is mine, and the buggy one my son's. They were bought at the same time. Neither has buzz-fix, they have the same date code on the internal sticker and the same date on the NOR boot screen. > > [cut] > > Does anyone have any ideas about a failed NAND > [cut] > That is what I was about to ask. How many time did you (and all > previous users) flashed internal NAND? AFAIR it doesn't have many > write cycles guaranteed by producent, however [1] says different. > > [1] http://wiki.openmoko.org/wiki/NAND_bad_blocks Each would have had the NAND flashed between 10 and 20 times. I see the wiki suggests it should have lasted longer. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Gta04-owner] QtMoko v38 for GTA04 with suspend and GSM calls
On Tuesday 31 January 2012 18:00:13 Denis 'GNUtoo' Carikli wrote: > hi, > how did you get suspend working reliabily? > personally I've that: > [ 406.115966] platform l3_main.0: LATE power domain suspend > [ 406.121612] platform iva.0: LATE power domain suspend > [ 406.126892] platform mpu.0: LATE power domain suspend > [ 406.132171] omap_l3_smx omap_l3_smx.0: LATE power domain suspend > [ 406.138458] reg-dummy reg-dummy: LATE suspend > [ 406.143035] PM: late suspend of devices complete after 682.739 msecs > [ 406.149688] Checking wakeup interrupts > [ 406.876373] Successfully put all powerdomains to target state > [ 406.882507] reg-dummy reg-dummy: EARLY resume > [ 406.887115] omap_l3_smx omap_l3_smx.0: EARLY power domain resume > [ 406.893402] platform mpu.0: EARLY power domain resume > [ 406.898681] platform iva.0: EARLY power domain resume > [ 406.903961] platform l3_main.0: EARLY power domain resume I think i saw something similar too, but in last few days suspend/resume worked fine. One reason could be that the phone wakes because of signal strength change. Do you disable signal strength modem reports before suspend? I always send "AT_OSQI=0" before suspend. Another thing is that i use QtMoko's feature which suspends phone after 20s when screen is locked, so it can save power on random wakeups. > Should the userspace suspend/resume work in a way that is similar to > android(but in userspace): > The display would be powered off etc and the phone would try to suspend all > the time and would fully resume when he get a good reason to do so(like a > phone call or an user pressing the resume button). In QtMoko it works same as Freerunner. But the suspend-when-locked feature is similar. I am personally using this featuer since Freerunner. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Gta04-owner] QtMoko v38 for GTA04 with suspend and GSM calls
hi, how did you get suspend working reliabily? personally I've that: [ 406.115966] platform l3_main.0: LATE power domain suspend [ 406.121612] platform iva.0: LATE power domain suspend [ 406.126892] platform mpu.0: LATE power domain suspend [ 406.132171] omap_l3_smx omap_l3_smx.0: LATE power domain suspend [ 406.138458] reg-dummy reg-dummy: LATE suspend [ 406.143035] PM: late suspend of devices complete after 682.739 msecs [ 406.149688] Checking wakeup interrupts [ 406.876373] Successfully put all powerdomains to target state [ 406.882507] reg-dummy reg-dummy: EARLY resume [ 406.887115] omap_l3_smx omap_l3_smx.0: EARLY power domain resume [ 406.893402] platform mpu.0: EARLY power domain resume [ 406.898681] platform iva.0: EARLY power domain resume [ 406.903961] platform l3_main.0: EARLY power domain resume Should the userspace suspend/resume work in a way that is similar to android(but in userspace): The display would be powered off etc and the phone would try to suspend all the time and would fully resume when he get a good reason to do so(like a phone call or an user pressing the resume button). Denis. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: New $200 tablet?
It's just Plasma Active on top of a meego-derived distro, right? http://community.kde.org/Plasma/Active/Development You can boot a USB live image on some other touchscreen device to play around; I did that on my s10-3t last night. On 31 January 2012 14:31, Patryk Benderz wrote: > [cut] >> Also, there is NO SOURCE CODE available publicly (maybe with the >> exception of one github repository which seems to have at least some >> code) which means that all companies currently selling this device are >> violating the GPL. > If you are sure above is true, it might be worth notifying [1],[2] and > kernel guys. > > [1] http://www.softwarefreedom.org/ > [2] http://gpl-violations.org/ > > -- > Patryk "LeadMan" Benderz > Linux Registered User #377521 > () ascii ribbon campaign - against html e-mail > /\ www.asciiribbon.org - against proprietary attachments > > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: New $200 tablet?
[cut] > Also, there is NO SOURCE CODE available publicly (maybe with the > exception of one github repository which seems to have at least some > code) which means that all companies currently selling this device are > violating the GPL. If you are sure above is true, it might be worth notifying [1],[2] and kernel guys. [1] http://www.softwarefreedom.org/ [2] http://gpl-violations.org/ -- Patryk "LeadMan" Benderz Linux Registered User #377521 () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Installing v35
On Tuesday 31 January 2012 11:25:49 Liz wrote: > In fact I am now back where I was 12 hours ago, with the Power button > just making a red flash on the Aux button and then locking up the > system with a blank screen. I have to remove the battery to reset (a > capacitor?) and then it can boot off the Aux button or applying a power > source to the USB connector. RED flash could mean that qi is started. Does it also vibrate? Can you hold POWER button for long time? Qi should start kernel with verbose log then. Another thing you can try is SD card installer mentioned here [1] Regards Radek [1] http://wiki.openmoko.org/wiki/QtMoko#OpenMobile.nl_Download ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Installing v35
[cut] sorry but I can stand it - first of all: I am glad you are not top posting, but please, trim your citations. There is no need to send all discussion again. [cut] > same result on the terminal : the dfu-utils says the bootloader is > installed the freerunner says the bootloader installed but it doesn't > actuallyresult in a NAND that I can access Radek asked you to paste output from terminal, not to describe what you see on it. He did it for one important reason. It might happen that you miss some information that might be vital for solving your problem. > > I have two freerunners on my desk, That situation is comfortable for debugging. If you do not fear of breaking another FR, you can repeat exactly the same procedure with working FR and check if it is valid, and allows you to flash FR and make it work. > one has v35 on it from those downloads and exact same commands. If that is true, this would mean that definitely something is wrong with the device, not the flashing procedure itself. Are you sure that both FR are the same revision (A4,A5,A6, buzz-fixed or not)? [cut] > Does anyone have any ideas about a failed NAND [cut] That is what I was about to ask. How many time did you (and all previous users) flashed internal NAND? AFAIR it doesn't have many write cycles guaranteed by producent, however [1] says different. [1] http://wiki.openmoko.org/wiki/NAND_bad_blocks -- Patryk "LeadMan" Benderz Linux Registered User #377521 () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v38 for GTA04 with suspend and GSM calls
Hi Radek, Am 29.01.2012 um 14:45 schrieb Radek Polak: > There is still problems with GSM calls that other site hears echo and you > will > need to set silent profile in Qtmoko's settings to have sound in incoming > call. while testing some boards with our arecord | aplay scripts I observed that the ringing tone of the phone being called is transmitted after several seconds. Let me try an explanation: * arecord on the microphone starts immediately filling the pipe * aplay towards the modem does not start before it gets clocked * this is only when the connection is accepted * this may delay up to 5 seconds * arecord on the modem does start at the same moment * and aplay on the phone sees an empty pipe until then So, the filling level of the pipe microphone -> CPU -> pipe -> CPU -> modem is up to 5 seconds with sound - before the phone call is established. This includes recording the ringing tone of my landline phone :) Since supplier and consumer speeds are both 8 kHz, the pipe filling level remains constant, i.e. the same delay. So a solution would be to use a pipe with limited size (does not exist) or write our own daemon to spawn and communicate with all arecord/aplay subprocesses and discard all microphone data until the first byte from the modem arrives. It does not need to be complex, just forking 4 processes and setting up a select(). Maybe, the code of femtocom.c could even be a start. If I find some time before/during FODEM I could give it a try... Hope this gives an idea... Nikolaus ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Gta04-owner] GTA04A4 starts shipping tomorrow
Am 31.01.2012 um 15:30 schrieb Gennady.Kupava: > Hello, Nikolaus, > > В Пнд, 30/01/2012 в 21:13 +0100, Dr. H. Nikolaus Schaller пишет: >> >> After 3 days of intensive research (incl. this weekend) we did find the root >> cause: it is the same as it was for the GTA02A5 board [1]. The SD card >> clock. It is 25 MHz and 25 * 63 = 1575 MHz, i.e. the GPS frequency. >> >> This means that the GTA04 creates some noise which is neglectable >> in more than 5cm distance with an external antenna, but not for the >> active GPS antenna built into the case. And some boards and >> antennas are a little better and others are a little worse so that it >> results in a basically working, but very unreilable receiver. >> >> The main problem was to find a measurement setup that gave >> reproducible results so that we could not only compare devices, swap >> antennas and try different shielding scenarios, but also check the >> effectiveness of measures against the problem. >> >> Like with the GTA02 there is a hardware and a software fix. The SW fix >> was to re-enable a feature in the 2.6.32 kernel that we had disabled due >> to problems with the SDIO driver. It appears that it is not at all necessary >> to change anything in the 3.2 kernel. So please forget immediately that >> there is a SW fix :) Because it fixes our unawareness and not a problem... >> >> The real hardware fix is adding a small capacitor like for the GTA02A5. >> >> You may wonder why we did not find it earlier. One aspect is testing time. >> The more testing you do the more issues you find. But we simply did >> not have enough GTA04A3 boards to do these tests... > > First of all, really nice to see that open phone reached release state. > > As i were always wondering about SD reading issues in GTA02, which rises > voltage in driver with reduced clock at beginning, and is not working at This is a patch in the GTA02 kernel to reduce noise *without* capacitor. Only GTA02A6 boards have it. > 25MHz at all. I wonder can it be related to that capacitor? Are GTA04 > users going to experience same speed issues with SD like in GTA02? No. It works at full speed, even with capacitor. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GTA04A4 starts shipping tomorrow
Hello, Nikolaus, В Пнд, 30/01/2012 в 21:13 +0100, Dr. H. Nikolaus Schaller пишет: > > After 3 days of intensive research (incl. this weekend) we did find the root > cause: it is the same as it was for the GTA02A5 board [1]. The SD card > clock. It is 25 MHz and 25 * 63 = 1575 MHz, i.e. the GPS frequency. > > This means that the GTA04 creates some noise which is neglectable > in more than 5cm distance with an external antenna, but not for the > active GPS antenna built into the case. And some boards and > antennas are a little better and others are a little worse so that it > results in a basically working, but very unreilable receiver. > > The main problem was to find a measurement setup that gave > reproducible results so that we could not only compare devices, swap > antennas and try different shielding scenarios, but also check the > effectiveness of measures against the problem. > > Like with the GTA02 there is a hardware and a software fix. The SW fix > was to re-enable a feature in the 2.6.32 kernel that we had disabled due > to problems with the SDIO driver. It appears that it is not at all necessary > to change anything in the 3.2 kernel. So please forget immediately that > there is a SW fix :) Because it fixes our unawareness and not a problem... > > The real hardware fix is adding a small capacitor like for the GTA02A5. > > You may wonder why we did not find it earlier. One aspect is testing time. > The more testing you do the more issues you find. But we simply did > not have enough GTA04A3 boards to do these tests... First of all, really nice to see that open phone reached release state. As i were always wondering about SD reading issues in GTA02, which rises voltage in driver with reduced clock at beginning, and is not working at 25MHz at all. I wonder can it be related to that capacitor? Are GTA04 users going to experience same speed issues with SD like in GTA02? Gennady ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Installing v35
On Tue, 31 Jan 2012 21:06:10 +1100 Liz wrote: > On Tue, 31 Jan 2012 10:58:00 +0100 > Korbinian Rosenegger wrote: > > > Hi > > > > On Tue, 2012-01-31 at 18:45 +1100, Liz wrote: > > > Sadly, I don't have Power and Aux buttons confused. > > > I don't have access to NAND from the Power button. > > > Both boot methods start the NOR bootloader. > > > > If you can't start the NAND bootloader and your Freerunner starts > > the NOR bootloader everytime, it may be possible that your AUX > > button got stuck somehow. A friend had the same problem with his > > brand new Freerunner. He was able to fix the problem himself, but > > he needed to replace (or resolder, don't remember) the AUX button. > > Are you able to cycle through the menu items in the bootloader by > > pressing AUX? If you can your AUX button is working. > > > > Korbi > > > > > > > Yes I can cycle through the menu on Aux. > Thanks for the idea, though > > ___ > In fact I am now back where I was 12 hours ago, with the Power button just making a red flash on the Aux button and then locking up the system with a blank screen. I have to remove the battery to reset (a capacitor?) and then it can boot off the Aux button or applying a power source to the USB connector. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Installing v35
On Tue, 31 Jan 2012 10:58:00 +0100 Korbinian Rosenegger wrote: > Hi > > On Tue, 2012-01-31 at 18:45 +1100, Liz wrote: > > Sadly, I don't have Power and Aux buttons confused. > > I don't have access to NAND from the Power button. > > Both boot methods start the NOR bootloader. > > If you can't start the NAND bootloader and your Freerunner starts the > NOR bootloader everytime, it may be possible that your AUX button got > stuck somehow. A friend had the same problem with his brand new > Freerunner. He was able to fix the problem himself, but he needed to > replace (or resolder, don't remember) the AUX button. > Are you able to cycle through the menu items in the bootloader by > pressing AUX? If you can your AUX button is working. > > Korbi > > > Yes I can cycle through the menu on Aux. Thanks for the idea, though ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Installing v35
Hi On Tue, 2012-01-31 at 18:45 +1100, Liz wrote: > Sadly, I don't have Power and Aux buttons confused. > I don't have access to NAND from the Power button. > Both boot methods start the NOR bootloader. If you can't start the NAND bootloader and your Freerunner starts the NOR bootloader everytime, it may be possible that your AUX button got stuck somehow. A friend had the same problem with his brand new Freerunner. He was able to fix the problem himself, but he needed to replace (or resolder, don't remember) the AUX button. Are you able to cycle through the menu items in the bootloader by pressing AUX? If you can your AUX button is working. Korbi ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Installing v35
On Tue, 31 Jan 2012 09:43:37 +0100 Radek Polak wrote: > On Tuesday 31 January 2012 08:45:11 Liz wrote: > > > Sadly, I don't have Power and Aux buttons confused. > > I don't have access to NAND from the Power button. > > Both boot methods start the NOR bootloader. > > I have loaded those three files into those places and the phone > > doesn't boot, it says there is a checksum error. I checked the > > md5sum with sourceforge, and it matches. > > Oki, so first you need bootloader. Can you please give exact steps > (copy paste commands from terminal) how are you doing it and what is > the outcome? Something like: > > $ wget > http://sourceforge.net/projects/qtmoko/files/qi-v35.udfu/download -O > qi- v35.udfu > > Resolving sourceforge.net... 216.34.181.60 > Connecting to sourceforge.net|216.34.181.60|:80... connected. > HTTP request sent, awaiting response... 302 Found > 2012-01-31 09:41:36 (190 KB/s) - `qi-v35.udfu' saved [29088/29088] > > > > $ md5sum qi-v35.udfu > fe258f3493b7aed65d61c74bdce26cc3 qi-v35.udfu > > > $ dfu-util -a u-boot -R -D qi-v35.udfu > dfu-util - (C) 2007-2008 by OpenMoko Inc. > This program is Free Software and has ABSOLUTELY NO WARRANTY > > Opening USB Device 0x:0x... > Claiming USB DFU Runtime Interface... > Determining device status: state = appIDLE, status = 0 > Device really in Runtime Mode, send DFU detach request... > Resetting USB... > > > Regards > > Radek downloaded bootloader from sourceforge whose md5sum is fe258f3493b7aed65d61c74bdce26cc3 downloads/qtmoko/qi-v35.udfu same result on the terminal : the dfu-utils says the bootloader is installed the freerunner says the bootloader installed but it doesn't actually result in a NAND that I can access I have two freerunners on my desk, one has v35 on it from those downloads and exact same commands. I don't think persevering with the dfu-utils is going to have any success with the second phone. Does anyone have any ideas about a failed NAND or ideas about updating a debian SD card which is FAT+ext2 and can be booted from NOR to qtmoko v35? Liz ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Installing v35
On Tuesday 31 January 2012 08:45:11 Liz wrote: > Sadly, I don't have Power and Aux buttons confused. > I don't have access to NAND from the Power button. > Both boot methods start the NOR bootloader. > I have loaded those three files into those places and the phone > doesn't boot, it says there is a checksum error. I checked the md5sum > with sourceforge, and it matches. Oki, so first you need bootloader. Can you please give exact steps (copy paste commands from terminal) how are you doing it and what is the outcome? Something like: $ wget http://sourceforge.net/projects/qtmoko/files/qi-v35.udfu/download -O qi- v35.udfu Resolving sourceforge.net... 216.34.181.60 Connecting to sourceforge.net|216.34.181.60|:80... connected. HTTP request sent, awaiting response... 302 Found 2012-01-31 09:41:36 (190 KB/s) - `qi-v35.udfu' saved [29088/29088] $ md5sum qi-v35.udfu fe258f3493b7aed65d61c74bdce26cc3 qi-v35.udfu $ dfu-util -a u-boot -R -D qi-v35.udfu dfu-util - (C) 2007-2008 by OpenMoko Inc. This program is Free Software and has ABSOLUTELY NO WARRANTY Opening USB Device 0x:0x... Claiming USB DFU Runtime Interface... Determining device status: state = appIDLE, status = 0 Device really in Runtime Mode, send DFU detach request... Resetting USB... Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
