From: Richard Danter <richard.danter@ntlworld.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] AMD29LV800T in 16bit mode x4 devices (64bit bus)
Date: Tue, 12 Jul 2005 20:38:25 +0100 [thread overview]
Message-ID: <42D41C31.2090903@ntlworld.com> (raw)
In-Reply-To: <20050711210531.C1103353AED@atlas.denx.de>
Wolfgang Denk wrote:
> In message <42D2DC59.6090507@ntlworld.com> you wrote:
>
>>Is there a driver that supports this flash within U-Boot? I can't see
>>one, but want to make sure I didn't miss it before I reinvent the wheel!
>
> There are several. First, there is the general CFI driver, and then
> there are several board specific drivers like board/tqm8260/flash.c
I have tried both of the suggested drivers with neither working for me.
I have spent more time looking at the tqm8260/flash.c and have managed
to make some improvements. Initially it was unable to even read back the
device type but I noticed that if I single stepped (using JTAG) the
flash_get_size() function then it _was_ able to correctly read the
device type.
This sounded like a timing issue until someone suggested that between
the writes and reads I should have "sync" and/or "eieio" to ensure the
CPU (MPC7400) does not execute them out of sequence. This certainly
fixed the flash_get_size() function, but I am still unable to write to
the flash (eg using saveenv). Though again I do see some data written if
I am single-stepping the write_dword() function.
Reading data from the flash works just fine.
Any suggestions?
Thanks
Rich
next prev parent reply other threads:[~2005-07-12 19:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 20:53 [U-Boot-Users] AMD29LV800T in 16bit mode x4 devices (64bit bus) Richard Danter
2005-07-11 21:05 ` Wolfgang Denk
2005-07-12 19:38 ` Richard Danter [this message]
2005-07-15 14:00 ` [U-Boot-Users] AMD29LV800T in 16bit mode x4 devices (64bit bus) - Fixed Richard Danter
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=42D41C31.2090903@ntlworld.com \
--to=richard.danter@ntlworld.com \
--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