From: Peter Asemann <peter.asemann@web.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] .../board/fads/flash.c confuses me - give me a hint
Date: Wed, 12 Jan 2005 15:43:52 +0100 [thread overview]
Message-ID: <41E537A8.8050006@web.de> (raw)
Im writing my own flash.c for "my" custom board in the moment.
That's why I'm trying to understand what the flash.c does.
I thought I got it when I encountered the following problem examining
board/fads/flash.c
All functions in there seem to be written to handle 4x8bit flash banks.
As indication for that are - in my opinion - the QUAD_ID macro in line
41+ and the fact that 0xAAAAAAAA, 0x55555555 and 0x90909090 and not
0x00AA00AA, 0x00550055 and 0x00900090 are written in the auto select
command sequence, beginning in line 227 (u-boot 1.1.2).
But they do write to the addresses which are typical - my fine flash
datasheet says - for word-mode flash access.
So the data written seems not to fit the addresses written to.
I'd be very happy if someone could give me a hint what I missed or what
I got wrong or why it must be that way though.
Peter Asemann
next reply other threads:[~2005-01-12 14:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 14:43 Peter Asemann [this message]
2005-01-12 16:54 ` [U-Boot-Users] .../board/fads/flash.c confuses me - give me a hint Wolfgang Denk
2005-01-12 17:21 ` Peter Asemann
2005-01-12 18:47 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2005-01-12 18:16 Nghiem, Tien
2005-01-12 19:34 ` Peter Asemann
2005-01-12 21:03 ` Tolunay Orkun
2005-01-12 22:29 ` Wolfgang Denk
2005-01-13 3:19 ` Tolunay Orkun
2005-01-12 21:06 ` Jon Loeliger
2005-01-12 22:19 ` Wolfgang Denk
2005-01-12 21:08 Nghiem, Tien
2005-01-13 8:24 Peter Pearse
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=41E537A8.8050006@web.de \
--to=peter.asemann@web.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.