From: Trevor Woolven <trevw@zentropix.com>
To: MTD <mtd@infradead.org>
Subject: Reviving DiskOnChip
Date: Fri, 10 Mar 2000 17:34:43 +0000 [thread overview]
Message-ID: <38C93233.A1AC0566@zentropix.com> (raw)
Err, anybody know the spells and incantations required to bring a
DiskOnChip back to life?
According to M-Systems there are ways to do this (eg: dformat /win:xxx
/unformat) but they don't seem to work for me, (wrong kind of pointy hat
I guess).
docpmap /e appears to frag the thing completely, full stop, goodnight
vienna.
I include an excerpt from an email that opens the lid (very slightly) on
some of their secret squirrel stuff in case it's of use/information to
anyone.
If anyone has the full monty on the M-Systems utilities, ie: what the
commands really do, what their commandline parameters really are and
which sub-sets actually work, I'd be externally grateful.
Alternatively, has anyone got some other utilities to achieve, stable,
working, reliable and robust DOCs?
Have I been stupid? (don't answer that!) or just unlucky?
Thanks in advance and desperation,
Trev.
<<Snip>>
dformat /win:e400 /log:<filename> - this will save the bad block table
in
the file <filename> just to be on the safe side. I still owe you this
answer
from a previous email if I remember correctly. you can later use dformat
/win:e400 /uselog:<filename> - if you accidentally used docpmap /e.
then
dformat /win:e400 /unformat - this will return the DOC to it's original
condition where the flash is totally erased and bad blocks are marked.
dformat /win:e400 /s:doc122.exb - this will return the firmware to the
doc
and format it ready for the file system
There is a manual in the physical pack but unfortunately all the secrets
such as these undocumented options are not documented there and in the
help
message when you write dformat with no parameters, sorry :-)
<</Snip>>
--
Trevor Woolven - Director of Customer Applications Engineering
Zentropix Inc - a Lineo company
Tel: +44 (0)1273 234 647 Fax: +44 (0)1273 704 482
Visit http://www.zentropix.com/ for Real Time Linux Tools
Visit http://www.realtimelinux.org/ for Real Time Linux Information
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next reply other threads:[~2000-03-10 17:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-10 17:34 Trevor Woolven [this message]
2000-03-12 13:24 ` Reviving DiskOnChip David Woodhouse
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=38C93233.A1AC0566@zentropix.com \
--to=trevw@zentropix.com \
--cc=mtd@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