Re: [Gumstix-users] How to initialize the NAND to factory default

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

like this:

@ @ @ D��`

--
Tiến Nguyễn

858-225-7372


On Wed, Aug 11, 2010 at 1:48 PM, colinfp <co...@be...> wrote:

>
> Hi,
>   I am assuming that the quoted section is from the good board? What does
> the bad board output?
>
>
>
>
> Tien Nguyen-3 wrote:
> >
> > Thanks so much for the explanation and I think I got what you said. Now
> in
> > my case, I am sure that I have a good MMC card with MLO, u-boot.bin and
> > uImage on it because I was able to boot up from MMC using one of my "good
> > device" as shown below. However, the same MMC install on the "bad device"
> > got stuck after a few garbage characters and the red LED light just stuck
> > there forever.
> >
> > I am willing to try anything before giving up on this.
> > Thanks,
> > -------
> > Texas Instruments X-Loader 1.4.2 (Jul  8 2009 - 21:19:00)
> > Reading boot sector
> > Error: reading boot sector
> > Loading u-boot.bin from nand
> >
> >
> > U-Boot 2009.11 (Aug 03 2010 - 20:58:22)
> >
> > OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz, Max clock-600Mhz
> > Gumstix Overo board + LPDDR/NAND
> > I2C:   ready
> > DRAM:  256 MB
> > NAND:  256 MiB
> > *** Warning - bad CRC or NAND, using default environment
> >
> > In:    serial
> > Out:   serial
> > Err:   serial
> > Board revision:  0
> > No EEPROM on expansion board
> > Die ID #28ce00040000000004035c141801a015
> > Net:   smc911x-0
> > Hit any key to stop autoboot:  0
> > mmc1 is available
> > reading boot.scr
> >
> > ** Unable to read "boot.scr" from mmc 0:1 **
> > reading uImage
> >
> > 3160220 bytes read
> > Booting from mmc ...
> > ## Booting kernel from Legacy Image at 82000000 ...
> >    Image Name:   Angstrom/2.6.34/overo
> >    Image Type:   ARM Linux Kernel Image (uncompressed)
> >    Data Size:    3160156 Bytes =  3 MB
> >    Load Address: 80008000
> >    Entry Point:  80008000
> >    Verifying Checksum ... OK
> >    Loading Kernel Image ... OK
> > OK
> >
> > Starting kernel ...
> >
> > -------
> > --
> > Tiến Nguyễn
> >
> >
> > On Wed, Aug 11, 2010 at 12:13 PM, colinfp <co...@be...> wrote:
> >
> >>
> >> Hi,
> >>   I think that an explanation of the boot process will help your
> >> understanding of the situation you are in.  Please forgive me if that is
> >> not
> >> true.  The following is what I have gathered.  I have learned this in
> >> reference to the beagleboard so some of the boot orders might be a
> little
> >> off.
> >>
> >> When you power on the overo the TM***** power manager chip is given
> >> power.
> >> This chip stabilizes a series of clocks and does some pin stuff.  Once
> >> things are stable, it starts a "power up" sequence for the OMAP
> >> processor.
> >> The OMAP has a little piece of memory with an elementary boot up script
> >> in
> >> it.  This script reads the status of a series of gpio pins to see what
> >> order
> >> it should try to look for external sources having the MLO and Uboot.
> >> These
> >> options are USB, UART, MMC, NAND etc.  The order that it looks at the
> >> sources differs for the Beagleboard and the Overo so I don't really know
> >> which is which.  But I am pretty sure that the processor tries to look
> on
> >> the MMC before the Nand.
> >>
> >> The existence of the OMAP bootscript means is that the system can not be
> >> bricked.  You can always get it to a point where you can upload the MLO.
> >> Once you get the MLO (i.e. X-loader) you can then get into the next
> >> bootloader (U-boot).  And from there boot into the kernel.
> >>
> >> So, it seems that you screwed up your nand somehow.  Putting the MLO and
> >> U-BOOT onto a correctly formatted MMC should allow the system to boot up
> >> to
> >> U-BOOT.  There are instructions for formatting MMC's etc all over the
> >> place.
> >> I recommend either the gumstix or pixhawk websites.  Once you are in the
> >> U-boot you can clean out all the nand and re-write the mlo and u-boot to
> >> it.
> >> There are tutorials on how to do that for the beagleboard.  Go to the
> >> beagleboard google groups and search for it.
> >>
> >> I hope that helps a bit.
> >>
> >> -Colin
> >> --
> >> View this message in context:
> >>
> http://old.nabble.com/How-to-initialize-the-NAND-to-factory-default-tp29402641p29411808.html
> >> Sent from the Gumstix mailing list archive at Nabble.com.
> >>
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> This SF.net email is sponsored by
> >>
> >> Make an app they can't live without
> >> Enter the BlackBerry Developer Challenge
> >> http://p.sf.net/sfu/RIM-dev2dev
> >> _______________________________________________
> >> gumstix-users mailing list
> >> gum...@li...
> >> https://lists.sourceforge.net/lists/listinfo/gumstix-users
> >>
> >
> >
> ------------------------------------------------------------------------------
> > This SF.net email is sponsored by
> >
> > Make an app they can't live without
> > Enter the BlackBerry Developer Challenge
> > http://p.sf.net/sfu/RIM-dev2dev
> > _______________________________________________
> > gumstix-users mailing list
> > gum...@li...
> > https://lists.sourceforge.net/lists/listinfo/gumstix-users
> >
> >
>
> --
> View this message in context:
> http://old.nabble.com/How-to-initialize-the-NAND-to-factory-default-tp29402641p29412673.html
> Sent from the Gumstix mailing list archive at Nabble.com.
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> gumstix-users mailing list
> gum...@li...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>