public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] CFI driver AMD Command Set Top boot	geometry reversal, etc. [Updated]
Date: Fri, 10 Nov 2006 16:44:07 -0600	[thread overview]
Message-ID: <455500B7.5050506@freescale.com> (raw)
In-Reply-To: <4554EFCC.2000204@freescale.com>

Timur Tabi wrote:
> Stefan Roese wrote:
> 
>> As you may notice, even the ID's are not correct (0020 and 22c4 are correct) 
>> and the geometry is not correct (bottom instead of top).
> 
> It looks like the problem with the IDs (I have them too) is that 
> flash_read_jedec_ids() is broken.  After sending the commands, the function 
> just reads the regular data instead of the command reply.

Well, I think I fixed it.

In flash_read_jedec_ids(), make this change:

-               flash_write_cmd(info, 0, 0, FLASH_CMD_READ_ID);
+               flash_write_cmd(info, 0, AMD_ADDR_START, FLASH_CMD_READ_ID);

I got the value of AMD_ADDR_START from the MX29LV640BT/BB reference manual, 
which says that the third bus cycle should be a write of 90h to 555 or AAA, 
depending on the width.

Now when I run flinfo, I get this:

Bank # 1: CFI conformant FLASH (16 x 16)  Size: 8 MB in 135 Sectors
   AMD Standard command set, Manufacturer ID: 0xC2, Device ID: 0xC9
   Erase timeout: 16384 ms, write timeout: 1 ms

If this fix is real, then it means that flash_read_jedec_ids() never worked 
for any AMD part.

-- 
Timur Tabi
Linux Kernel Developer @ Freescale

  reply	other threads:[~2006-11-10 22:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-09 23:46 [U-Boot-Users] [PATCH] CFI driver AMD Command Set Top boot geometry reversal, etc. [Updated] Tolunay Orkun
2006-11-10 11:16 ` Stefan Roese
2006-11-10 15:47   ` Tolunay Orkun
2006-11-10 21:31   ` Timur Tabi
2006-11-10 22:44     ` Timur Tabi [this message]
2006-11-12  4:42       ` Tolunay Orkun
2006-11-12  8:13         ` Stefan Roese
2006-11-12 22:04           ` Tolunay Orkun
2006-11-13 13:05             ` Stefan Roese
2006-11-13 15:34         ` Timur Tabi

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=455500B7.5050506@freescale.com \
    --to=timur@freescale.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