Re: Installing v35
On Wed, 1 Feb 2012 21:27:13 +0100 Boudewijn wrote: > Hmmm... Must be driving you quite mad after all this testing. In > which area do you live, is there anyone with a debug board not too > far away? I'm calmer than that - One day I will have a GTA-04 board. > > FOSDEM might be an opportunity, if it is in your part of earth, but > your email address sounds like Australia so no luck there? Not just Australia, but a long way away from any major centres. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Installing v35
On Wednesday 01 February 2012 20:30:40 Liz wrote: > On Tue, 31 Jan 2012 14:22:06 +0100 > > Radek Polak wrote: > > Another thing you can try is SD card installer mentioned here [1] > > > > Regards > > > > Radek > > > > [1] http://wiki.openmoko.org/wiki/QtMoko#OpenMobile.nl_Download > > This thinks it writing to the NAND, but the reboot fails. When I reboot > it the freerunner goes through the same cycle of writing and telling me > that Qi is installed, but still no effect. So your NAND boot looks really dead. You can try QtMoko v26 - it has kernel 1.9MB and should be booted ok from NOR. You can download it here [1]. If you have debug board then there is possibility to flash NOR boot e.g. with qi, but i never tried anything like that. Maybe its possible to do it even without debug board - just wiring 2 pins, but i dont recall details. Regards Radek [1] http://sourceforge.net/projects/qtmoko/files/OldStable/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Installing v35
On Wednesday 01 February 2012 20:53:41 Liz wrote: > On Wed, 01 Feb 2012 19:09:50 +0400 > > "Gennady.Kupava" wrote: > > Try this > > http://wiki.openmoko.org/wiki/NAND_bad_blocks#Clearing_BadBlocks > > first. > > Original bad blocks list > (...) > New bad blocks list > (...) > tried qi-v35.udfu again, no change > back to finding that microSD card :( Hmmm... Must be driving you quite mad after all this testing. In which area do you live, is there anyone with a debug board not too far away? FOSDEM might be an opportunity, if it is in your part of earth, but your email address sounds like Australia so no luck there? Boudewijn smime.p7s Description: S/MIME cryptographic signature ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Installing v35
On Wed, 01 Feb 2012 19:09:50 +0400 "Gennady.Kupava" wrote: > Try this > http://wiki.openmoko.org/wiki/NAND_bad_blocks#Clearing_BadBlocks > first. Original bad blocks list Device 0 bad blocks: 022a 03d4 04c6 0ff8 0ffa 0ffc 0ffe New bad blocks list Device 0 bad blocks: 022a 04c6 0ff8 0ffa 0ffc 0ffe tried qi-v35.udfu again, no change back to finding that microSD card :( ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Installing v35
On Wed, 1 Feb 2012 13:07:00 +0100 "Dr. H. Nikolaus Schaller" wrote: > Before doing this, consider upgrading to a GTA04 board :) > > I've paid for one. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Installing v35
Am 01.02.2012 um 16:35 schrieb Gennady.Kupava: > As your NAND is unusable at all, i guess it's appropriate to try > anything except hammer or trash bin. Before doing this, consider upgrading to a GTA04 board :) Or getting a used GTA02 Motherboard: http://www.handheld-linux.com/wiki.php?page=Neo%20Freerunner%3ASpare%20Parts ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Installing v35
As your NAND is unusable at all, i guess it's appropriate to try anything except hammer or trash bin. > > > I saw that, and didn't know if it was appropriate to try it. > I've now dropped the microSD card and lost it so Ill that later. > > ___ > 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: Installing v35
On Wed, 01 Feb 2012 19:09:50 +0400 "Gennady.Kupava" wrote: > I see one more possibility here - > > May be something with bad blocks in beginning of of NAND. You can try > to completely clear your NAND and recreate BBT and partitions. > > Try this > http://wiki.openmoko.org/wiki/NAND_bad_blocks#Clearing_BadBlocks > first. > > Gena > > I saw that, and didn't know if it was appropriate to try it. I've now dropped the microSD card and lost it so Ill that later. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Installing v35
В Втр, 31/01/2012 в 10:58 +0100, Korbinian Rosenegger пишет: > it may be possible that your AUX button got > stuck somehow. A friend had the same problem with his brand new > Freerunner. It should be easy to check stuck button, just press AUX in NOR u-boot menu, it it doesn't react or meny items switching like crazy without touching it - some problems with aux exist. It should be also possible to just read some memory address from inside NOR u-boot i guess to find out real state of AUX. Gena ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Installing v35
I see one more possibility here - May be something with bad blocks in beginning of of NAND. You can try to completely clear your NAND and recreate BBT and partitions. Try this http://wiki.openmoko.org/wiki/NAND_bad_blocks#Clearing_BadBlocks first. Gena В Срд, 01/02/2012 в 20:55 +1100, Liz пишет: > On Wed, 01 Feb 2012 09:24:29 +0100 > Patryk Benderz wrote: > > > However I have just reread through > > your description of a problem and realised I had also some strange > > problems (partial boot) which was resolved by flashing different qi > > bootloader. Do both FR have the same bootloader? > > Currently yes, qi-v35.udfu > I have also tried the qi-31.udfu u-boot_g2x_2.udfu and even the ancient > u-boot-gta02v5-1.3.1+gitr650149z53dbdd48bf6dfef90930c8ab182adb512-r1.bin > and just tried the qi-v36.udfu > > > == > root@mum-quad:/home/liz/downloads/qtmoko# dfu-util -a u-boot -R -D > qi-v36.udfu dfu-util 0.5 > > (C) 2005-2008 by Weston Schmidt, Harald Welte and OpenMoko Inc. > (C) 2010-2011 Tormod Volden (DfuSe support) > This program is Free Software and has ABSOLUTELY NO WARRANTY > > dfu-util does currently only support DFU version 1.0 > > Opening DFU USB device... ID 1d50:5119 > Run-time device DFU version 0100 > Found DFU: [1d50:5119] devnum=0, cfg=1, intf=0, alt=1, name="u-boot" > Claiming USB DFU Interface... > Setting Alternate Setting #1 ... > Determining device status: state = dfuIDLE, status = 0 > dfuIDLE, continuing > DFU mode device DFU version 0100 > Device returned transfer size 4096 > No valid DFU suffix signature > Warning: File has no DFU suffix > bytes_per_hash=581 > Copying data from PC to DFU device > Starting download: [##] > finished! state(2) = dfuIDLE, status(0) = No error condition is present > Done! > Resetting USB to switch back to runtime mode > > == > > result? none significant - we're back to the power button starting the > NOR boot. > > ___ > 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: Installing v35
On Wed, 01 Feb 2012 09:24:29 +0100 Patryk Benderz wrote: > However I have just reread through > your description of a problem and realised I had also some strange > problems (partial boot) which was resolved by flashing different qi > bootloader. Do both FR have the same bootloader? Currently yes, qi-v35.udfu I have also tried the qi-31.udfu u-boot_g2x_2.udfu and even the ancient u-boot-gta02v5-1.3.1+gitr650149z53dbdd48bf6dfef90930c8ab182adb512-r1.bin and just tried the qi-v36.udfu == root@mum-quad:/home/liz/downloads/qtmoko# dfu-util -a u-boot -R -D qi-v36.udfu dfu-util 0.5 (C) 2005-2008 by Weston Schmidt, Harald Welte and OpenMoko Inc. (C) 2010-2011 Tormod Volden (DfuSe support) This program is Free Software and has ABSOLUTELY NO WARRANTY dfu-util does currently only support DFU version 1.0 Opening DFU USB device... ID 1d50:5119 Run-time device DFU version 0100 Found DFU: [1d50:5119] devnum=0, cfg=1, intf=0, alt=1, name="u-boot" Claiming USB DFU Interface... Setting Alternate Setting #1 ... Determining device status: state = dfuIDLE, status = 0 dfuIDLE, continuing DFU mode device DFU version 0100 Device returned transfer size 4096 No valid DFU suffix signature Warning: File has no DFU suffix bytes_per_hash=581 Copying data from PC to DFU device Starting download: [##] finished! state(2) = dfuIDLE, status(0) = No error condition is present Done! Resetting USB to switch back to runtime mode == result? none significant - we're back to the power button starting the NOR boot. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Installing v35
On Wed, 1 Feb 2012 08:15:11 +1000 Dave wrote: > 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. Thanks for remembering, but already checked, and is OK. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Installing v35
[cut] > 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] > Each would have had the NAND flashed between 10 and 20 times. I see > the wiki suggests it should have lasted longer. So both these track gets us no where. However I have just reread through your description of a problem and realised I had also some strange problems (partial boot) which was resolved by flashing different qi bootloader. Do both FR have the same bootloader? -- 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
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: 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: 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: 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: 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
Re: Installing v35
On Tue, 31 Jan 2012 08:07:57 +0100 Radek Polak wrote: > On Tuesday 31 January 2012 05:39:59 Liz wrote: > > > I tried flashing the NAND with a few other bootloaders. > > What I have now is that pushing the Power key gives me NOR boot. > > First i think you are mixing POWER and AUX button: > > POWER = the circle button near the USB connector > AUX = the rectangular button on the same side as headphones jack > > and you are mixing NOR and NAND: > > NOR = the readonly memory with original uboot > NAND = writable memory with your kernel+rootfs+bootloader > > I think you should first enter NOR boot: hold AUX then press POWER. > You will see uboot menu. > > Now plug USB cable and flash to NAND kernel+rootfs+bootloader: > > dfu-util -a kernel -R -D uImage-v35.bin > dfu-util -a rootfs -R -D qtmoko-debian-v35.ubi > dfu-util -a u-boot -R -D qi-v35.udfu > > Power off the phone and remove your SD card. Now just shortly press > POWER. The phone will blink with LED and vibrate (this is done by qi > bootloader) and should start booting. > > > I can boot an old Om2008 I've got here > > but after that I lost touchscreen input again > > Original QT was working last night - but I don't have a copy of that > > kernel and image any more. > > I think you can forget about booting old kernels and using NOR > bootloader. They are bugged. > > > NOR boot can only boot off SD card if FAT + ext2 > > and so it can't read the debian on ext3 that I made. > > Qi bootloader can boot from SD card with ext3 partition. You just > need to unpack the qtmoko release tarball on SD card. > > > What options do I have to get qtmoko working? > > You can have qtmoko on SD card or on NAND. For bootloader you must > use NAND bootloader which is activated *just with POWER button*. You > can use qi (recommended) or some uboot from gena2x - you have to > search a bit for it. > > Good luck > > Radek 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. I've got a SD card with the tarball unpacked onto it, and the phone won't boot that - because I have no Qi bootloader that I can access from the Power key. Last installed was the uboot from gena2x with a default config file, but still this does not work. I need some other ideas, please. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Installing v35
On Tuesday 31 January 2012 05:39:59 Liz wrote: > I tried flashing the NAND with a few other bootloaders. > What I have now is that pushing the Power key gives me NOR boot. First i think you are mixing POWER and AUX button: POWER = the circle button near the USB connector AUX = the rectangular button on the same side as headphones jack and you are mixing NOR and NAND: NOR = the readonly memory with original uboot NAND = writable memory with your kernel+rootfs+bootloader I think you should first enter NOR boot: hold AUX then press POWER. You will see uboot menu. Now plug USB cable and flash to NAND kernel+rootfs+bootloader: dfu-util -a kernel -R -D uImage-v35.bin dfu-util -a rootfs -R -D qtmoko-debian-v35.ubi dfu-util -a u-boot -R -D qi-v35.udfu Power off the phone and remove your SD card. Now just shortly press POWER. The phone will blink with LED and vibrate (this is done by qi bootloader) and should start booting. > I can boot an old Om2008 I've got here > but after that I lost touchscreen input again > Original QT was working last night - but I don't have a copy of that > kernel and image any more. I think you can forget about booting old kernels and using NOR bootloader. They are bugged. > NOR boot can only boot off SD card if FAT + ext2 > and so it can't read the debian on ext3 that I made. Qi bootloader can boot from SD card with ext3 partition. You just need to unpack the qtmoko release tarball on SD card. > What options do I have to get qtmoko working? You can have qtmoko on SD card or on NAND. For bootloader you must use NAND bootloader which is activated *just with POWER button*. You can use qi (recommended) or some uboot from gena2x - you have to search a bit for it. Good luck Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Installing v35
On Tue, 31 Jan 2012 09:18:27 +1100 Liz wrote: > On Mon, 31 Oct 2011 02:25:54 +1100 > Philip Rhoades wrote: > > > I used: > > > > dfu-util -a kernel -R -D uImage-v35.bin > > dfu-util -a rootfs -R -D qtmoko-debian-v35.ubi > > dfu-util -a u-boot -R -D qi-v35.udfu > > > I've got a Freerunner with no working NAND boot (ie pressing the Power > key does nothing). > I've just tried to put on v35 with those commands but still there is > no response from the Power key. > Booting from NOR results in > CRC error bad data Checksum > can't get kernel image > > I've tried a few installs of the kernel whose md5sum is > 907917848c8437f8f4126b8a971b06da uImage-v35.bin > > any help available? > > Liz > > I tried flashing the NAND with a few other bootloaders. What I have now is that pushing the Power key gives me NOR boot. I can boot an old Om2008 I've got here but after that I lost touchscreen input again Original QT was working last night - but I don't have a copy of that kernel and image any more. NOR boot can only boot off SD card if FAT + ext2 and so it can't read the debian on ext3 that I made. What options do I have to get qtmoko working? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Installing v35
On Mon, 31 Oct 2011 02:25:54 +1100 Philip Rhoades wrote: > I used: > > dfu-util -a kernel -R -D uImage-v35.bin > dfu-util -a rootfs -R -D qtmoko-debian-v35.ubi > dfu-util -a u-boot -R -D qi-v35.udfu I've got a Freerunner with no working NAND boot (ie pressing the Power key does nothing). I've just tried to put on v35 with those commands but still there is no response from the Power key. Booting from NOR results in CRC error bad data Checksum can't get kernel image I've tried a few installs of the kernel whose md5sum is 907917848c8437f8f4126b8a971b06da uImage-v35.bin any help available? Liz ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
