AM35xx booting for samsung 8 bit nand error???

Can you provide further details like,

 - Which x-loader and u-boot version you are using?

 - Steps/commands you are using to flash images?

 - Log?

Thanks,

Vaibhav

My x-load and u-boot version is u-boot.2011.09

is SDK 5.03.02.00

this is my mmc rooting log 

U-Boot SPL 2011.09 (Jan 13 2012 - 21)

Texas Instruments Revision detection unimplemented
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img


U-Boot 2011.09 (Jan 13 2012 - 21:26:25)

AM35XX-GP ES2.0, CPU-OPP2, L3-165MHz, Max CPU Clock 600 Mhz
AM3517EVM Board + LPDDR/NAND
I2C: ready
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: HW ECC [Kernel/FS layout] selected
512 MiB
MMC: OMAP SD/MMC: 0
In: serial
Out: serial
Err: serial
Die ID #415c0001000000000160ae2d0200b01a
Net: Ethernet PHY: GENERIC @ 0x00
DaVinci-EMAC
Hit any key to stop autoboot: 0 
AM3517_EVM # 

write MLO and u-boot.img to nand is this steps

AM3517_EVM # mmc rescan
AM3517_EVM # nand erase 0x0 0x280000

NAND erase: device 0 offset 0x0, size 0x280000
Skipping bad block at 0x00200000 
Skipping bad block at 0x00260000 

OK
AM3517_EVM # nandecc hw 2
HW ECC [X-loader/U-boot layout] selected
AM3517_EVM # fatload mmc 0 0x81000000 MLO
reading MLO

36728 bytes read
AM3517_EVM # nand write 0x81000000 0x0 0x20000

NAND write: device 0 offset 0x0, size 0x20000
 131072 bytes written: OK
AM3517_EVM # nand write 0x81000000 0x20000 0x20000

NAND write: device 0 offset 0x20000, size 0x20000
 131072 bytes written: OK
AM3517_EVM # nand write 0x81000000 0x40000 0x20000

NAND write: device 0 offset 0x40000, size 0x20000
 131072 bytes written: OK
AM3517_EVM # nand write 0x81000000 0x60000 0x20000

NAND write: device 0 offset 0x60000, size 0x20000
 131072 bytes written: OK
AM3517_EVM # fatload mmc 0 0x81000000 u-boot.img
reading u-boot.img

265752 bytes read
AM3517_EVM # nand write 0x81000000 0x80000 0x1E0000

NAND write: device 0 offset 0x80000, size 0x1e0000
Skip bad block 0x00200000
Skip bad block 0x00260000
 1966080 bytes written: OK
AM3517_EVM # 

this command is at document sitara-linuxsdk-sdg-05.03.02.00.pdf page 88

and my am3517_evm board can use this command booting for nand

but my board is not boot ....

is very strange...

At 0x260000 offset in NAND is where u-boot environment is stored and you have a bad block there.

Not sure what will happen.  I will look further into this Monday.

Regards,

Michael

thanks for reply

i setting the u-boot environment address to 0x220000, Situation is the same

and now , i change the nand ic to MT29F4G08ABADA ( 8 bit ), The problem is the same too , can read and write , but not boot in nand ...

When you say, it is not booting for you? Even x-loader is not coming up? Can you paste the boot log here?

Thanks,

Vaibhav

yes ,is not booting for nand... x-loader is not coming up!

if i booting for nand, not log print...

if i booting for mmc, this is log..

U-Boot SPL 2011.09 (Jan 16 2012 - 09:34:27)
Texas Instruments Revision detection unimplemented
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img


U-Boot 2011.09 (Jan 16 2012 - 09:34:27)

AM35XX-GP ES2.0, CPU-OPP2, L3-165MHz, Max CPU Clock 600 Mhz
AM3517EVM Board + LPDDR/NAND
I2C: ready
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: HW ECC [Kernel/FS layout] selected
512 MiB
MMC: OMAP SD/MMC: 0
In: serial
Out: serial
Err: serial
Die ID #205e0001000000000160ae2c0e015021
Net: No ETH PHY detected!!!
DaVinci-EMAC

Add a function to read nand id 
>>>>> data = 0x2C
>>>>> data = 0xDC
>>>>> data = 0x90
>>>>> data = 0x95
>>>>> data = 0x56
Hit any key to stop autoboot: 0 
reading boot.scr

457 bytes read
Running bootscript from mmc ...
## Executing script at 82000000
reading uImage

** Unable to read "uImage" from mmc 0:1 **
***** RootFS: /dev/mmcblk0p2 *****
## Booting kernel from Legacy Image at 82000000 ...
 Image Name: Execute uImage.bin
 Image Type: ARM Linux Script (uncompressed)
 Data Size: 393 Bytes = 393 Bytes
 Load Address: 00000000
 Entry Point: 00000000
 Contents:
 Image 0: 385 Bytes = 385 Bytes
 Verifying Checksum ... OK
Wrong Image Type for bootm command
ERROR: can't get kernel image!
AM3517_EVM # 

nand next, i write x-load and u-boot to nand

AM3517_EVM # mmc rescan
AM3517_EVM # nand erase 0x0 0x280000

NAND erase: device 0 offset 0x0, size 0x280000
Erasing at 0x260000 -- 100% complete.
OK
AM3517_EVM # saveenv
Saving Environment to NAND...
Erasing Nand...
Erasing at 0x220000 -- 100% complete.
Writing to Nand... done
AM3517_EVM # nandecc hw 2
HW ECC [X-loader/U-boot layout] selected
AM3517_EVM # fatload mmc 0 0x81000000 MLO
reading MLO

36728 bytes read
AM3517_EVM # nand write 0x81000000 0x0 0x20000

NAND write: device 0 offset 0x0, size 0x20000
 131072 bytes written: OK
AM3517_EVM # nand write 0x81000000 0x20000 0x20000

NAND write: device 0 offset 0x20000, size 0x20000
 131072 bytes written: OK
AM3517_EVM # nand write 0x81000000 0x40000 0x20000

NAND write: device 0 offset 0x40000, size 0x20000
 131072 bytes written: OK
AM3517_EVM # nand write 0x81000000 0x60000 0x20000

NAND write: device 0 offset 0x60000, size 0x20000
 131072 bytes written: OK
AM3517_EVM # fatload mmc 0 0x81000000 u-boot.img
reading u-boot.img

265840 bytes read
AM3517_EVM # nand write 0x81000000 0x80000 0x1E0000

NAND write: device 0 offset 0x80000, size 0x1e0000
 1966080 bytes written: OK
AM3517_EVM # 

and next, i try boot in nand ... x-load is not coming up, not log to print...