New problem with DoC

New problem with DoC

[Gregg C Levine]

Hello from Gregg C Levine
It seems to be my day for problems with this configuration. Using the
"doc_loadbios" program found in the util directory of the mtd
collection, I've managed to write the firmware to the DoC, one was the
one labeled "DOC2.FFF", and the other one was "doc42.exb", both were
copied from the disk provided by M-SYS that's version 4.2 of their
series of tools.

Now with the card inserted in the computer, it does not even respond
to the <ctrl> <alt> B sequence, that M-SYS insists will prevent the
firmware, from loading. Nor is there any message printed regarding the
device. Now I am really lost. Oh, and this is an OEM computer wearing
an Award BIOS.
-------------------
Gregg C Levine hansolofalcon at worldnet.att.net
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."=A0 Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )

New problem with DoC

[Henrik Nordstrom]

The Control+Alt+B DoC bypass key is only in newer 5.X versions of the MSys
firmware if I remeber correctly, and only if the firmware can be loaded 
OK.

Regards
Henrik

On Sun, 16 Mar 2003, Gregg C Levine wrote:

> Hello from Gregg C Levine
> It seems to be my day for problems with this configuration. Using the
> "doc_loadbios" program found in the util directory of the mtd
> collection, I've managed to write the firmware to the DoC, one was the
> one labeled "DOC2.FFF", and the other one was "doc42.exb", both were
> copied from the disk provided by M-SYS that's version 4.2 of their
> series of tools.
> 
> Now with the card inserted in the computer, it does not even respond
> to the <ctrl> <alt> B sequence, that M-SYS insists will prevent the
> firmware, from loading. Nor is there any message printed regarding the
> device. Now I am really lost. Oh, and this is an OEM computer wearing
> an Award BIOS.
> -------------------
> Gregg C Levine hansolofalcon at worldnet.att.net
> ------------------------------------------------------------
> "The Force will be with you...Always." Obi-Wan Kenobi
> "Use the Force, Luke."? Obi-Wan Kenobi
> (This company dedicates this E-Mail to General Obi-Wan Kenobi )
> (This company dedicates this E-Mail to Master Yoda )
> 
> 
> 
> 
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
> 

New problem with DoC

[Gregg C Levine]

<Reply below!>
> -----Original Message-----
> From: linux-mtd-admin at lists.infradead.org [mailto:linux-mtd-
> admin at lists.infradead.org] On Behalf Of Henrik Nordstrom
> Sent: Monday, March 17, 2003 2:05 AM
> To: Gregg C Levine
> Cc: linux-mtd at lists.infradead.org
> Subject: Re: New problem with DoC
>=20
> The Control+Alt+B DoC bypass key is only in newer 5.X versions of
the MSys
> firmware if I remeber correctly, and only if the firmware can be
loaded
> OK.
>=20
> Regards
> Henrik
>=20
> On Sun, 16 Mar 2003, Gregg C Levine wrote:
>=20
> > Hello from Gregg C Levine
> > It seems to be my day for problems with this configuration. Using
the
> > "doc_loadbios" program found in the util directory of the mtd
> > collection, I've managed to write the firmware to the DoC, one was
the
> > one labeled "DOC2.FFF", and the other one was "doc42.exb", both
were
> > copied from the disk provided by M-SYS that's version 4.2 of their
> > series of tools.
> >
> > Now with the card inserted in the computer, it does not even
respond
> > to the <ctrl> <alt> B sequence, that M-SYS insists will prevent
the
> > firmware, from loading. Nor is there any message printed regarding
the
> > device. Now I am really lost. Oh, and this is an OEM computer
wearing
> > an Award BIOS.
> > -------------------
> > Gregg C Levine hansolofalcon at worldnet.att.net
> > ------------------------------------------------------------
> > "The Force will be with you...Always." Obi-Wan Kenobi
> > "Use the Force, Luke."=A0 Obi-Wan Kenobi
> > (This company dedicates this E-Mail to General Obi-Wan Kenobi )
> > (This company dedicates this E-Mail to Master Yoda )
> >
> >
> >
> >
> >
> > ______________________________________________________
> > Linux MTD discussion mailing list
> > http://lists.infradead.org/mailman/listinfo/linux-mtd/
> >
>=20
>=20
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/

Hello again from Gregg C Levine
Actually Henrik, it's also documented in the release notes for the
4.2.2 material for Linux for the Disk On Chip, as well. And from what
I can see also in the release notes in the 4.2 series of material as
well. I've contacted M-SYS technical support so I'll see what happens.
There's got to be something that I can do, as the company can't afford
to buy any of these things until sometime next month.
-------------------
Gregg C Levine hansolofalcon at worldnet.att.net
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."  Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )

New problem with DoC

[Henrik Nordstrom]

I did not get the bypass to work in the 4.2 firmware. Have only
succeeded using the M-Sys bypass when using 5.X firmware.

However, if the system does not even print the M-SYS banner when
programmed with the M-Sys firmware then the firmware on the module is
completely non-functional and the module needs to be reformatted (or at
a minimum have the firmware reinstalled). The M-Sys bypass only works if
the firmware works in the first place and can only deactivate the
installation of the emulated harddrive.

