Re: I/O problems with SD card
2008/11/24 Nikita V. Youshchenko [EMAIL PROTECTED]: Yes, I know that, but I'm unable to connect to the phone through DFU protocol because Neo don't offer itself as a device supporting DFU. Have you tried to connect usb cable AFTER freerunner started NOR u-boot? I haven't; will do that later at home since I have neither phone nor Linux box here at work... Thanks for the hint. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: I/O problems with SD card
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | 2008/11/24 Nikita V. Youshchenko [EMAIL PROTECTED]: |Yes, I know that, but I'm unable to connect to the phone through | DFU protocol because Neo don't offer itself as a device supporting | DFU. | Have you tried to connect usb cable AFTER freerunner started NOR u-boot? | |I haven't; will do that later at home since I have neither phone | nor Linux box here at work... Thanks for the hint. My early problems with DFU disappeared after I took this approach in a script, it seems it can announce under two different PIDs (this one is for updating U-Boot): #!/bin/bash dfu-util -a 1 -d 0x1d50:0x5119 -D u-boot.udfu if [ $? -eq 1 ] ; then dfu-util -a 1 -d 0x1d50:0x5120 -D u-boot.udfu dfu-util -a 1 -d 0x1d50:0x5119 -D u-boot.udfu fi - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkkqbFgACgkQOjLpvpq7dMp+CACeLhIe8mB/48vnksV/ThM75V7V m2oAnRdtakyxkEgnDiDyDYRpHbLwTnJs =U+2O -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: I/O problems with SD card
Hi, Evgeny Karyakin [EMAIL PROTECTED] writes: 2008/11/24 Andy Green [EMAIL PROTECTED]: I'm not sure what's happening to you, but your dmesg traffic would be pretty normal if you were entering and then leaving U-Boot... the connection would indeed timeout (-110) when we leave U-Boot and load the kernel / crash or whatever. If you hold down the AUX / corner key when you power up, you should come up in NOR U-Boot with a menu on the LCM. If that's true, you should have 30s to do the DFU you want to do before it times out. Yes, I know that, but I'm unable to connect to the phone through DFU protocol because Neo don't offer itself as a device supporting DFU. I have Neo plugged in to desktop throught USB cable. AUX+POW gives me NOR boot menu and at the same time Neo must be visible to desktop as DFU-capable device within next 30 seconds, but it's not. It might be a silly suggestion but please double-check the usb cable used, try to connect directly to the motherboard (avoid front-panel connectors and usb hubs). May be you should try another PC. By no means (as you have no dboard) you could have damaged the NOR bootloader by dfu-util. It should just work. The battery must be charged before the flashing (you can even use any full-charged Nokia battery). Try removing the battery for some time (to ensure clean boot), then boot directly into the NOR uBoot, connect to PC and try to flash. If it doesn't work, use another cable/usb port/pc. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:[EMAIL PROTECTED] ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: I/O problems with SD card
2008/11/24 Andy Green [EMAIL PROTECTED]: My early problems with DFU disappeared after I took this approach in a script, it seems it can announce under two different PIDs (this one is for updating U-Boot): #!/bin/bash dfu-util -a 1 -d 0x1d50:0x5119 -D u-boot.udfu if [ $? -eq 1 ] ; then dfu-util -a 1 -d 0x1d50:0x5120 -D u-boot.udfu dfu-util -a 1 -d 0x1d50:0x5119 -D u-boot.udfu fi I'll try this as well, thanks, although listing of any connected DFU devices with dfu-util -l outputs nothing, which means desktop doesn't see Freerunner at all. I'll try Nikita's advice on connecting USB cable after starting NOR u-boot. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: I/O problems with SD card
2008/11/24 Paul Fertser [EMAIL PROTECTED]: It might be a silly suggestion but please double-check the usb cable used, try to connect directly to the motherboard (avoid front-panel connectors and usb hubs). May be you should try another PC. By no means (as you have no dboard) you could have damaged the NOR bootloader by dfu-util. It should just work. The battery must be charged before the flashing (you can even use any full-charged Nokia battery). Try removing the battery for some time (to ensure clean boot), then boot directly into the NOR uBoot, connect to PC and try to flash. If it doesn't work, use another cable/usb port/pc. This might also be the cause of it, I'll check, thanks. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: I/O problems with SD card
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | 2008/11/24 Andy Green [EMAIL PROTECTED]: | My early problems with DFU disappeared after I took this approach in a | script, it seems it can announce under two different PIDs (this one is | for updating U-Boot): |I'll try this as well, thanks, although listing of any connected | DFU devices with dfu-util -l outputs nothing, which means desktop It means there was nothing seen with the VID/PID it was looking for, but the script tries both that can be told by U-Boot. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkkqdPoACgkQOjLpvpq7dMqyfACgjNNzXXxOGEXGr3meyZSYlIIL izEAmQG7bJoAuU6nFYybGnuSMjfDSGhR =FOPj -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: I/O problems with SD card
Yes, I know that, but I'm unable to connect to the phone through DFU protocol because Neo don't offer itself as a device supporting DFU. Have you tried to connect usb cable AFTER freerunner started NOR u-boot? ... My early problems with DFU disappeared after I took this approach in a script, it seems it can announce under two different PIDs (this one is for updating U-Boot): #!/bin/bash dfu-util -a 1 -d 0x1d50:0x5119 -D u-boot.udfu if [ $? -eq 1 ] ; then dfu-util -a 1 -d 0x1d50:0x5120 -D u-boot.udfu dfu-util -a 1 -d 0x1d50:0x5119 -D u-boot.udfu fi ... It might be a silly suggestion but please double-check the usb cable used, try to connect directly to the motherboard (avoid front-panel connectors and usb hubs). May be you should try another PC. By no means (as you have no dboard) you could have damaged the NOR bootloader by dfu-util. It should just work. The battery must be charged before the flashing (you can even use any full-charged Nokia battery). Try removing the battery for some time (to ensure clean boot), then boot directly into the NOR uBoot, connect to PC and try to flash. If it doesn't work, use another cable/usb port/pc. Thanks you all, Andy, Nikita and Paul, now I have the phone working again. I used all your suggestions in complex, use another USB port on desktop, connect Freerunner to notebook after it's in NOR boot menu state, and flashed the phone using -d dfu-util option. It finished successfully. Still don't know what caused that troubles with DFU recognition failures. I have to be careful in the future while doing low-level manipulations with Neo like environment changes. Thanks, your help was invaluable! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Re: I/O problems with SD card
On Nov 23, 2008 8:12pm, Andy Green [EMAIL PROTECTED] wrote: Recent kernels have a workaround in that starts the card at slower clock until the first bulk transfer completed successfully when it is cranked up to 16MHz, that seemed to make the previous problems with some cards pretty much go away. Presumably these recent kernels aren't in 2008.9. Is there any way of getting them without getting testing versions of everything else? Regards Jeff ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: I/O problems with SD card
jewgeni, seems you experience the well known sd card issue. wiki and/or archives should offer a lot of postings on the issue. it boils down to setting sd_max_clk -- in your case in the nand boot environment since your fr seems unable to boot from sd at all. searching for sd_max_clk +openmoko should give you sufficient enough hits. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: I/O problems with SD card
seems you experience the well known sd card issue. wiki and/or archives should offer a lot of postings on the issue. it boils down to setting sd_max_clk -- in your case in the nand boot environment since your fr seems unable to boot from sd at all. searching for sd_max_clk +openmoko should give you sufficient enough hits. Thanks for suggestion, I've found a lot of information on this. Now I have a disaster... Trying to follow http://docs.openmoko.org/trac/ticket/1743#comment:5 I entered /dev/ttyACM0 console and redefined bootcmd environment variable through minicom terminal emulator. Something went wrong -- I don't know what step caused it -- and since then Neo could still boot from NAND (kernel + rootfs) but couldn't be reflashed, it says something like writing past memory available, I guess it's because broken environment. I've found some promising info about Factory reset, but it wasn't in my NAND boot menu. Bad. Next I found Devirginator which promises to do that reset another way. One of the steps described in http://wiki.openmoko.org/wiki/Bootloader says that I need to make a shot of current env before modifying it writing it back in place. So I issued dfu-util -a u-boot_env -R -U env.in and this was the end. dfu-util said that no DFU device is present and exit. Now Neo can't even be seen as DFU device from my notebook. Although Freerunner boots its current software version, FSO milestone 4. What next? Resort to http://wiki.openmoko.org/wiki/Bricked or search for a guy with Debug board or ...? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: I/O problems with SD card
like writing past memory available, I guess it's because broken environment. hardly. i'd rather think you try to flash the wrong partition. what exactly did you do and what exactly did dfu-util or the fr report? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: I/O problems with SD card
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | seems you experience the well known sd card issue. | wiki and/or archives should offer a lot of postings on the issue. | it boils down to setting sd_max_clk -- in your case in the nand boot environment since your fr seems | unable to boot from sd at all. | searching for sd_max_clk +openmoko should give you sufficient enough hits. | |Thanks for suggestion, I've found a lot of information on this. |Now I have a disaster... Trying to follow | http://docs.openmoko.org/trac/ticket/1743#comment:5 I entered | /dev/ttyACM0 console and redefined bootcmd environment variable | through minicom terminal emulator. Something went wrong -- I don't If it's a Freerunner, just hold down that corner AUX button when you power on, you should get into a backup NOR copy of U-Boot and can DFU new stuff in from there. If you still get errors, post your dfu-util commandline. For the original problem, actually my first suspect would be physical connectivity to the fingers in the uSD connector. A guy before found he had to add some paper on top of the SIM to push down enough to make reliable contact. Recent kernels have a workaround in that starts the card at slower clock until the first bulk transfer completed successfully when it is cranked up to 16MHz, that seemed to make the previous problems with some cards pretty much go away. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkkpqzYACgkQOjLpvpq7dMro/wCbB8ruZlgL6eYIEhXWSK+i45yj SUEAoI12TXFYY8DpIHqlijhixSnyBlj9 =4O3A -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: I/O problems with SD card
2008/11/23 Andy Green [EMAIL PROTECTED]: Recent kernels have a workaround in that starts the card at slower clock until the first bulk transfer completed successfully when it is cranked up to 16MHz, that seemed to make the previous problems with some cards pretty much go away. Presumably these recent kernels aren't in 2008.9. Is there any way of getting them without getting testing versions of everything else? Regards Jeff ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: I/O problems with SD card
From: arne anka [EMAIL PROTECTED] like writing past memory available, I guess it's because broken environment. hardly. i'd rather think you try to flash the wrong partition. what exactly did you do and what exactly did dfu-util or the fr report? I already flashed Freerunner several times before with dfu-util -a u-boot -R -D uImage-XX.bin with no troubles, last time I tried uImage-2.6.24+r10+gitr6e2a723ef54ee2e739c34786981b2c508db803c1-r10-om-gta02.bin which is 1895768 bytes long so there shouldn't be a problem here. dfu-util now can't even locate GTA02 when it's in NOR menu state. dfu-util -l says nothing, and dmesg has this: [20575.933963] usb 3-1.4: new full speed USB device using ehci_hcd and address 36 [20582.407633] usb 3-1.4: new full speed USB device using ehci_hcd and address 37 [20588.431796] usb 3-1.4: device descriptor read/64, error -110 [20595.195357] usb 3-1.4: device descriptor read/64, error -110 [20595.335909] usb 3-1.4: new full speed USB device using ehci_hcd and address 38 [20601.865524] usb 3-1.4: new full speed USB device using ehci_hcd and address 39 [20608.656191] usb 3-1.4: device descriptor read/64, error -110 [20616.763672] usb 3-1.4: device descriptor read/64, error -110 [20616.838742] usb 3-1.4: new full speed USB device using ehci_hcd and address 40 [20623.245361] usb 3-1.4: device descriptor read/64, error -110 [24031.580522] usb 3-1.4: new full speed USB device using ehci_hcd and address 41 [24038.054249] usb 3-1.4: new full speed USB device using ehci_hcd and address 42 [24044.080009] usb 3-1.4: device descriptor read/64, error -110 [24050.142505] usb 3-1.4: device descriptor read/64, error -110 [24050.214373] usb 3-1.4: new full speed USB device using ehci_hcd and address 43 [24066.486002] usb 3-1.4: new full speed USB device using ehci_hcd and address 44 and many other lines related to it, so I'm sure I'm bricked. DFU functionality disappeared right after I tried to take a snapshot of u-boot environment with dfu-util -a u-boot_env -R -U env.bin From: Andy Green [EMAIL PROTECTED] If it's a Freerunner, just hold down that corner AUX button when you power on, you should get into a backup NOR copy of U-Boot and can DFU new stuff in from there. If you still get errors, post your dfu-util commandline. I'm in NOR menu already (see above) and dfu-util says that it writes u-boot piece past memory. Now thanks God all I have is working FSO m4 from where I can do something with this situation. For the original problem, actually my first suspect would be physical connectivity to the fingers in the uSD connector. A guy before found he had to add some paper on top of the SIM to push down enough to make reliable contact. Recent kernels have a workaround in that starts the card at slower clock until the first bulk transfer completed successfully when it is cranked up to 16MHz, that seemed to make the previous problems with some cards pretty much go away. I'm glad to hear it. It may be a good idea to have a backup rock-solid bare copy of working firmware somewhere inside Neo to restore it in such cases, although that tempting Factory reset option may be exactly what I'm talking about. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: I/O problems with SD card
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | From: arne anka [EMAIL PROTECTED] | | like writing past memory available, I guess it's because broken | environment. | hardly. i'd rather think you try to flash the wrong partition. | what exactly did you do and what exactly did dfu-util or the fr report? | |I already flashed Freerunner several times before with | | dfu-util -a u-boot -R -D uImage-XX.bin Hum the -a u-boot or -a 1 tells it to put stuff in the U-Boot partition, it's the wrong one: uImage-blah.bin is a kernel image. To flash the kernel, you need to tell it -a kernel or -a 3. To fix it you need to put a U-Boot image into the u-boot partition again. |and many other lines related to it, so I'm sure I'm bricked. DFU | functionality disappeared right after I tried to take a snapshot of | u-boot environment with | | dfu-util -a u-boot_env -R -U env.bin Why do you think it's bricked? The NOR menu comes up OK on LCM, right? - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkkpy+AACgkQOjLpvpq7dMog3wCfYFRcSsf+C+R5OA9KZG/+v8qu n2cAn15MsGAJJFAdBdJNksAOg9+hKN6d =pMrT -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: I/O problems with SD card
2008/11/24 Andy Green [EMAIL PROTECTED]: | dfu-util -a u-boot -R -D uImage-XX.bin Hum the -a u-boot or -a 1 tells it to put stuff in the U-Boot partition, it's the wrong one: uImage-blah.bin is a kernel image. To flash the kernel, you need to tell it -a kernel or -a 3. Ah yes, missed that, I write it by memory. To fix it you need to put a U-Boot image into the u-boot partition again. Why do you think it's bricked? The NOR menu comes up OK on LCM, right? DFU is absent, dfu-util -l finds no suitable device to work with, maybe because I damaged it when I changed environment in minicom console or I uploaded wrong image onto that. AUX+POW on the phone, menu appears, dfu-util -l on desktop, and no DFU device found. I know no other way of flashing new u-boot image without DFU protocol working, except Debug board which I haven't. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: I/O problems with SD card
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | 2008/11/24 Andy Green [EMAIL PROTECTED]: | | dfu-util -a u-boot -R -D uImage-XX.bin | | Hum the -a u-boot or -a 1 tells it to put stuff in the U-Boot | partition, it's the wrong one: uImage-blah.bin is a kernel image. | To flash the kernel, you need to tell it -a kernel or -a 3. | |Ah yes, missed that, I write it by memory. | | To fix it you need to put a U-Boot image into the u-boot partition again. | Why do you think it's bricked? The NOR menu comes up OK on LCM, right? | |DFU is absent, dfu-util -l finds no suitable device to work with, | maybe because I damaged it when I changed environment in minicom | console or I uploaded wrong image onto that. AUX+POW on the phone, | menu appears, dfu-util -l on desktop, and no DFU device found. |I know no other way of flashing new u-boot image without DFU | protocol working, except Debug board which I haven't. I'm not sure what's happening to you, but your dmesg traffic would be pretty normal if you were entering and then leaving U-Boot... the connection would indeed timeout (-110) when we leave U-Boot and load the kernel / crash or whatever. If you hold down the AUX / corner key when you power up, you should come up in NOR U-Boot with a menu on the LCM. If that's true, you should have 30s to do the DFU you want to do before it times out. =Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkkp0tkACgkQOjLpvpq7dMqT8ACeOHz4I52jvyHmAohEwymwTacD aiwAmwfNZTIxBkA/Dx79gHkWGjaQZ8iD =iJ8e -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: I/O problems with SD card
2008/11/24 Andy Green [EMAIL PROTECTED]: |DFU is absent, dfu-util -l finds no suitable device to work with, | maybe because I damaged it when I changed environment in minicom | console or I uploaded wrong image onto that. AUX+POW on the phone, | menu appears, dfu-util -l on desktop, and no DFU device found. |I know no other way of flashing new u-boot image without DFU | protocol working, except Debug board which I haven't. I'm not sure what's happening to you, but your dmesg traffic would be pretty normal if you were entering and then leaving U-Boot... the connection would indeed timeout (-110) when we leave U-Boot and load the kernel / crash or whatever. If you hold down the AUX / corner key when you power up, you should come up in NOR U-Boot with a menu on the LCM. If that's true, you should have 30s to do the DFU you want to do before it times out. Yes, I know that, but I'm unable to connect to the phone through DFU protocol because Neo don't offer itself as a device supporting DFU. I have Neo plugged in to desktop throught USB cable. AUX+POW gives me NOR boot menu and at the same time Neo must be visible to desktop as DFU-capable device within next 30 seconds, but it's not. That's why I (may be erroneously) call myself bricked -- I can boot Neo with it's currently installed software (FSO m4) but I can't update it's NAND to anything else since the moment I damaged(?) u-boot. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: I/O problems with SD card
If you hold down the AUX / corner key when you power up, you should come up in NOR U-Boot with a menu on the LCM. If that's true, you should have 30s to do the DFU you want to do before it times out. Yes, I know that, but I'm unable to connect to the phone through DFU protocol because Neo don't offer itself as a device supporting DFU. Have you tried to connect usb cable AFTER freerunner started NOR u-boot? signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
I/O problems with SD card
Hello!
This is my first time of booting from MicroSD card since before
this time I flashed several distributions onto internal flash. I
downloaded FSO milestone 4.1 and put that on Transcend 2Gb flash: made
two partitions, kernel 2Mb vfat and remaining for rootfs ext2,
formatted it accordingly (mkfs vfat and ext2) and copied file on them,
that means, followed http://wiki.openmoko.org/wiki/Booting_from_SD
instructions. Nevertheless booting from SD failed, I chose a
corresponding menu item from NOR loader (load from SD fat+ext2) and
started to receive multiple error messages:
# right after load start
s3c2410_udc: debugfs dir creation failed -19
# next lines mixed with each other
mmcblk0: error -110 sending read/write command
EXT2-fs error (device mmcblk0p2) ex2_get_inode: unable to read inode
block - inode=12345 block=67890
Buffer I/O error on device mmcblk0p2, logical block 0
# and partial success messages among them
Plus multiple Input/Output errors while reading /etc/rc.d/* files
and writing to /etc/volatile or something.
This is how Freerunner sees my card:
Card type: SD 2.0
Manufacturer: 0x1b, OEM SM
Product name: 0, revision 1.0
Serial number: 1234567890
Manufacturing date: 7/2008
MMC/SD size: 511 MiB
Thinking a card may be broken, I did check all files on it like that:
find /mnt -depth -type f -exec md5sum \{\} \;
And several files resulted in Input/Output errors. Aha! Then I
initialized my card with
dd if=/dev/urandom of=/dev/mmcblk0p2 bs=32768 count=62150
Then issued mkfs again and untarred rootfs second time. Checked
again -- none of the files reported an error. Still Neo can't read
many files on a card, especially in /etc/ . All SD card preparation
operations were made on a notebook with built-in card reader.
Does anybody experienced any troubles with MicroSD cards like the
abovementioned ones?
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
