From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] mtd: cfi: Add support for status register polling
Date: Fri, 17 Nov 2017 20:02:55 +0100 [thread overview]
Message-ID: <48e13a2e-3380-4ff5-ad64-6b3e23910156@gmail.com> (raw)
In-Reply-To: <HE1PR04MB2073D2D6F6BA95DAD80BE5709A2F0@HE1PR04MB2073.eurprd04.prod.outlook.com>
On 11/17/2017 05:43 PM, York Sun wrote:
> On 09/12/2017 10:09 AM, Marek Vasut wrote:
>> The status register is optional in the AMD command sets, but it's
>> presence can be checked by reading out CFI table entry 0xc bit 0.
>> If the register is present, prefer using it's bit 7 to determine
>> if the flash is busy over reading the flash ; this is needed ie.
>> on Hyperflash memories.
>>
>> Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com>
>> ---
>
> Marek,
>
> Some of our boards failed. I traced to this commit. Reverting this
> commit fixes the issue. I happen to have two boards with slightly
> different flash chip. One works and the other doesn't.
I can't since I don't have the board with such a chip ...
Which chip is that ? Mine is Spansion S25KL256 hyperflash.
> The working board has
>
> => fli
>
> Bank # 1: CFI conformant flash (16 x 16) Size: 128 MB in 1024 Sectors
> AMD Standard command set, Manufacturer ID: 0x01, Device ID: 0x227E2801
> Erase timeout: 2048 ms, write timeout: 1 ms
> Buffer write timeout: 3 ms, buffer size: 512 bytes
>
> The failing board has
>
> => fli
>
> Bank # 1: CFI conformant flash (16 x 16) Size: 128 MB in 1024 Sectors
> AMD Standard command set, Manufacturer ID: 0x01, Device ID: 0x227E2801
> Erase timeout: 4096 ms, write timeout: 1 ms
> Buffer write timeout: 3 ms, buffer size: 64 bytes
>
> Can you investigate?
>
> York
>
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2017-11-17 19:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 17:09 [U-Boot] [PATCH] mtd: cfi: Add support for status register polling Marek Vasut
2017-09-26 15:57 ` Stefan Roese
2017-11-17 16:43 ` [U-Boot] " York Sun
2017-11-17 19:02 ` Marek Vasut [this message]
2017-11-17 19:04 ` Marek Vasut
2017-11-17 19:48 ` York Sun
2017-11-17 20:59 ` York Sun
2017-11-17 21:48 ` York Sun
2017-11-18 10:23 ` Marek Vasut
2017-11-18 19:11 ` York Sun
2017-12-02 9:14 ` Marek Vasut
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=48e13a2e-3380-4ff5-ad64-6b3e23910156@gmail.com \
--to=marek.vasut@gmail.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