* [U-Boot-Users] Resolved -- Problems accessing flash on OMAP 1510 Innovator
@ 2004-10-13 18:41 Stephen Johnson
2004-10-14 4:28 ` George G. Davis
0 siblings, 1 reply; 2+ messages in thread
From: Stephen Johnson @ 2004-10-13 18:41 UTC (permalink / raw)
To: u-boot
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* [U-Boot-Users] Resolved -- Problems accessing flash on OMAP 1510 Innovator
2004-10-13 18:41 [U-Boot-Users] Resolved -- Problems accessing flash on OMAP 1510 Innovator Stephen Johnson
@ 2004-10-14 4:28 ` George G. Davis
0 siblings, 0 replies; 2+ messages in thread
From: George G. Davis @ 2004-10-14 4:28 UTC (permalink / raw)
To: u-boot
On Wed, Oct 13, 2004 at 02:41:29PM -0400, Stephen Johnson wrote:
> 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
Based on your previous e-mail (with little to no CFI debug output displayed
after explicitly enabling cfi_flash driver debugging as I had recommended : )
I suspected that you may be using that now obsolete board/omap1510inn/flash.c
driver instead. It was recently replaced by drivers/cfi_flash.c. Please do a
cvs update and retest using the current cfi_flash driver and see if that works.
It does seem to work well for me.
--
Regards,
George
> 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
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-10-14 4:28 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-10-13 18:41 [U-Boot-Users] Resolved -- Problems accessing flash on OMAP 1510 Innovator Stephen Johnson
2004-10-14 4:28 ` George G. Davis
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox