public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Non standard CFI detection tweaks
Date: Tue, 20 Jul 2010 09:58:33 +0200	[thread overview]
Message-ID: <201007200958.33622.sr@denx.de> (raw)
In-Reply-To: <4C446314.7040702@dawes.za.net>

Hi Rogan,

On Monday 19 July 2010 16:37:08 Rogan Dawes wrote:
> On 2010/07/19 3:33 PM, Stefan Roese wrote:
> > 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
> 
> Here is the setup code from the Linux kernel:
>  >http://lxr.free-electrons.com/source/arch/arm/mach-orion5x/dns323-setup.c
>  >#L93>
> 
> Which is used by:
> 
> <http://lxr.free-electrons.com/source/arch/arm/mach-orion5x/dns323-setup.c#
> L435>
> 
> I don't know enough about the kernel to understand where it goes to from
> there.

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.


BTW: This code you referenced is also available in mainline kernel.org.

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

  reply	other threads:[~2010-07-20  7:58 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 [this message]
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=201007200958.33622.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