devb-doc does not create a /dev/hdx entry when booted alone

I have built an image of QNX RTOS 6.1.0 that I want to load from a
DiskOnChip that exists on the PC104 system I am using. When I use the
development system and start devb-doc everything works fine. But, when it
use the following .build file and boot from the DiskOnChip - I get the DOC
driver load message just fine but I get no device built in the /dev
directory.

Any ideas?

…build file follows:

###########################################################################

Neutrino on an PC BIOS compatible system

This is for building a bootable neutrino image with a minimal

filesystem. (i.e. only what is in the image)

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
PATH=/proc/boot LD_LIBRARY_PATH=/proc/boot:/dev/shmem procnto
}

[search=/sbin:/usr/sbin:/bin:/usr/bin:/lib:/lib/dll:/boot/sys]

[search=/x86/bin:/x86/boot/sys:/x86/lib/dll:/x86/lib:/x86/sbin:/opt/m-sys/us
r/sbin]
[+script] startup-script = {

Start up some consoles

devc-con -n4 &
reopen /dev/con1

display_msg .
display_msg Welcome to Neutrino JES EPROM

Start the pci server

seedres
pci-bios &
waitfor /dev/pci

DiskOnChip driver

devb-doc blk automount=hd0t79:/ &
waitfor /bin 45

Some common servers

pipe &
mqueue &
devc-ser8250 &
devc-pty &

These env variables inherited by all the programs which follow

SYSNAME=nto
TERM=qansi
LD_LIBRARY_PATH=/proc/boot:/dev/shmem
PATH=/proc/boot

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
[type=link] /usr/lib/ldqnx.so.1=/proc/boot/libc.so.1

We use the “c” shared lib (which also contains the runtime linker)

libc.so.2
libc.so.1

Just incase someone needs floating point…

fpemu.so.2

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 the DiskOnChip driver.

devb-doc

Include the hard disk files so we can access files on the disk

libcam.so.1
io-blk.so

filesystem required shared libs

cam-disk.so
fs-qnx4.so

Include pci server

pci-bios
seedres

Use the “public domain korn shell” as the default shell “sh”

sh=ksh

or use the smaller non-posix “Fat Embedded Shell” as the default shell

“sh”
#sh=fesh

Other executables

pipe
mqueue
devc-ser8250
devc-pty
ls
cat
pidin
uname
df
slay

###########################################################################




###########################################################################

John

The only thing I see that is different to the build file supplied with the
diskonchip is that you specify automount=hd0t79:/ not hd0t77:/

Are you using the latest devb-doc form M-Systems, not the one supplied on
the qnxrtp6.10 distribution.

The old devb-doc (6.0)that is supplied with 6.1, works from the comand line,
but does not work when you try and boot it.

“John Sanders” <jsanders@radix.net> wrote in message
news:9od1u6$slf$1@inn.qnx.com

I have built an image of QNX RTOS 6.1.0 that I want to load from a
DiskOnChip that exists on the PC104 system I am using. When I use the
development system and start devb-doc everything works fine. But, when it
use the following .build file and boot from the DiskOnChip - I get the DOC
driver load message just fine but I get no device built in the /dev
directory.

Any ideas?

.build file follows:


###########################################################################

Neutrino on an PC BIOS compatible system

This is for building a bootable neutrino image with a minimal

filesystem. (i.e. only what is in the image)

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
PATH=/proc/boot LD_LIBRARY_PATH=/proc/boot:/dev/shmem procnto
}

[search=/sbin:/usr/sbin:/bin:/usr/bin:/lib:/lib/dll:/boot/sys]

[search=/x86/bin:/x86/boot/sys:/x86/lib/dll:/x86/lib:/x86/sbin:/opt/m-sys/us
r/sbin]
[+script] startup-script = {

Start up some consoles

devc-con -n4 &
reopen /dev/con1

display_msg .
display_msg Welcome to Neutrino JES EPROM

Start the pci server

seedres
pci-bios &
waitfor /dev/pci

DiskOnChip driver

devb-doc blk automount=hd0t79:/ &
waitfor /bin 45

Some common servers

pipe &
mqueue &
devc-ser8250 &
devc-pty &

These env variables inherited by all the programs which follow

SYSNAME=nto
TERM=qansi
LD_LIBRARY_PATH=/proc/boot:/dev/shmem
PATH=/proc/boot

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
[type=link] /usr/lib/ldqnx.so.1=/proc/boot/libc.so.1

We use the “c” shared lib (which also contains the runtime linker)

libc.so.2
libc.so.1

Just incase someone needs floating point…

fpemu.so.2

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 the DiskOnChip driver.

devb-doc

Include the hard disk files so we can access files on the disk

libcam.so.1
io-blk.so

filesystem required shared libs

cam-disk.so
fs-qnx4.so

Include pci server

pci-bios
seedres

Use the “public domain korn shell” as the default shell “sh”

sh=ksh

or use the smaller non-posix “Fat Embedded Shell” as the default shell

“sh”
#sh=fesh

Other executables

pipe
mqueue
devc-ser8250
devc-pty
ls
cat
pidin
uname
df
slay


###########################################################################

.
.
.

###########################################################################

Yes - I just got the 5.0 devb-dev driver from m-sys. It works fine. The
4.2 devb-doc is only for RTOS 6.0 according to m-sys - but this is the one
that loads from the distribution when I installed 6.1 from scratch from the
CD.

Anyway, all is well now and thanks for looking into this for me.