From: David Woodhouse <dwmw2@infradead.org>
To: Brett Carswell <BrettC@nulec.com.au>
Cc: "'mtd@infradead.org'" <mtd@infradead.org>
Subject: Re: CFI with 4 x8/x16 devices on a 32-bit bus
Date: Fri, 06 Apr 2001 14:45:37 +0100 [thread overview]
Message-ID: <7657.986564737@redhat.com> (raw)
In-Reply-To: <1072F1A27E99D3119747005004B9A380EB98A6@MAIL>
BrettC@nulec.com.au said:
> I have four flash chips in parallel on a 32 bit bus so my impression
> is that I have an interleave of 4, a device type of 1 (8 bits) and a
> buswidth of 4 (32bits).
I believe that for 29LV160 chips, the device type should be X16, as that
determines the addresses to which the CFI commands must be sent, rather than
X8, which is merely the mode in which the chip happens to be configured at
the moment.
> However, the CFI probe is detecting the flash chips as device type 2
> (16bit).
That's what I'd expect. They _are_ 16-bit devices, even though you're using
them in 8-bit mode.
> This is fine except when the second address for the write
> command is generated as 0x1550 (0x2AA << 8) instead of 0x1554 (0x555
> << 4).
This stuff makes my head hurt :)
Thinks... Numbering CPU address lines by _byte_ addresses, A0 and A1 don't
exist. A2 is driving the 'A-1' line (aka D15 in word mode) of the flash
chip, presumably. A3 is driving the A0 line, etc. Right? Remembering that
the flash chip address lines are numbered by word (16-bit) addresses.
So to put 0x555 on the real address lines of the chip, we need to put
(0x555 << 3) == 0x2AA8 onto the CPU's address bus. And to put 0x2AA on the
real address lines of the chip, we put (0x2AA << 3) == 0x1550 onto the
CPU's address bus.
Ignoring the fact that you wrote '<<' when you meant '*', why do you think
we should be using the address 0x1554 (== 0x555 << 3)? What am I missing
this time? :)
0x1554 would be asserting the 'A-1' line of the flash chips. Why would you
want to do that?
> I'm trying to work out whether the detection or the program
> address generation is wrong or whether by interpretation of buswidth,
> interleave etc is wrong.
The address generation seems right. What exactly is going wrong, and where?
To confirm:
buswidth: obvious. (4 bytes)
interleave: Number of devices accessible through a single bus-width access (4)
device type: _Device_ type (2). You ignore the 'A-1' line because the magic
addresses still need to be on the 'A0' line and above, so you still
have to do the multiplication by this number.
At one time, I was under the mistaken impression that
buswidth == interleave * devtype. That's not necessarily true.
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2001-04-06 13:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-05 22:58 CFI with 4 x8/x16 devices on a 32-bit bus Brett Carswell
2001-04-06 13:45 ` David Woodhouse [this message]
2001-04-06 14:12 ` David Woodhouse
2001-04-13 8:41 ` What about a search engine ? DELANNEAU Alain
2001-04-17 14:55 ` David Woodhouse
2001-04-09 16:24 ` CFI with 4 x8/x16 devices on a 32-bit bus Joakim Tjernlund
-- strict thread matches above, loose matches on Subject: below --
2001-04-17 14:59 Joakim Tjernlund
2001-04-17 15:23 ` David Woodhouse
2001-04-17 15:51 ` Joakim Tjernlund
2001-04-17 15:53 ` David Woodhouse
2001-04-17 16:26 ` Joakim Tjernlund
2001-04-14 16:54 Kári Davíðsson
2001-04-12 12:41 Kári Davíðsson
2001-04-12 13:52 ` Joakim Tjernlund
2001-04-17 13:57 ` David Woodhouse
2001-04-11 15:05 Joakim Tjernlund
2001-04-10 7:30 Brett Carswell
2001-04-17 14:13 ` David Woodhouse
2001-04-09 23:34 Brett Carswell
2001-04-10 0:27 ` Nicolas Pitre
2001-04-10 1:55 ` David Woodhouse
2001-04-10 1:53 ` David Woodhouse
2001-04-10 2:01 ` David Woodhouse
2001-04-05 7:32 Brett Carswell
2001-04-05 14:09 ` David Woodhouse
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=7657.986564737@redhat.com \
--to=dwmw2@infradead.org \
--cc=BrettC@nulec.com.au \
--cc=mtd@infradead.org \
/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