Keyboard dead on embedded install

I’m setting up a a minimal install, booting from CompactFlash.
Photon is not involved.
For some reason, on this board, the keyboard is dead once
the prompt is displayed.
Unplugging the keyboard from the live system and plugging it back revives it.
Any ideas?

The version is Patch B.

This is just a wild guess. Try booting without the mount connected
and see if the keyboard still does not work on startup.

Previously, Alex Cellarius wrote in qdn.public.qnxrtp.installation:

I’m setting up a a minimal install, booting from CompactFlash.
Photon is not involved.
For some reason, on this board, the keyboard is dead once
the prompt is displayed.
Unplugging the keyboard from the live system and plugging it back revives it.
Any ideas?

The version is Patch B.
\


Mitchell Schoenbrun --------- maschoen@pobox.com

On Wed, 13 Jun 2001 13:03:49 -0700, Mitchell Schoenbrun <maschoen@pobox.com> wrote:

This is just a wild guess. Try booting without the mount connected

The “mount” connected?

and see if the keyboard still does not work on startup.

Previously, Alex Cellarius wrote in qdn.public.qnxrtp.installation:
I’m setting up a a minimal install, booting from CompactFlash.
Photon is not involved.
For some reason, on this board, the keyboard is dead once
the prompt is displayed.
Unplugging the keyboard from the live system and plugging it back revives it.
Any ideas?

The version is Patch B.



\

Mitchell Schoenbrun --------- > maschoen@pobox.com

Previously, Alex Cellarius wrote in qdn.public.qnxrtp.installation:

The “mount” connected?

Sorry, mouse.


Mitchell Schoenbrun --------- maschoen@pobox.com

Is devi-hirun invoke. I’ve seen some keyboard that need a -R (prevents
reset).

“Alex Cellarius” <acellarius@systems104.co.za> wrote in message
news:1103_992461284@pentiumii…

I’m setting up a a minimal install, booting from CompactFlash.
Photon is not involved.
For some reason, on this board, the keyboard is dead once
the prompt is displayed.
Unplugging the keyboard from the live system and plugging it back revives
it.
Any ideas?

The version is Patch B.

There are two devc-con in setup script, aren’t they?


“Alex Cellarius” <acellarius@systems104.co.za> wrote in message
news:1106_992553534@pentiumii…

On Wed, 13 Jun 2001 17:10:28 -0700, Mitchell Schoenbrun
maschoen@pobox.com> > wrote:
Previously, Alex Cellarius wrote in qdn.public.qnxrtp.installation:
The “mount” connected?

Sorry, mouse.

Ah. Mouse was connected via serial port, but disconnecting did not make a
difference.
It’s not need in this config (embedded networked device).

Here’s the build file:


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

This buildfile is for building a bootable Neutrino-2 image that will

run on the PC BIOS compatible system from EIDE connected CompactFlash

Note that the default image links at 4M. If you have 4M or less,

uncomment the line below

[image=1m]

August 30, 2000

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

[search=/sbin:/usr/sbin:/bin:/usr/bin:/lib:/lib/dll:/boot/sys]
[virtual=x86,bios +compress] boot = {
startup-bios -Nmachine-name
PATH=/proc/boot:/bin:/sbin:/usr/bin
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 Booting Neutrino from the CompactFlash.

Start the pci server

pci-bios &
waitfor /dev/pci

EIDE driver

devb-eide blk automount=hd0t79:/ &

Wait for a bin for the rest of the commands (up to 30 secs)

waitfor /bin 30

Some common servers

pipe &
mqueue &
devc-con &
io-net -dns83815 -pttcpip if=en0:192.9.200.2

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.1=/proc/boot/libc.so

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

libc.so

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 the drivers.

devb-eide
sh

Include pci server

pci-bios
pipe
mqueue
io-net

On Wed, 13 Jun 2001 17:10:28 -0700, Mitchell Schoenbrun <maschoen@pobox.com> wrote:

Previously, Alex Cellarius wrote in qdn.public.qnxrtp.installation:
The “mount” connected?

Sorry, mouse.

Ah. Mouse was connected via serial port, but disconnecting did not make a difference.
It’s not need in this config (embedded networked device).

Here’s the build file:

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

This buildfile is for building a bootable Neutrino-2 image that will

run on the PC BIOS compatible system from EIDE connected CompactFlash

Note that the default image links at 4M. If you have 4M or less,

uncomment the line below

[image=1m]

August 30, 2000

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

[search=/sbin:/usr/sbin:/bin:/usr/bin:/lib:/lib/dll:/boot/sys]
[virtual=x86,bios +compress] boot = {
startup-bios -Nmachine-name
PATH=/proc/boot:/bin:/sbin:/usr/bin 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 Booting Neutrino from the CompactFlash.

Start the pci server

pci-bios &
waitfor /dev/pci

EIDE driver

devb-eide blk automount=hd0t79:/ &

Wait for a bin for the rest of the commands (up to 30 secs)

waitfor /bin 30

Some common servers

pipe &
mqueue &
devc-con &
io-net -dns83815 -pttcpip if=en0:192.9.200.2

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.1=/proc/boot/libc.so

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

libc.so

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 the drivers.

devb-eide
sh

Include pci server

pci-bios
pipe
mqueue
io-net

On Thu, 14 Jun 2001 08:36:06 -0400, “Mario Charest” <mcharest@zinformatic.com> wrote:

Is devi-hirun invoke. I’ve seen some keyboard that need a -R (prevents
reset).

No, just devc-con. Is devi-hirun needed for console type applications?

Previously, Alex Cellarius wrote in qdn.public.qnxrtp.installation:

On Wed, 13 Jun 2001 17:10:28 -0700, Mitchell Schoenbrun <> maschoen@pobox.com> > wrote:
Sorry, mouse.

Ah. Mouse was connected via serial port, but disconnecting did not make a difference.
It’s not need in this config (embedded networked device).

Ok, I was thinking of course of a PS/2 mouse which seems to have an
incestuous relationship to the keyboard hardware.


Mitchell Schoenbrun --------- maschoen@pobox.com

On Thu, 14 Jun 2001 15:41:51 -0400, “Alex Chapiro” <achapiro@qnx.com> wrote:

There are two devc-con in setup script, aren’t they?

Bingo.
Sharp eyes - thanks.