I want to boot qnx from diskonchip2000. I used a buildfile downloaded from m-sys.com (v5.04).When I get my image file system under qnx 6.10 according to the manual,I burn it to diskonchip.The result shows that it cannot boot from diskonchip.
I also try boot from diskonchip which has dos system.Then it was done.
So It’s not the question of bios and diskonchip.
Then what can I do? 
What errors do you get when you try to boot? I have booted QNX on various DoC systems without issue in the past.
“Disk boot failure . Insert system disk and press enter”
prox-1520(NS-geode mini board with vga/sound/lan)
cpu:built-in NS-geode™ gx1-300Mhz.
diskonchip2000 32mb (m-sys)
We are working on this on IRC. I will get gpfly to post the results once we figure them out…
Thanks for you help.But it seems this is not the end.I do the following instructions as you said:
devb-doc;
dd if=/dev/zero of=/dev/ha1 count=100;
fdisk /dev/hd1 add -f 1 qnx all;
mount -e /dev/hd1;
fdisk /dev/hd1 boot;
dloader /dev/hd1 pc1;
dinit -h /dev/hd1t77;
dloader /dev/hd1t77 pc2;
mount /dev/hd1t77 /mnt/diskonchip;
Then:
mkdir /mnt/diskonchip/bin;
mkdir /mnt/diskonchip/sbin;
mkdir /mnt/diskonchip/lib;
cp -R /x86/bin/* /mnt/diskonchip/bin;
cp -R /x86/sbin/* /mnt/diskonchip/sbin;
and,
cd /boot
mkifs -v build/bios.diskonchip.build fs/bios.diskonchip.ifs
cp fs/bios.diskonchip.ifs /mnt/diskonchip/.boot
umount /mnt/diskonchip;
shutdown.
Enter bios setup.disable all hard disks;
boot.then get:
“Disk boot failure insert system disk and press enter”
bios.diskonchip.build:
###########################################################################
Neutrino on an PC BIOS compatible system
This is for building a bootable neutrino image that will run from its
own filesystem partition on M-Systems DiskOnChip.
Note that the default image links at 4M. If you have 4M or less,
uncomment the line below
[image=1m]
###########################################################################
[virtual=x86,bios +compress] boot = {
startup-bios -Nmachine-name
PATH=/proc/boot:/bin:/sbin LD_LIBRARY_PATH=/proc/boot:/dev/shmem:/lib:/lib/dll procnto
}
[+script] startup-script = {
Start up some consoles
devc-con -n4 &
reopen /dev/con1
display_msg Welcome to Neutrino on an PC compatible BIOS system
Start the pci server
seedres
pci-bios &
waitfor /dev/pci
Disk drivers (The default one and some fun others for your pleasure…)
devb-doc blk automount=hd0t77:/ &
Wait for a bin for the rest of the commands (up to 30 secs)
waitfor /bin 30
Some common servers
pipe &
mqueue &
devc-pty &
These env variables inherited by all the programs which follow
SYSNAME=nto
TERM=qansi
Start some extra shells on other consoles
reopen /dev/con2
[+session] sh &
reopen /dev/con3
[+session] sh &
Start a high priority shell just in case…
reopen /dev/con4
[pri=25 +session] sh &
Start the main shell
reopen /dev/con1
[+session] sh
[+session] login -p
}
Cheat and make the /temp point to the shared memory area…
[type=link] /tmp=/dev/shmem
Redirect console messages for syslog
[type=link] /dev/console=/dev/con1
Programs require the runtime linker (ldqnx.so) to be at a fixed location
[type=link] /usr/lib/ldqnx.so.2=/proc/boot/libc.so
We use the “c” shared lib (which also contains the runtime linker)
libc.so
Just incase someone needs floating point…
fpemu.so.2
Include the socket library
libsocket.so
Include the hard disk files so we can access files on the disk
libcam.so
io-blk.so
filesystem required shared libs
cam-disk.so
fs-qnx4.so
The files above this line can be shared by mutiple processes
[data=c]
Executables must currently be below this line
Include a console driver
devc-con
Include DiskOnChip driver.
devb-doc
Include pci server
pci-bios
seedres
###########################################################################
Interrupt Assignments
---------------------
vector: 0
trigger: rising edge
device: 8254 (system timer)
vector: 1
trigger: rising edge
device: Keyboard
vector: 2
trigger: rising edge
device: Cascade from second 8259 controller
vector: 3
trigger: rising edge
device: Serial 2
vector: 4
trigger: rising edge
device: Serial 1
vector: 5-12
trigger: rising edge
device: unassigned
vector: 13
trigger: rising edge
device: Coprocessor
vector: 14,15
trigger: rising edge
device: unassigned
vector: 0x80000000 (X86_INTR_CLASS_NMI+0) (non-maskable)
trigger: rising edge
device: system board error (SERR# NMI)
vector: 0x80000001 (X86_INTR_CLASS_NMI+1) (non-maskable)
trigger: rising edge
device: ISA I/O check error (IOCHK# NMI)
###########################################################################
Try just doing this…
dd if=/dev/zero of=/dev/hd1 count=100
dloader /dev/hd1 pc1
And reboot and boot from the DOC. What happens? If we can’t get this working nothing else matters.
Nothing happen.The same question.
I have no time.God
you have done :fdisk /dev/hd1
but in your buildfile, it is "devb-doc blk automount=hd0t77:/ & "
in my opinion, this is the difference .