Arve Slenes <arve@datarespons.no> wrote:
Hello Arve,
The driver cannot find the DOC. Try the option “devb-doc doc addr=0xd0000” if
that is where you feel the DOC is installed at. Also the driver acesses the
DOC in 32-bit mode, depending on your board, this may not work, you might
try “devb-doc doc 8bit”.
This is probably your case:
You may have to initialize the DOC in DOS first…you would have to get the
following tools from M-Systems. Boot from DOS and run DINFO.EXE utility(from
M-Systems) It should find the DiskOnChip, and report it’s address. You should
then run DFORMAT.EXE (also from M-Systems) utility:
DFORMAT /win= /y /s:doc50.exb /nopnp
where was reported by DINFO.EXE (usually “d000”). Note
that it’s “d000”, not “d0000” or “0xd000”.
You can now boot QNX6.1, start DiskOnChip driver and it should create an entry
in /dev/hd#, where # is the number of your DOC and proceed to create a QNX
filesystem:
Clear DOC’s partition table:
dd if=/dev/zero of=/dev/hd# count=100
Set up partition…
fdisk /dev/hd# add -f 1 qnx all
fdisk /dev/hd# boot qnx
fdisk /dev/hd# loader
fdisk /dev/hd# show
Mount partition…
mount -e /dev/hd#
Initialize filesystem on DOC partition
dinit -hb /dev/hd#t77
Create a directory…and mount DOC
mkdir -p /mnt/doc
mount /dev/hd#t77 /mnt/doc
Now you can add files and build an image to boot from the DOC.
I was able to get this to work, with a DiskOnChip PCI Evaluation
Board(DOC TSOP-I EVB PCI ZIF) with a Millenium Plus(8 M) part…once we
installed and booted from a DOS 6.22 ;-} machine and successfully ran the two
aforementioned utilities.
Good Luck,
Chris
Hi!
I’m using a DigitalLogic 586SL-card with 32M RAM and a 16M DiskOnChip
on QNX RTP. When trying to start the devb-doc driver I get the
following message:
DiskOnChip driver, ver. 5.00
No doc interfaces found
What could be possible causes for this? Or: What actions can I do to get
closer
to the answer of problem?
I have tried to specify the exact base for the interface as set in the
BIOS
(e.g. 0xd0000), but to no difference.
Regards
Arve
PS! I have also used the 6.0 driver with no success.