All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Yergovich <ayergo@jkmicro.com>
To: linux-mtd@lists.infradead.org
Subject: Re: M-systems DOC 2000
Date: Mon, 04 Jan 2010 10:55:12 -0800	[thread overview]
Message-ID: <4B423990.6040607@jkmicro.com> (raw)
In-Reply-To: <20100104183407.NJYA21638.aamtaout02-winn.ispmail.ntl.com@Parkytowers.ntlworld.com>

David Parkinson wrote:
> Hi,
> 
> I've been doing stuff with some old GEODE-based thin clients (circa 
> 2003) and have Linux running off CF cards on the IDE interface.  A 
> couple of them (Neoware Capio and Relisys RWT200EM) have DOC 2000s on 
> them (32Mb and 16Mb respectively) which hold the original WinCE firmware 
> and I thought it would be interesting to try and utilise these - however 
> Google has not been my friend here.
> 
> Currently I'm using Tiny Core and have rebuilt the kernel and included 
> MTD support along with the drivers for the DOC 2000.  I've got as far as 
> getting the message "No DiskOnChip devices found" in the start-up 
> messages.  I did wonder whether the M-systems DOS-based tool set 
> (v5.1.4.0?) would help me get a grip on things, but all the "download 
> from here" links that Google found link to the m-systems website that I 
> believe vanished some time ago.  How-to's that I've found are all 4-5 
> years old and generally refer to M-systems drivers and/or require 
> ancient kernels and specific compilers....  (I have however managed to 
> locate and download the device datasheets!)
> 
> I'd appreciate any pointers to any documentation or tools that would 
> help me with my quest.
> 
> Regards
> 
> David
> 

Can be tricky work dealing with the old systems.  I've done a fair 
amount of work with the Disk On Chip 2000, and my company even has them 
for sale if you need more.  We also have our own little toolbox for 
formatting and partitioning the drives, however its all setup to use our 
controllers so i'm not sure how much use it is to you.  You can take a 
look though:

www.jkmicro.com

http://www.jkmicro.com/downloads/zip/DiskOnChipToolbox.zip

It could just be that your DOC isn't formatted and thus not showing up, 
and i've also seen failed DOC that won't respond at all.  You might want 
to make sure you start with a fresh one.  I wouldn't be surprised if the 
old WinCE firmware on there used some wacky partitioning to obscure 
their executables.

If they are FAT formatted though you could plug them into one of our 
boards and at least get the executables off.

Hope this helps,

-Adam

-- 
Adam Yergovich
Engineer
JK Microsystems

1403 Fifth St. Suite D
Davis, CA 95616

Tel:(530) 297-6073

      reply	other threads:[~2010-01-04 18:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-04 18:33 M-systems DOC 2000 David Parkinson
2010-01-04 18:55 ` Adam Yergovich [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=4B423990.6040607@jkmicro.com \
    --to=ayergo@jkmicro.com \
    --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 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.