Re: FR won't boot without going into uboot menu first
nickd escreveu: > your splash.gz and maybe your uboot-env. I got both of a friend, which > worked, but apparently your uboot-env has a list of bad blocks in it > written at manufacturing time specifically for your phone. Debug board No, the bad block list is not on the u-boot environment. The bad block list is in a different hidden area, which doesn't show up as a partition and thus is a bit harder to damage (it's in the four "fake" bad blocks at the very end of the NAND flash). There's another "hidden" area, in the OOB bytes of the first NAND block, which points to the u-boot environment. If the partitioning is different (and the partitions are stored in the u-boot environment), it has to be adjusted to point to the u-boot environment (else u-boot cannot find it). For more details, take a look at http://wiki.openmoko.org/wiki/NAND_bad_blocks (which was written for the GTA01, but AFAIK the only relevant change for the GTA02 is the addition of the NOR flash and different partition sizes). -- Cesar Eduardo Barros [EMAIL PROTECTED] [EMAIL PROTECTED] ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: FR won't boot without going into uboot menu first
Yes this happened to me OP. I didn't pipe something into mtdblock but somehow I lost my NAND flash which contained the things Cesar listed below in the quote (uboot uboot-env spash etc). You'll have to reupload your splash.gz and maybe your uboot-env. I got both of a friend, which worked, but apparently your uboot-env has a list of bad blocks in it written at manufacturing time specifically for your phone. Debug board can do this but my way seemed to yield good results albeit any problems unaware to me. Best of luck! -Nick > There are another two partitions you would have to reflash, if you > really overwrote all of them. They are the splash partition (u-boot > splash image) and the u-boot environment partition (u-boot > configuration). Junk on the splash partition could be a good explanation > for the video noise and perhaps also the hang. The environment partition > can be rewritten from within u-boot itself. > > Resume (the other side of suspend) uses only a small part of u-boot > (which is why reflashing it fixed suspend/resume), so the other two > partitions being damaged wouldn't break it. > > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: FR won't boot without going into uboot menu first
Thorben Krueger escreveu: > My FreeRunner won't boot unless I hold down the AUX button while > powering up and select "boot" manually from the menu. This problem > started to appear when I had piped junk into all mtdblock devices on > my FR. (I had misinterpreted one of the wiki pages about images (the > instructions were intended for the host machine, not the FR itself)) > > I reflashed my FR with another image, but as the previously working > suspend was not doing so any more, I eventually decided to update > uboot. This solved my suspend issues somewhat but not the boot > problems. Yes, I also toyed with different uImages, to no avail. There are another two partitions you would have to reflash, if you really overwrote all of them. They are the splash partition (u-boot splash image) and the u-boot environment partition (u-boot configuration). Junk on the splash partition could be a good explanation for the video noise and perhaps also the hang. The environment partition can be rewritten from within u-boot itself. Resume (the other side of suspend) uses only a small part of u-boot (which is why reflashing it fixed suspend/resume), so the other two partitions being damaged wouldn't break it. -- Cesar Eduardo Barros [EMAIL PROTECTED] [EMAIL PROTECTED] ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: FR won't boot without going into uboot menu first
On Wednesday 03 September 2008 05:13:17 Thorben Krueger wrote: > My FreeRunner won't boot unless I hold down the AUX button while > powering up and select "boot" manually from the menu. This problem > started to appear when I had piped junk into all mtdblock devices on > my FR. (I had misinterpreted one of the wiki pages about images (the > instructions were intended for the host machine, not the FR itself)) So booting from NOR works but booting from NAND doesn't. Sounds like a uboot problem to me ... but I am guessing. Maybe try an older uboot image. What happens if you boot directly to NAND? If you don't know how, it is in the wiki somewhere. Sarton ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
FR won't boot without going into uboot menu first
My FreeRunner won't boot unless I hold down the AUX button while powering up and select "boot" manually from the menu. This problem started to appear when I had piped junk into all mtdblock devices on my FR. (I had misinterpreted one of the wiki pages about images (the instructions were intended for the host machine, not the FR itself)) I reflashed my FR with another image, but as the previously working suspend was not doing so any more, I eventually decided to update uboot. This solved my suspend issues somewhat but not the boot problems. Yes, I also toyed with different uImages, to no avail. So what does happen if I press the power button without AUX? After a few seconds, I get an AUX-button blink, a soft vibration (I like this actually) and at the same time, the display lights up, but instead of showing me any bootup screen, it displays the the contents of some video buffer (i.e. some random lines of noise or even the entire last screen contents before shutdown). Holding down the power button for any period of time at this stage yields nothing. I have to remove the battery. (Worries about backplate durability anyone?) Any suggestions? Thorben ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