Reformatting a "busted" DoC having a bad firmware installed is a little
hard unless you have a burner, but there is some dirty tricks you can
try such as plugging the DoC module while the system is running and
other similar adventures, but is nothing I would recommend unless all
other options have been exhausted as it may easily burn both your board
and the DoC module..

Regards
Henrik



m?n 2003-03-17 klockan 12.31 skrev Gregg C Levine:

> Hello again from Gregg C Levine
> Actually Henrik, it's also documented in the release notes for the
> 4.2.2 material for Linux for the Disk On Chip, as well. And from what
> I can see also in the release notes in the 4.2 series of material as
> well. I've contacted M-SYS technical support so I'll see what happens.
> There's got to be something that I can do, as the company can't afford
> to buy any of these things until sometime next month.
> -------------------
> Gregg C Levine hansolofalcon at worldnet.att.net
> ------------------------------------------------------------
> "The Force will be with you...Always." Obi-Wan Kenobi
> "Use the Force, Luke."  Obi-Wan Kenobi
> (This company dedicates this E-Mail to General Obi-Wan Kenobi )
> (This company dedicates this E-Mail to Master Yoda )
> 
> 
> 
> 
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
-- 
Henrik Nordstrom <hno@marasystems.com>
MARA Systems AB

New problem with DoC

[Gregg C Levine]

<Please see below! Jasmine you too!>
> -----Original Message-----
> From: Jasmine Strong [mailto:jasmine at regolith.co.uk]
> Sent: Monday, March 17, 2003 8:45 AM
> To: Gregg C Levine
> Subject: Re: New problem with DoC
>=20
>=20
> On Monday, Mar 17, 2003, at 02:42 Europe/London, Gregg C Levine
wrote:
>=20
> > Hello from Gregg C Levine
> > It seems to be my day for problems with this configuration. Using
the
> > "doc_loadbios" program found in the util directory of the mtd
> > collection, I've managed to write the firmware to the DoC, one was
the
> > one labeled "DOC2.FFF", and the other one was "doc42.exb", both
were
> > copied from the disk provided by M-SYS that's version 4.2 of their
> > series of tools.
>=20
> Uh.  last I saw, doc_loadbios didn't understand .exb files.
>=20
> You should be using the Grub firmware anyway.
>=20
> -Jas.
Hello again from Gregg C Levine
Thanks folks. That worked. Funny thing, these devices, the solutions
suggested by the manufacturer didn't work. Which is what I expected.=20

Whereas the MTD method for reviving it, or even a new one for
installing the Grub Firmware worked. It still looks for the /boot
directory, and the menu.lst file. But at least it works.=20

Next question, how do I put that one, the /boot directory, and the
menu.list as when I would use a normal Grub booting arrangement in to
the DoC? Oh, and a custom kernel as well.
-------------------
P.S. David is my message formatting acceptable?

-------------------------------
Gregg C Levine hansolofalcon at worldnet.att.net
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."  Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )

New problem with DoC

[Russ Dill]

> Thanks folks. That worked. Funny thing, these devices, the solutions
> suggested by the manufacturer didn't work. Which is what I expected. 

Generally, if you want to use their stuff, I think you have to use their
dos based tools

> Next question, how do I put that one, the /boot directory, and the
> menu.list as when I would use a normal Grub booting arrangement in to
> the DoC? Oh, and a custom kernel as well.

right now, grub only supports filesystems on top of NFTL. It'd be really
nice to get YAFFS and JFFS2 support into grub. As a workaround, you may
be able to use a small NFTL partition, with cramfs (patches exist to add
cramfs to grub) containing a menu.lst and kernel, and then mount the
rest as YAFFS/JFFS2. Or of course just use NFTL

> P.S. David is my message formatting acceptable?

generally, its best to reply to relevant paragraphs right below that
paragraph, and then delete stuff that isn't relevant.

New problem with DoC

[Charles Manning]

On Tue, 18 Mar 2003 08:31, Russ Dill wrote:
[snip]
>
> > Next question, how do I put that one, the /boot directory, and the
> > menu.list as when I would use a normal Grub booting arrangement in to
> > the DoC? Oh, and a custom kernel as well.
>
> right now, grub only supports filesystems on top of NFTL. It'd be really
> nice to get YAFFS and JFFS2 support into grub. As a workaround, you may
> be able to use a small NFTL partition, with cramfs (patches exist to add
> cramfs to grub) containing a menu.lst and kernel, and then mount the
> rest as YAFFS/JFFS2. Or of course just use NFTL

There is a bootloader for YAFFS in CVS (in the direct subdirectory). Very 
simple. Should be very easy to add to grub.

-- CHarles

New problem with DoC

[Russ Dill]

> > right now, grub only supports filesystems on top of NFTL. It'd be really
> > nice to get YAFFS and JFFS2 support into grub. As a workaround, you may
> > be able to use a small NFTL partition, with cramfs (patches exist to add
> > cramfs to grub) containing a menu.lst and kernel, and then mount the
> > rest as YAFFS/JFFS2. Or of course just use NFTL
> 
> There is a bootloader for YAFFS in CVS (in the direct subdirectory). Very 
> simple. Should be very easy to add to grub.

you'd like to think so, unfortunately, grub is a "bit" weird in its API
and interfacing, adding cramfs support to grub was a bit of a pain. I'll
contract to add YAFFS to grub if someone needs it.