Hi,
Continuing with NAND problems...
I replaced:
#define CFG_LCRR (LCRR_DBYP | LCRR_CLKDIV_4)
by:
#define CFG_LCRR (LCRR_DBYP | LCRR_CLKDIV_8)
And now I can read and there is only one bad block, but no erase or write yet:
(I checked WP and its correct, 3.3V)
=> nand read.jffs2 0x02
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
Ma
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
When I had discovered that my NAND flash had all bad blocks, I found a
patch to dump the NAND blocks (which I think you had said you did). What
I found in my case was that on one board 8 data lines were disconnected
and on another one of the 0 ohm resistors was faulty (so one bit was
always read as
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...
Another th
Alemao wrote:
> Hi all,
>
> Im trying to use my NAND flash at MPC8360E-RDK based board.
> But it seems that the whole chip is bad blocked.
> Dont know if Im missing something... below some outputs:
Odds are that something is broken in the NAND driver, and you're reading
garbage.
> Any help/sugg
Hi all,
Im trying to use my NAND flash at MPC8360E-RDK based board.
But it seems that the whole chip is bad blocked.
Dont know if Im missing something... below some outputs:
=> nand info
Device 0: NAND 64MiB 3,3V 8-bit, sector size 16 KiB
=> nand bad
4000
.
.
.
03ff4
7 matches
Mail list logo
