From: Thorsten Reimers <thorsten@treimers.net>
To: linux-mtd@lists.infradead.org
Subject: Problem booting from DiskOnChip 2000
Date: Mon, 19 Jan 2004 19:05:50 +0100 [thread overview]
Message-ID: <400C1C7E.2090404@treimers.net> (raw)
Hi all,
I have a board with a DiskOnChip 200 module from M-System. I have been able, to
start the driver as a module and partitioning and fromatting the chip. I am
struggling to boot from it, does anybody have an idea?
Find below the messages from my Bios and from Linux during boot (from floppy).
BIOS Messages
=============
DOC Socket Services - Version 0.2
(C) Copyright 1992-1996, M-Systems Ltd.
TrueFFF-BIOS -- Version 3.3.9 for DiskOnChip 2000 (V4.3)
Copryright (C) M-Systems, 1992-2001
Linux Boot Messages
===================
Using /opt/files/lib/modules/2.4.23/kernel/drivers/mtd/mtdcore.o
Using /opt/files/lib/modules/2.4.23/kernel/drivers/mtd/nand/nand_ids.o
Using /opt/files/lib/modules/2.4.23/kernel/drivers/mtd/devices/docecc.o
Using /opt/files/lib/modules/2.4.23/kernel/drivers/mtd/devices/doc2000.o
Using /opt/files/lib/modules/2.4.23/kernel/drivers/mtd/mtd_bkl_devs.o
DiskOnChip 2000 found at address 0xD8000
Flash chip foind: Manufacturer ID: 98, Chip ID: E6 (Toshiba: NAND 8MiB 3,3V)
3 flash chips found. Total DiskOnChip size: 24 MiB
Ignoring DiskOnChip 2000 at 0xDA000 - already configured
Ignoring DiskOnChip 2000 at 0xDC000 - already configured
Ignoring DiskOnChip 2000 at 0xDE000 - already configured
Using /opt/files/lib/modules/2.4.23/kernel/drivers/devices/docprobe.o
NFTL driver: nftlcore.c $Revision: 1.94 $, nftlmount.c $Revision: 1.34 $
NFTL: UnitSizeFactor 0x00 detected. This violates the spec but we think we know
what it means ...
During boot it stop's after sending out only some characters from linux load:
SYSLINUX 1.76 0x3d93445f
Maybe I should clean the chip by a tool, maybe I should install a new
firmware on the chip? I tried it together with a hard disk with Windows and the
disk-on-chip tools from MSystem. This worked really fine so I decided to
install Linux now.
And, last but not least: Dave Woodhouse, I would like to apologize for sending
out an email to you (which you did answer nevertheless). I just discovered this
mailing list and how to get help.
Thorsten
Wer krank wird, erfährt als erstes, dass er selber Schuld hat. - Eugen Drewermann
next reply other threads:[~2004-01-19 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 18:05 Thorsten Reimers [this message]
2004-01-20 7:50 ` Problem booting from DiskOnChip 2000 Andrea Galbusera
2004-01-23 10:15 ` Thorsten Reimers
2004-04-25 10:37 ` Thorsten Reimers
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=400C1C7E.2090404@treimers.net \
--to=thorsten@treimers.net \
--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