From: Stephen Johnson <steve@research.panasonic.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Resolved -- Problems accessing flash on OMAP 1510 Innovator
Date: Wed, 13 Oct 2004 14:41:29 -0400 [thread overview]
Message-ID: <002201c4b154$40e2a160$bb01a996@CLOYDWIN2K> (raw)
After studying code in rrload and doing some googling, I tried an experiment
and it worked. In the file board/omap1510inn/flash.c I changed the function
get_flash_size() so that it now contains the following code:
/* Write auto select command: read Manufacturer ID */
// addr[0x5555] = (FPW) 0x00AA00AA;
// addr[0x2AAA] = (FPW) 0x00550055;
// addr[0x5555] = (FPW) 0x00900090;
addr[0] = (FPW) 0x00900090;
In other words I got rid of three lines of code and added my own. I can now
access -- both read and write -- the flash. My only concern is what have I
broken by this change! But for now I'm happy.
Thanks for everyone's help.
Steve
next reply other threads:[~2004-10-13 18:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 18:41 Stephen Johnson [this message]
2004-10-14 4:28 ` [U-Boot-Users] Resolved -- Problems accessing flash on OMAP 1510 Innovator George G. Davis
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='002201c4b154$40e2a160$bb01a996@CLOYDWIN2K' \
--to=steve@research.panasonic.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