public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: zhang jingxin <zhangjingxin@sict.ac.cn>
To: linux-mtd@lists.infradead.org
Subject: doc2000 problem
Date: Wed, 08 Dec 2004 20:41:50 +0800	[thread overview]
Message-ID: <1102509710.2462.6.camel@z21921> (raw)

hi,
I want use JFFS2 on my DOC2000 original.I download the latest CVS
version(041128).I use diskonchip.c to drive.It works.

Dec  6 17:47:11 localhost kernel: Creating 1 MTD partitions on
"DiskOnChip 2000 (NFTL Model)":
Dec  6 17:47:11 localhost kernel: 0x00014000-0x02000000 : " DiskOnChip
BDTL partition"
Dec  6 17:47:11 localhost kernel: mtd: Giving out device 1 to 
DiskOnChip BDTL partition

But it has a little error.



Dec  8 10:23:54 localhost kernel: nand_read_ecc: from = 0x0000c000, len
= 512
Dec  8 10:23:54 localhost kernel: nand_read_ecc: Failed ECC read, page
0x00000060 on chip 0
Dec  8 10:23:54 localhost kernel: ECC error scanning DOC at 0xc000

Dec  8 10:23:54 localhost kernel: nand_read_ecc: from = 0x00010000, len
= 512
Dec  8 10:23:55 localhost kernel: nand_read_ecc: Failed ECC read, page
0x00000080 on chip 0
Dec  8 10:23:55 localhost kernel: ECC error scanning DOC at 0x10000

There are two ECC errors.
Then it nand_read_ecc 0x0000c200 .

Dec  8 10:23:55 localhost kernel: nand_read_ecc: from = 0x0000c200, len
= 2048

I don't know why,this position has already done.

I had read below

2004-10-26 15:46

Dan Brown dan_brown at ieee.org 
Fri Jun 18 19:30:56 EDT 2004 
Brief HOWTO (better HOWTO coming soon!):

- Have a DOC Millenium or DOC2000 TSOP.  Millenium+ is not supported
(other
folks are hard at work on this).  DOC2000 original does not have BBT
handling yet (coming soon!) and should not be used with JFFS2 yet.

- Load the new diskonchip module (there is now a kernel configuration
option
for this under NAND devices).  If your DOC device is not at window D000,
you'll have to edit the source or remap your chip.  Proper probing
coming
soon!

- A bunch of mtd devices should be created.  mtd0 is the whole DOC.  The
others are partitions created by M-Systems.  A "BDK" partition is
probably
the M-Sys BIOS driver.  A "BDTL" partition is where your INFTL
filesystem
used to be.  I say used to be, because you're about to trash it.

- You can review the list of devices with 'cat /proc/mtd'

- Assuming your BDTL partition is mtd3:

    flash_eraseall -j /dev/mtd3
    mkfs.jffs2 -p -e 16384 -n -q -r <rootdir> -o <outputfile>
    nandwrite /dev/mtd3 <outputfile from above>
    mount -t jffs2 /dev/mtdblock3 <mountpoint>

So I follow it.
I review the list of devices with 'cat /proc/mtd'
 
 
cat /proc/mtd
dev:    size   erasesize  name
mtd0: 02000000 00004000 "DiskOnChip 2000 (NFTL Model)"
mtd1: 01fec000 00004000 " DiskOnChip BDTL partition"


flash_eraseall -j /dev/mtd1
It doesn't recongize the device.

what should i do??
It's this reason --DOC2000 original does not have BBT
handling yet (coming soon!).

             reply	other threads:[~2004-12-08 12:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-08 12:41 zhang jingxin [this message]
2004-12-08 14:15 ` doc2000 problem Dan Brown
  -- strict thread matches above, loose matches on Subject: below --
2004-12-09  1:28 zhang jingxin
2004-12-09  9:55 ` Thomas Gleixner

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=1102509710.2462.6.camel@z21921 \
    --to=zhangjingxin@sict.ac.cn \
    --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