Dont know if can be a hardware problem, cause NAND is found in localbus:
I just copy/paste nand_scan code (from nand_base.c) and try this:
With u-boot-1.1.4 + drivers from u-boot-1.3.4:
DDR RAM: 128 MB FLASH: 16 MB In: serial Out: serial Err: serial NAND: 64 MiB
=> nand scan
Maf. ID: 0x00 - Dev. ID: 0x00 => nand scan
Maf. ID: 0x20 - Dev. ID: 0x76 => nand scan
Maf. ID: 0x00 - Dev. ID: 0x00 => nand scan
Maf. ID: 0x20 - Dev. ID: 0x76
Maf. ID: 0x20, Dev. ID: 0x76: the right nand, NAND512W3A2BN6E from STMICRO
And if I use another command like "nand bad", then I got just 0x00 in all other "nand scan" commands.
Now with u-boot-1.1.4 + drivers from first upm release:
DDR RAM: 128 MB FLASH: 16 MB In: serial Out: serial Err: serial NAND: 64 MiB
=> nand scan
Maf. ID: 0x00 - Dev. ID: 0x00 => nand scan
Maf. ID: 0x00 - Dev. ID: 0x00 => nand scan
Maf. ID: 0x00 - Dev. ID: 0x00 => nand scan
Maf. ID: 0x00 - Dev. ID: 0x00
0x00 in all tries.
Each version cause a different behavior, so not sure if can be hardware
Cheers,
-- Alemao On Wed, Aug 13, 2008 at 11:44 AM, Stefan Roese sr@denx.de wrote:
On Wednesday 13 August 2008, Alemao wrote:
Now i got all NAND stuffs from u-boot-1.3.4, including common/cmd_nand.c and drivers/mtd/nand/*, but still the same problem.
Other components of u-boot can influence NAND behavior?
I saw some people with similar problem using "nand scrub", but im little bit afraid with this command...
Yes, you should be. Be careful with this command.
Note that in all cases where I read all NAND blocks as bad, either the NAND driver had a problem or the hardware had a problem. Are you sure that the hardware is ok?
Best regards, Stefan
===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office@denx.de =====================================================================