I have gone back to trying and get my MD2800-D08 to boot
like the MD2200-D08, but cannot quite get there. Followed
all the directions and have the latest firmware and drivers,
yet still have a problem. At least now it is recognizing the
device upon boot. Odd thing is it fails when mounting the
device.
Here is what it looks like:
QNX Loader
Boot Partition 1
Press Esc for alternate OS…
48MHz 386 AT bus boot modules:
sys/Proc32
sys/Slib32
sys/Slib16
/bin/Fsys
/bin/Fsys.diskonchip
/bin/mount
/bin/sinit
Starting QNX…
Then a very long pause and finally I get this last message
and the systems just hangs there, keyboard dead and all:
mount -p: open() on /dev/tffs0 failed: No such file or directory
If I boot from a floppy I can mount the diskonchip with no problem
and everything is there, accessible and appears to be fine.
Any ideas, suggestions, or comments are welcomed!!!
Can you post your build file
Previously, Paul N. Leonard wrote in qdn.public.qnx4:
{ I have gone back to trying and get my MD2800-D08 to boot
{ like the MD2200-D08, but cannot quite get there. Followed
{ all the directions and have the latest firmware and drivers,
{ yet still have a problem. At least now it is recognizing the
{ device upon boot. Odd thing is it fails when mounting the
{ device.
{
{ Here is what it looks like:
{ QNX Loader
{ Boot Partition 1
{ Press Esc for alternate OS…
{ 48MHz 386 AT bus boot modules:
{ sys/Proc32
{ sys/Slib32
{ sys/Slib16
are you running anything that needs Slib16?
{ /bin/Fsys
{ /bin/Fsys.diskonchip
{ /bin/mount
{ /bin/sinit
{ Starting QNX…
{
{ Then a very long pause and finally I get this last message
{ and the systems just hangs there, keyboard dead and all:
{
{ mount -p: open() on /dev/tffs0 failed: No such file or directory
{
{ If I boot from a floppy I can mount the diskonchip with no problem
{ and everything is there, accessible and appears to be fine.
is this with the same image as .boot on the DOC??
{ Any ideas, suggestions, or comments are welcomed!!!
{
do an ls of /dev and see if the DOC is tffs0.
–
Pat Ford email: pford@qnx.com
QNX Software Systems, Ltd. WWW: http://www.qnx.com
(613) 591-0931 (voice) mail: 175 Terence Matthews
(613) 591-3579 (fax) Kanata, Ontario, Canada K2M 1W8
Thanks Pat,
Let me first respond to your questions, then I’ll get to what the
problem turned out to be.
Can you post your build file
No need for the build file as you will see later, although looking
at that again is what led to the solution.
{ sys/Slib16
are you running anything that needs Slib16?
My understanding is that we do require it for loading floating point
emulation, since our CPU has no co-processor, and for using the
Watcom debugger over a serial port.
The problem turned out to be just what I thought it was not.
We have the latest firmware and drivers for the DiskOnChip,
and they are stored in several places on both development stations,
except on one development station the driver under /bin was the
previous version. I had checked the versions everywhere else but
there and it wasn’t until I went through the build script that
it dawned on me “maybe this file is different”. (duh)
My apologies for the bandwidth used here on such an oversight,
but maybe it will help someone else in the future. I know I’m going
to be more aware of multiple copies now.
-Paul
Glad you got it working
Previously, Paul N. Leonard wrote in qdn.public.qnx4:
{ Thanks Pat,
{
{ Let me first respond to your questions, then I’ll get to what the
{ problem turned out to be.
{
{ >
{ > Can you post your build file
{
{ No need for the build file as you will see later, although looking
{ at that again is what led to the solution.
{
{ > { sys/Slib16
{ >
{ > are you running anything that needs Slib16?
{
{ My understanding is that we do require it for loading floating point
{ emulation, since our CPU has no co-processor, and for using the
{ Watcom debugger over a serial port.
{
{ The problem turned out to be just what I thought it was not.
{ We have the latest firmware and drivers for the DiskOnChip,
{ and they are stored in several places on both development stations,
{ except on one development station the driver under /bin was the
{ previous version. I had checked the versions everywhere else but
{ there and it wasn’t until I went through the build script that
{ it dawned on me “maybe this file is different”. (duh)
btdt repeatedly
{
{ My apologies for the bandwidth used here on such an oversight,
{ but maybe it will help someone else in the future. I know I’m going
{ to be more aware of multiple copies now.
{
{ -Paul
{
–
Pat Ford email: pford@qnx.com
QNX Software Systems, Ltd. WWW: http://www.qnx.com
(613) 591-0931 (voice) mail: 175 Terence Matthews
(613) 591-3579 (fax) Kanata, Ontario, Canada K2M 1W8