[U-Boot] [RFC/PATCH] jffs2/mtdparts: Fix problem with usage from JFFS2 and MTDPARTS together
Wolfgang Denk
wd at denx.de
Sun May 24 23:10:24 CEST 2009
Dear Stefan Roese,
In message <200905201201.50810.sr at denx.de> you wrote:
>
> > => fsinfo
> > ### filesystem type is JFFS2
> > Scanning JFFS2 FS: read_nand_cached: error reading nand off 0xabfe00 size
> > 8192 bytes read_nand_cached: error reading nand off 0xadfe00 size 8192
> > bytes
> > read_nand_cached: error reading nand off 0xac0000 size 8192 bytes
> > read_nand_cached: error reading nand off 0xaffe00 size 8192 bytes
>
> <snip>
>
> > The addresses where the read errors occur don't seem to be related to
> > the bad blocks reported by Linux.
>
> No. What does a "normal" "nand read" return when reading this complete
> partition into RAM? On PPC4xx it returned -117 here. I fixed it with the
> already posted patches for the 4xx NDFC ECC byte ordering. Perhaps the TQM8548
> has similar incompatibility issues with the Linux kernel here too?
I get this:
=> nand read 200000 0 1000000
NAND read: device 0 offset 0x0, size 0x1000000
NAND read from offset 0 failed -74
16777216 bytes read: ERROR
Hm, this is indeed a very helpful message. What does it tell you? I
can't parse that. May we please have more readable error messages from
the NAND code? Please?!
Is this -74 decimal as EBADMSG or -0x74 = NAND_CMD_STATUS_ERROR1 ?
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Being schizophrenic is better than living alone.
More information about the U-Boot
mailing list