From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Non standard CFI detection tweaks
Date: Thu, 12 Aug 2010 14:40:01 +0200 [thread overview]
Message-ID: <201008121440.01113.sr@denx.de> (raw)
In-Reply-To: <4C63E3E7.30300@dawes.za.net>
Hi Rogan,
On Thursday 12 August 2010 14:07:03 Rogan Dawes wrote:
> I found the following configuration snippet for OpenOCD for the DNS323
> at http://wiki.dns323.info/hardware:jtag:
>
> # driver addr size chip_width bus_width options
> flash bank cfi 0xff800000 0x800000 1 2 0
>
> It seems that the key here is that the bus_width is set to 2, even
> though the chip_width is only 1.
Seems not to be so uncommon: 8bit device on a 16bit external bus.
> Also, the flash address is still 0xff800000, even though the kernel has
> it as 0xf4000000. I guess this is because only a certain number of
> address lines are actually connected through to the flash chip, and so
> the chip can appear in multiple places?
Yes, this could be the case. The flash is most likely "mirrored".
> Does that make any more sense? Is it possible that the CFI code in
> U-Boot doesn't consider the case when bus_width == 2?
As mentioned above, this seems to be a common use-case (even though I don't
have such a board at hand right now). Bus-width = 2 (vs. bus-width = 1)
shouldn't really matter here. A CPU byte access to the flash address space
should translate in one access cycle (8-bit) to the flash device.
Sorry, no real idea whats going wrong without being able to test/debug on this
platform.
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-08-12 12:40 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
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 [this message]
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=201008121440.01113.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