From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Non standard CFI detection tweaks
Date: Mon, 19 Jul 2010 15:33:37 +0200 [thread overview]
Message-ID: <201007191533.37947.sr@denx.de> (raw)
In-Reply-To: <4C44429D.9020307@dawes.za.net>
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
next prev parent reply other threads:[~2010-07-19 13:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 20:00 [U-Boot] Non standard CFI detection tweaks Rogan Dawes
2010-07-19 9:34 ` Stefan Roese
2010-07-19 10:18 ` Rogan Dawes
2010-07-19 10:49 ` Stefan Roese
2010-07-19 11:05 ` Rogan Dawes
2010-07-19 11:50 ` Stefan Roese
2010-07-19 12:18 ` Rogan Dawes
2010-07-19 13:33 ` Stefan Roese [this message]
2010-07-19 14:37 ` Rogan Dawes
2010-07-20 7:58 ` Stefan Roese
2010-07-20 8:38 ` Rogan Dawes
2010-07-20 10:00 ` Rogan Dawes
2010-07-20 10:06 ` Reinhard Meyer
2010-07-20 10:22 ` Reinhard Meyer
2010-07-20 10:29 ` Rogan Dawes
2010-07-20 10:53 ` Reinhard Meyer
2010-07-20 11:01 ` Rogan Dawes
2010-07-23 10:17 ` Albert ARIBAUD
2010-08-12 12:07 ` Rogan Dawes
2010-08-12 12:40 ` Stefan Roese
2010-08-12 13:14 ` Reinhard Meyer
2010-08-12 13:26 ` Rogan Dawes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201007191533.37947.sr@denx.de \
--to=sr@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox