Re: [Gumstix-users] Problem booting latests Overo Earth COMs

[Francesco M. <fra...@mo...>]

Hi Steve,
U-Boot detect the NAND and display its size on the console, as you can see
from the following boot log extract

Gumstix installation:
------------------------------------------------------------------
Texas Instruments X-Loader 1.5.0 (Sep 16 2011 - 12:10:02)
OMAP3503-GP ES3.1.2
Board revision: 1
Loading u-boot.bin from nand


U-Boot 2010.09 (Oct 20 2010 - 10:11:49)

OMAP3503-GP ES3.1.2, CPU-OPP2, L3-165MHz, Max CPU Clock 600 mHz
Gumstix Overo board + LPDDR/NAND
I2C:   ready
DRAM:  512 MiB
NAND:  512 MiB
*** Warning - bad CRC or NAND, using default environment

In:    serial
Out:   serial
Err:   serial
Board revision: 1
Direct connection on mmc2
No EEPROM on expansion board
Die ID #04b6000700000000015154780d00e020
Net:   No ethernet found.
Hit any key to stop autoboot:  0
I2C read: I/O error
I2C read: I/O error
No MMC card found
Booting from nand ...

NAND read: device 0 offset 0x280000, size 0x400000
 4194304 bytes read: OK
## Booting kernel from Legacy Image at 82000000 ...
   Image Name:   Angstrom/2.6.34/overo
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3160068 Bytes = 3 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Custom setting (booting from MMC):
------------------------------------------------------------------
Texas Instruments X-Loader 1.4.4ss (Nov 15 2010 - 08:42:50)
OMAP3503-GP ES3.1.2
Board revision: 1
Reading boot sector
Loading u-boot.bin from mmc


U-Boot 2011.09 (Jun 20 2012 - 15:54:28)

OMAP3503-GP ES3.1.2, CPU-OPP2, L3-165MHz, Max CPU Clock 600 mHz
Gumstix Overo board + LPDDR/NAND
I2C:   ready
DRAM:  512 MiB
NAND:  512 MiB
MMC:   OMAP SD/MMC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Board revision: 1
Direct connection on mmc2
No EEPROM on expansion board
Die ID #04b6000700000000015154780d00e020
SpyDER #
SpyDER # setenv mmcboot 'if mmc rescan ${mmcdev}; then if run loaduimage;
then echo Booting from MMC ..'
SpyDER # run mmcboot
reading uImage

1967376 bytes read
Booting from MMC ...
## Booting kernel from Legacy Image at 82000000 ...
   Image Name:   Linux-2.6.34
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1967312 Bytes = 1.9 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...


And yes, the factory NAND image boots correctly.



2012/8/8 Steve Sakoman <sa...@gm...>

> On Wed, Aug 8, 2012 at 1:12 AM, Francesco Marletta
> <fra...@mo...> wrote:
>
> > The only (and blocking) problem is that my kernel is not able to find the
> > NAND chip.
>
> Forgive me for asking the obvious, but does u-boot detect and display
> the NAND size in the boot log?
>
> If so, do the COMs boot with the factory NAND image?
>
> Steve
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> gumstix-users mailing list
> gum...@li...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>



-- 
Francesco Marletta
Development Manager

Mobile: +39.3317332107
Email: fra...@mo...