public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Eric BENARD <ebenard@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] Incorrect Chip ID for Micrel Nand Flash on AT91SAM9260 board
Date: Fri, 17 Oct 2008 11:52:43 +0200	[thread overview]
Message-ID: <48F8606B.1020005@free.fr> (raw)
In-Reply-To: <179373d80810170249y4aa91406u4eab2af9d28f5f4f@mail.gmail.com>

Hi Kevin,

Kevin Greer a ?crit :
> I am working with a custom board based on the Atmel at91sam9260 arm
> processor with a Micrel 2 Gb Nand flash chip (mt29f2g08aadwp).  However,
> when u-boot starts it reports the wrong Chip ID (0x01 instead of 0xda) and
> then I start getting Bad eraseblock messages during the rest of the boot
> process.  The strange thing is that when I debug the board using a JTAG it
> gets the correct Chip ID and boots properly.  I am hoping that someone else
> might have run into a similar problem, or might have an idea of how to
> proceed.
> 
try sending a reset command to the nand before getting the ID, this 
should solve the problem.

Eric

      reply	other threads:[~2008-10-17  9:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-17  9:49 [U-Boot] Incorrect Chip ID for Micrel Nand Flash on AT91SAM9260 board Kevin Greer
2008-10-17  9:52 ` Eric BENARD [this message]

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=48F8606B.1020005@free.fr \
    --to=ebenard@free.fr \
    --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