From: Gerhard H. <Ger...@pe...> - 2011-09-12 13:29:48
|
Hello, I have got a problem when I flash may overos + tobi with an image from last year based on 20100803 but with some additional packages installed (jamvm classpath rxtx ...) and some additional configurations. In the meantime I ordered some new overos and tobis (with the Standard USB A Host conector). When I write this image to the flash and run it for some minutes everything is fine. When trying to reboot removing the Power for a short time it hangs during/before the XLoader is loaded. Sometimes only the magic char are printed at the console "@ @QT,0 @�" but sometimes (not so often) also X-Loader starts and ends with: --- snip Texas Instruments X-Loader 1.4.2 (Aug 3 2010 - 20:56:28) Reading boot sector Error: reading boot sector X-Loader hangs ------- After waiting 10 Min everything is running fine again. When I run this image from an uSD card (where the same card makes problems on an already flashed overo) on an overo not touched (still with the factory image) the reboot makes no problems at all. Does anybody have an idea what could be the problem? Maybe some wrong procedure during flashing? E.g. I compared the script I used for flashing with the current from http://www.gumstix.org/how-to/70-writing-images-to-flash.html and there is one difference: instead of: echo "Erasing and formatting rootfs partition ..." flash_eraseall /dev/mtd4 mkfs.jffs2 -o /dev/mtdblock4 in my script just echo "Erasing and formatting rootfs partition ..." flash_eraseall -j /dev/mtd4 is executed - must have been different in the past. Or are the version incompatible (I didn't update the X-Loader (MLO), just U-Boot, the Kernal and the root FS)?. My versions on the Board with the described issue are: * X-Loader 1.4.4ss (Oct 20 2010 - 10:10:28) * U-Boot 2009.11 (Aug 03 2010 - 20:58:22) * Linux version 2.6.34 (st...@ww...) (gcc version 4.3.3 (GCC) ) #1 Tue Aug 3 21:03:43 PDT 2010 Thanks for any help or remark in advance Gerhard -- View this message in context: http://old.nabble.com/overo%2Btobi-doesn%27t-boot-again-after-running-some-time-tp32447905p32447905.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Gerhard H. <Ger...@pe...> - 2011-09-27 17:27:47
|
Hello again, in the meantime I did many tests, but had no success with my tobi/overos (PF3503-R2889/PCB30002-R2783; bought in April 2011) till now. Only flashing my prepared image to the older overo/tobi (PF3503-R2277/PCB30002-R2411) makes no problems at all. I tried already to reflash the current factory image http://cumulus.gumstix.org/images/angstrom/factory/2011-08-30-1058/ or the console version from http://cumulus.gumstix.org/images/angstrom/developer/2011-08-30-1058/ I do not get rid of may bootup problem after removing the power for some seconds any more. Even starting with different bootable uSD cards ... the bootup problem exists. I tried to reflash another "new" overo. There the problem didn't occure. So it seems to me that it is not a systematic problem. It happened just during my flash procedure. Nevertheless I would like to get rid of may power on/off issue of the first overo. Did anybody have a similar problem and solved it somehow? Any ideas? Thanks in advance Gerhard -- View this message in context: http://old.nabble.com/overo%2Btobi-doesn%27t-boot-again-after-running-some-time-tp32447905p32536066.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Ash C. <as...@gu...> - 2011-09-28 18:08:44
|
Hi Gerhard, Let's see if I get this summary right: - after flashing, some older boards would fail to boot past MLO (mixed versions of u-boot & x-load) - you purchased some new boards and now you see the issue even with microSD boot with a factory image - the booting issue are intermittent Is this a good summary? On Tue, Sep 27, 2011 at 10:27 AM, Gerhard H. <Ger...@pe...> wrote: > Nevertheless I would like to get rid of may power on/off issue of the first > overo. > Did anybody have a similar problem and solved it somehow? > Any ideas? Can you try using this combo http://feeds.sakoman.com/feeds/gnome-r13/images/overo/current/ of x-load and u-boot? This may not boot the kernel 100% but I expect it to get into u-boot 100% of the time running either from flash or from microSD card. -Ash |
From: Gerhard H. <Ger...@pe...> - 2011-10-03 17:41:15
|
Hi Ash, thank you for your help Ash Charles-2 wrote: > > Let's see if I get this summary right: > - after flashing, some older boards would fail to boot past MLO (mixed > versions of u-boot & x-load) > - you purchased some new boards and now you see the issue even with > microSD boot with a factory image > - the booting issue are intermittent > Is this a good summary? > almost excellent ;-) * finally I came to to point that may boot issue (removing the power supply for some seconds) occured only on one HW (tobi+over) of new generation (PF3503-R2889/PCB30002-R2783) ** that's the HW I want to focus any more ** came in the wrong direction because my friend told me that the same issue occures also on our 2nd new tobi/over board, but it wasn't * it started to make problems after may first flash procedure * we never had the issue on the old HW Version sorry for wrong pointers. I planned to test your MLO and U-Boot binaries right now, but the NAND Flash cannot be found (or accessed) any more. Got the following boot outputs booting with an uSD card: -- snip -- �tصb�$U @D�� � Texas Instruments X-Loader 1.5.0 (Aug 29 2011 - 12:52:49) No NAND detected OMAP3503-GP ES3.1 Board revision: 0 Reading boot sector Loading u-boot.bin from mmc U-Boot 2010.12 (Aug 22 2011 - 09:49:35) OMAP3503-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 600 mHz Gumstix Overo board + LPDDR/NAND I2C: ready DRAM: 256 MiB NAND: nand_get_flash_type: unknown NAND device: Manufacturer ID: 0xc0, Chip ID: 0xc0 0 MiB MMC: OMAP SD/MMC: 0 *** Warning - readenv() failed, using default environment .... -- snip -- X-Loader says No NAND Detected and Uboot says unknown NAND device. Booting from NAND is not possible at all any more. Just the magic characters are printed at the console - similar as during my boot issue. But my boot issue is gone using the MMC now. I think I will try to reflash once more. Do you think that this is a good idea? Can not get worse! The question is if it is a HW NAND issue or something went wrong during my first flash procedure? Will find some time on Thursday Gerhard -- View this message in context: http://old.nabble.com/overo%2Btobi-doesn%27t-boot-again-after-running-some-time-tp32447905p32583916.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Ash C. <ash...@gm...> - 2011-10-05 16:41:34
|
Hi Gerhard, On Mon, Oct 3, 2011 at 10:41 AM, Gerhard H. <Ger...@pe...> wrote: > Booting from NAND is not possible at all any more. Just the magic characters > are printed at the console - similar as during my boot issue. > But my boot issue is gone using the MMC now. > I think I will try to reflash once more. Do you think that this is a good > idea? Can not get worse! > The question is if it is a HW NAND issue or something went wrong during my > first flash procedure? It could be one of two situations: 1. Hardware issue either with the NAND or the processor 2. Some flashing issue (either bad code was flashed or the data on the flash got corrupted (nand scrub in u-boot does a good job of cleaning) I'd recommend first getting a microSD boot (this way, the status of the flash doesn't matter) and then cleaning the nand completely before reflashing. -Ash |
From: Rob <rbr...@gm...> - 2011-11-15 14:05:24
|
What was the solution here? I am having exactely the same problem with my overo (with no tobi) as described here. Any solutions? If not then I can provide some more debug information. /Rob |
From: JoeWoodward <jw...@te...> - 2011-11-15 14:44:34
|
This may not be useful, or relevant... But I've seen Overo's sometimes fail to boot since the following commit to x-loader: Friday January 28 2011 sakoman committed 24b8b7f overo: Fix bug in prcm_init Since reverting this commit I've never had a board fail to boot. I always boot from an SDCard, and the symptoms of a failed boot are that x-loader doesn't print anything to the terminal. This happens maybe once in a few dozen boots. Rob-162 wrote: > > What was the solution here? I am having exactely the same problem with my > overo > (with no tobi) as described here. > > Any solutions? If not then I can provide some more debug information. > > /Rob > > > > ------------------------------------------------------------------------------ > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://old.nabble.com/overo%2Btobi-doesn%27t-boot-again-after-running-some-time-tp32447905p32847940.html Sent from the Gumstix mailing list archive at Nabble.com. |