All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anders Larsen <alarsen@rea.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Incorrect flash ids?
Date: Tue, 13 Jan 2004 12:13:37 +0100	[thread overview]
Message-ID: <fc.004c4e48002007d13b9aca00782e001b.200854@rea.de> (raw)
In-Reply-To: <40036300.21469.1F117239@localhost>

listmember at orkun.us schreibt:
>Anders,
>
>Guess what! Knowing how picky everyone can be I actually did check the 
>datasheets for all these. Perhaps you should also do the same before 
>accusing me of doing that first.

I did, of course. And checked with the existing u-boot code, too:
It should be rather obvious that changing these IDs (which are supposed
to match the codes read back from the chips) will indeed break existing
code.

>I still stand behind that these are incorrect as it is in the spirit of
>the rest 
>of  XXX_ID_YYYY macros. Take a look at the file!

Looking into the data sheet of the Intel Strata chips (28FxxxJ3A, Intel
document number 290667-009) at Table 15 (Identifier Codes) you'll see
that the device codes (found at word address 0001) are
28F320J3A: 0x0016
28F640J3A: 0x0017
28F128J3A: 0x0018
No ambiguity here.

Looking into include/flash.h at the xxxx_ID_yyyy macros I fail to see
a single one with embedded manufacturer ID (apart from the (incorrect)
INTEL_ID_28F128J3).
>
>I notice these problems because I happen to have 28F128J3A chip on 
>Cogent CSB272 board that I am porting u-boot to. I actually did manually 
>issue commands using BDI2000 and verified the value for 28F128J3A as 
>well.

Then you clearly didn't do it in the same way that the (existing)
code does it; the manufacturer code is read separately from the chip ID
(see flash_get_size() in board/eric/flash.c for a good example).
>
>Also another thing it is obvious that while 28F128J3 has manufacturer 
>(0x89) embedded (once correct and once incorrectly) in the value the 
>27F127J3A does not have any manufacturer id (or rather manufid is set 
>to 0x00 incorrectly). At least these two should have matched.

As already stated in my previous mail, I agree that the code for
28F128J3 (without 'A') is incorrect
(BTW, the manufacturer code is _not_ supposed to be embedded in the
xxxx_ID_yyyy codes, see above).

Cheers
 Anders

  reply	other threads:[~2004-01-13 11:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13  0:24 [U-Boot-Users] Incorrect flash ids? listmember at orkun.us
2004-01-13  8:55 ` Anders Larsen
2004-01-13  9:16   ` listmember at orkun.us
2004-01-13 11:13     ` Anders Larsen [this message]
2004-01-13 18:47       ` listmember at orkun.us
2004-01-13 18:54         ` listmember at orkun.us
2004-01-13 18:59 Rune Torgersen

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=fc.004c4e48002007d13b9aca00782e001b.200854@rea.de \
    --to=alarsen@rea.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.