CFI with 4 x8/x16 devices on a 32-bit bus

[Joakim Tjernlund]

Hi again :-)

I have testing a few combinations w.r.t number of partitions
and this is what I have discoved so far:

1) No partitions, just do add_device() for the whole flash - Works OK (cat
/dev/mtd0 returns fffffffff ...)
2) 1 small(size 0x40000, offset 0) partition - Works OK (cat /dev/mtd0
returns fffffffff ...)
3) 2 partitions( tried a few different sizes) - Not OK, here I get
81ff81ff81ff ... !

I have 4 amd flash chips(label printed on them is D323BD90VI)
which I think maps to the following spec:
http://www.amd.com/products/nvd/techdocs/23480.pdf

Apparently this is chip with 2 erase sectors sizes. I suspect the different
sector sizes
is the cause to my problems, but I cant figure out where the problem is. I
have
tried with&whithout virtual regions.

Any ideas?

Boot message regarding the flash:

  RPX Lite or CLLF flash device: 1000000 at ff000000
  RPX: Found 4 x16 devices at 0x0 in 32-bit mode
  Amd/Fujitsu Extended Query Table v1.2 at 0x0040
  number of CFI chips: 1
  0: offset=0x0,size=0x8000,blocks=8
  1: offset=0x40000,size=0x40000,blocks=63
  Created 1 virtual regions for partiton 0
  mtd: Giving out device 0 to RPX App 0xff000000
  Created 1 virtual regions for partiton 1
  mtd: Giving out device 1 to RPX App 0xff040000
  Created 1 virtual regions for partiton 2
  mtd: Giving out device 2 to RPX CLLF boot firmware
  Created 1 virtual regions for partiton 3
  mtd: Giving out device 3 to RPX  App 0xfff40000
  Created 1 virtual regions for partiton 4
  mtd: Giving out device 4 to RPX  Diag & Utils


Brett, I have included your changes in rpxlite.c, did not make a difference,
but at lest I
have a better chance to write to the flash once the problem above has been
solved. Thanks a lot!

    Joakim

-----Original Message-----
From: Joakim Tjernlund [mailto:joakim.tjernlund at lumentis.se]
Sent: Monday, April 09, 2001 18:25
To: 'mtd at infradead.org'
Subject: RE: CFI with 4 x8/x16 devices on a 32-bit bus


Hi all

I have RPX CLLF (very similar to RPX Lite) with similar Flash setup as
below.
I have modified rpxlite.c so it will set up 5 partitions on that flash
and it appears to work, but when I do a cat /dev/mtd0 or cat /dev/mtdblock0
which is an erased partition I get the following pattern:
81ff81ff81ff81ff .....
for the whole partition instead of fffffffffffff ...

Any ideas?

 Jocke

-----Original Message-----
From: owner-mtd at infradead.org [mailto:owner-mtd at infradead.org]On Behalf
Of David Woodhouse
Sent: Friday, April 06, 2001 15:46
To: Brett Carswell
Cc: 'mtd at infradead.org'
Subject: Re: CFI with 4 x8/x16 devices on a 32-bit bus



BrettC at 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 at infradead.org



To unsubscribe, send "unsubscribe mtd" to majordomo at infradead.org