We have a system running on an SBC-357 board from AAEON. We have outfitted it with
16M RAM and an 8M DiskOnChip (DOC). The DOC 2000 was our first choice, but since
it is being discontinued in favor of DOC Millennium we tried one of those devices.
We can get both to become bootable, but only the DOC 2000 works completely.
The DOC Millennium gets to the message “QNX Loading…” and waits for a long period
of time before displaying an error message from mount indicating that /dev/tffs0
cannot be found. Of course, the whole thing ends there.
We are wondering if anybody else has experienced this problem on any other boards,
but especially interested in anyone using the SBC-357.
-Paul
Paul N. Leonard <paull@ifsreg.com> wrote:
We have a system running on an SBC-357 board from AAEON. We have outfitted it with
16M RAM and an 8M DiskOnChip (DOC). The DOC 2000 was our first choice, but since
it is being discontinued in favor of DOC Millennium we tried one of those devices.
We can get both to become bootable, but only the DOC 2000 works completely.
The DOC Millennium gets to the message “QNX Loading…” and waits for a long period
of time before displaying an error message from mount indicating that /dev/tffs0
cannot be found. Of course, the whole thing ends there.
We are wondering if anybody else has experienced this problem on any other boards,
but especially interested in anyone using the SBC-357.
I’ve gotten a DiskOnChip Millenium 2000 (not sure which this is, but I think
it is the new one) working on a Versalogic VSBC-6 SBC from Versalogic.
I needed a new version of the Fsys.diskonchip for the Millenium 2000 as
opposed to the old one that worked with the earlier (not Millenium labelled)
DiskOnChip devices.
Of course, newer meant an April 14, 1999 dated Fsys.diskonchip, rather than
a Mar 1998 version. If you already have the April 1999 version, I’ve got
no further ideas.
-David