public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Ruediger Haertel <hae@port.de>
To: linux-mtd@lists.infradead.org
Subject: MTD/ DoC Millenium Plus - Failure in flash detection
Date: Wed, 6 Jul 2005 17:45:18 +0200	[thread overview]
Message-ID: <200507061745.18226.hae@port.de> (raw)

Hello all,

I am trying to get the DOC Millenium Plus chip (16 MB, ChipID = 0x41) on 
my board (Coldfire 5272, uClinux) running. The chip as such is detected. 
If the DoC is accessed correctly then the flash chip has id 0xA5. This 
id is not in the table of NAND IDs in the file nand_ids.c.

The cvs MTD drivers has 0xA5 assigned to a SAMSUNG 2 GiB chip. But as 
far as I know the Doc MilPlus 16MB uses a Toshiba flash.

Any suggestions what's wrong here.

How would I verify that access to the DoC is correct?
At which address would I read? and what to expect?

If this would work, how do I proceed? I read something about 
nftl_format?


The documents/books I found so far (Building embedded linux; Linux MTD, 
JFFS Howto ..) mostly concentrate on using some kind of pluggable DOC 
chips that can be inserted in a computer that has Windows or Linux 
running. Then everything can be done with some tools. But how really to 
do it on an embedded linux with a soldered DoC ?



-- 

Ruediger Haertel

             reply	other threads:[~2005-07-06 15:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-06 15:45 Ruediger Haertel [this message]
2005-07-07 13:05 ` MTD/ DoC Millenium Plus - Failure in flash detection Ruediger Haertel
2005-07-07 13:21   ` Thomas Gleixner
2005-07-07 13:32     ` Ruediger Haertel
2005-07-07 14:00       ` Thomas Gleixner
2005-07-07 15:04       ` Ruediger Haertel
2005-07-08  8:48         ` Ruediger Haertel
2005-07-08  9:21           ` Ruediger Haertel
2005-07-11  8:04           ` Ruediger Haertel

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=200507061745.18226.hae@port.de \
    --to=hae@port.de \
    --cc=linux-mtd@lists.infradead.org \
    /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