jffs2+mtd+big endian problem

Li Yang leoli at motorola.com
Thu Feb 5 04:59:27 EST 2004


On Thu, 2004-02-05 at 17:27, David Woodhouse wrote:
> On Thu, 2004-02-05 at 17:02 +0800, Li Yang wrote:
> > Search for id:(ff89 ffaa) interleave(2) type(2)
> > Search for id:(ff89 ffaa) interleave(2) type(2)
> > Search for id:(ff89 ffaa) interleave(2) type(2)
> > Search for id:(ff89 ffaa) interleave(2) type(2)
> > Search for id:(ff89 ffaa) interleave(2) type(2)
> > Search for id:(89 aa) interleave(2) type(1)
> 
> The 'sharp.c' driver handles four 8-bit chips in parallel. Your probes
> above aren't _looking_ for that. Did you enable the advanced CFI options
> and then disable 4-way interleave? 
Oh, yes.  I enabled the advanced CFI options, but not the CFI geometry
selection.  Because I saw there is a BIG_ENDIAN_BYTE option under it,
maybe I was a little bit too nervous about the endian setting. =)  I
will try again without the advanced CFI options.
> 
> > MTD jedec_match(): Check fit 0x00000000 + 0x00200000 = 0x00200000
> > MTD jedec_match(): check unlock addrs 0x0555 0x02aa
> > MTD jedec_match(): check ID's disappear when not in ID mode
> > MTD jedec_match(): return to ID mode
> > MTD jedec_probe_chip(): matched device 0x89,0xaa unlock_addrs: 0x0555
> > 0x02aa
> > Found: Intel I28F016S3
> > Flash SIMM: Found 2 x8 devices at 0x0 in 32-bit mode
> > Probe at addr_unlock2(0x00400000 + 0xc0185aac) past the end of the
> > map(0x007fffff)
> 
> That's odd too. What is that pointer doing in addr_unlock2? Possibly not
> relevant though.
They are just baffling numbers to me.

-- 
Li Yang <leoli at motorola.com>
Metrowerks




More information about the linux-mtd mailing list