[U-Boot] Non standard CFI detection tweaks

[Stefan Roese]

On Monday 19 July 2010 14:18:37 Rogan Dawes wrote:
> DNS323B1> mw.w ff800aaa 00aa
> DNS323B1> mw.w ff800554 0055
> DNS323B1> mw.w ff800aaa 0090
> DNS323B1> md.w ff800000
> ff800000: 0000 0000 0000 0000 0000 0000 0000 0000    ................
> ff800010: 0000 0000 0000 0000 0000 0000 0000 0000    ................
> ff800020: 0000 0000 0000 0000 0000 0000 0000 0000    ................
> ff800030: 0000 0000 0000 0000 0000 0000 0000 0000    ................
> ff800040: 0000 0000 0000 0000 0000 0000 0000 0000    ................
> ff800050: 0000 0000 0000 0000 0000 0000 0000 0000    ................
> ff800060: 0000 0000 0000 0000 0000 0000 0000 0000    ................
> ff800070: 0000 0000 0000 0000 0000 0000 0000 0000    ................
> 
> I also tried various permutations of mw.w ff8000aa 00aa, etc, as well as
> mw.w 0xff800554 5500 (rather than 0055), since we are writing to a
> different address, and none of them gave anything other than 0000 results.

Too bad. :-(
 
> This is the procedure for entering QRY mode, though, from my original email:
>  > For this particular chip, the command is:
>  > 
>  > mw.w 0xff8000aa 9800 (rather than 9898)
>  > 
>  > (FWIW mw.b 0xff8000aa 98 also works fine to enter QRY mode)
>  > 
>  > Having done that, the QRY results are present at 0xff800020:
>  > 
>  > md.b ff800020 20
>  > ff800020: 51 51 52 52 59 59 02 02 00 00 40 40 00 00 00 00
> 
> QQRRYY....@@....
> 
>  > ff800030: 00 00 00 00 00 00 27 27 36 36 00 00 00 00 04 04
> 
> .....''66......
> 
> Does that help?

Not really. I find it odd, that writing 0x9800 works and 0x0098 doesn't. 
Perhaps the chip is connected in byte-mode after all? Not sure.

Do you know if and how the Linux MTD driver handles the NOR FLASH?

Cheers,
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 at denx.de