public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Rogan Dawes <rogan@dawes.za.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] Non standard CFI detection tweaks
Date: Thu, 12 Aug 2010 14:07:03 +0200	[thread overview]
Message-ID: <4C63E3E7.30300@dawes.za.net> (raw)
In-Reply-To: <201007200958.33622.sr@denx.de>

On 2010/07/20 9:58 AM, Stefan Roese wrote:
>
> OK, so the width is definitely 8 bit and not 16 bit:
>
> static struct physmap_flash_data dns323_nor_flash_data = {
> 	.width		= 1,
> ...
>
> But the base address is listed here as 0xf4000000:
>
> #define DNS323_NOR_BOOT_BASE 0xf4000000
>
> Are you sure you got this right? Nevertheless, now we know for sure, that the
> NOR chip is connected as an 8bit device and the chip is operated in byte mode.
> So all tests from the U-Boot prompt should be done with ".b" extension.

Hi Stefan,

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.

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?

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?

Regards,

Rogan

  parent reply	other threads:[~2010-08-12 12:07 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 [this message]
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=4C63E3E7.30300@dawes.za.net \
    --to=rogan@dawes.za.net \
    --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