public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: David Hawkins <dwh@ovro.caltech.edu>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Intel Flash CFI initialisation failure
Date: Thu, 13 Sep 2007 09:13:24 -0700	[thread overview]
Message-ID: <46E961A4.5030000@ovro.caltech.edu> (raw)
In-Reply-To: <Pine.LNX.4.44.0709131441230.25396-100000@slslc02.psi.ch>

Hi Mirek,

> Unfortunately I did not solve completely the problem which I had 
> with the Flash memory. It seems to be that in u-boot there is a problem 
> with 16 bits long data access. 
> 
> My memory has the size of 64 Mbits. In my configuration it should be 
> accessed in x16 bits mode so it means that under each memory location 
> there are 16 bits. In u-boot it seems to be that all is seen in bytes and 
> under one memory location there is seen only one byte instead of two.
> 
> Is it somehow possible to change that by some define statements?

Perhaps the board has LA[n:31] connected to the address bus
of the Flash rather than the correct LA[n:30] signals.

If so, its a hardware error, and there is not much you can
do. Even if the chip has a BYTE# pin you can change modes
with, a 16-bit Flash usually has a DQ15/A-1 pin that LA[31]
would then connect to.

Just a thought ...

Cheers,
Dave

  parent reply	other threads:[~2007-09-13 16:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-07 14:43 [U-Boot-Users] Intel Flash CFI initialisation failure Miroslaw Dach
2007-09-07 18:40 ` Wolfgang Denk
2007-09-10  9:59   ` Miroslaw Dach
2007-09-13  8:15 ` Miroslaw Dach
2007-09-13 12:56   ` Miroslaw Dach
2007-09-13 13:17     ` Jerry Van Baren
2007-09-13 13:45       ` Miroslaw Dach
2007-09-13 16:13     ` David Hawkins [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-09-07 19:22 Scott Mann
2007-09-10 10:20 ` Miroslaw Dach
2007-09-07 11:19 Mirek23

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=46E961A4.5030000@ovro.caltech.edu \
    --to=dwh@ovro.caltech.edu \
    --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