From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] M29EW flash is detected as 0xFF
Date: Wed, 20 Feb 2013 14:57:40 +0100 [thread overview]
Message-ID: <5124D654.4060804@denx.de> (raw)
In-Reply-To: <CAD6G_RQML2Fo-mE2GE0_yJXk5NUCC3QRRwR=OkAA2TKRTX26KQ@mail.gmail.com>
On 18.02.2013 10:57, Jagan Teki wrote:
> I have a 16MB, M29EW flash on target boards.
>
> I got the below info, while probing the flash.
>
> Bank # 1: CFI conformant flash (8 x 8) Size: 64 MB in 512 Sectors
> AMD Standard command set, Manufacturer ID: 0xFF, Device ID: 0xFF
> Erase timeout: 4096 ms, write timeout: 2 ms
> Buffer write timeout: 5 ms, buffer size: 1024 bytes
>
> Since the Manu.ID of this flash is 0x89, it got detected as 0xFF.
>
> Does u-boot code have a support for M29EW flash..?
I'm pretty sure, yes. Which U-Boot version are you using? Most likely
its an older version. Your problem reminds me about this commit:
Author: Philippe De Muyter <phdm@macqel.be> 2010-08-10 16:54:52
Committer: Stefan Roese <sr@denx.de> 2010-08-18 09:09:00
Parent: 2e97394a6d07a36dfc139b7b98b12e452b5bd8dc (cfi_flash: flinfo:
allow user interrupt in flash print info fn)
Child: 70084df7125a0b67de707b999982ec67adfdc35c (cfi_flash: Cleanup
flash_print_info())
Branches: many (98)
Follows: v2010.06
Precedes: v2010.09-rc1
Fix printing & reading of 16-bit CFI device identifiers
Fix reading and printing of CFI flashes 16-bit devices identifiers
Nowadays CFI flashes have a 16-bit device identifier. U-boot still
print them and read them as if they were only 8-bit wide. Fix that.
Before:
Intel Extended command set, Manufacturer ID: 0x89, Device ID: 0x1B
After:
Intel Extended command set, Manufacturer ID: 0x89, Device ID: 0x881B
So please update to the latest version and try again.
Best regards,
Stefan
next prev parent reply other threads:[~2013-02-20 13:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-17 11:51 [U-Boot] M29EW flash is detected as 0xFF Jagan Teki
2013-02-18 9:04 ` Jagan Teki
2013-02-18 9:57 ` Jagan Teki
2013-02-20 13:57 ` Stefan Roese [this message]
2013-02-20 17:25 ` Jagan Teki
2013-02-20 17:31 ` Jagan Teki
2013-02-20 18:14 ` Stefan Roese
2013-02-21 11:57 ` Jagan Teki
2013-02-22 15:32 ` Jagan Teki
2013-02-28 19:28 ` Jagan Teki
2013-03-01 6:59 ` Stefan Roese
2013-03-01 7:12 ` Jagan Teki
2013-03-01 7:18 ` Stefan Roese
2013-03-01 11:28 ` Jagan Teki
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=5124D654.4060804@denx.de \
--to=sr@denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox