qnx.6.3 PE issues ...

Hi…

QNX ver: 6.3.0 - PE

  1. A classical issue: the following build file (which I copy as
    …altboot) worked with QXN 6.2.1.B, it does not work on 6.3.0. I wonder
    if you could give a hint as to what needs to be done? The error is:

unable to start “seedres”
unable to start pci-bios

so on

and so forth

  1. on a native QNX 6.3 system, the IDE does not refresh the workspace
    well, and I cannot see any thing after I do some random operations. I
    have to close/open/do-things to make the IDE come back. Any known
    workaround to force the IDE to refresh ok? (The IDE works well on windows).

  2. pardon my ignorance, but the drivers devf-* are not present in
    qnx.6.3 Is this suppose to be so? If it is, then I wonder why the
    documentation still refers to them?

  3. qnx.6.3 and 6.2.1 nodes do not see each other on /net/* Is this
    suppose to be so?



    Thanks for your help.

Regards…

Miguel.



\


\

GENERATED FILE - DO NOT EDIT

[+compress]
[virtual=x86,bios] .bootstrap = {
startup-bios -s 64k
PATH=/proc/boot:/bin:/sbin
LD_LIBRARY_PATH=/proc/boot:/dev/shmem:/lib:/lib/dll procnto
}
[+script] .script = {
seedres

These env variables inherited by all the programs which follow

TERM=qansi-m
HOSTNAME=chps
HOME=/root
PATH=/proc/boot:/bin:/usr/bin:/sbin:/usr/sbin
LD_LIBRARY_PATH=/proc/boot:/lib:/lib/dll:/usr/lib
DL_DEBUG=1
SHELL=/bin/ksh

Start the pci server

display_msg “Starting pci-bios server…”
pci-bios &
waitfor /dev/pci 30

Start the standard PC console driver and

make it the default output (reopen).

display_msg “Starting up console driver…”
devc-con -n6 &
waitfor /dev/con1
reopen /dev/con1

Pipe provides pipe() services.

display_msg “Starting pipe manager…”
pipe &
mqueue &
devc-pty &
waitfor /dev/pipe 15

Start eide driver to get drive access.

display_msg “Starting eide driver…”
devb-eide blk automount=hd0t77:/ &
waitfor /bin 15

\

Network drivers and filesystems

io-net -dspeedo -ptcpip
sleep 2
waitfor /dev/io-net 15
ifconfig en0 10.3.49.215 netmask 255.255.255.0 up
sleep 2
netmanager
mount -Tio-net -o"host=chps.saic.com" npm-qnet.so
sleep 1
#fs-nfs2 10.2:/usr/nto / 10.2:/ /usr/qnx4 &
/usr/sbin/inetd /etc/inetd.conf &

#serial port
/sbin/devc-ser8250 -b 19200 -F 3f8,4 2f8,3 3e8,9 2e8,f &

Start some extra shells on other consoles

reopen /dev/con2
[+session pri=10r] fesh &
reopen /dev/con3
[+session pri=10r] fesh &
reopen /dev/con4
[+session pri=15r] fesh &
reopen /dev/con5
[+session pri=20r] fesh &

Start a high priority shell just in case…

reopen /dev/con6
[+session pri=30r] fesh &
#[pri=25 +session] fesh &

Start the main shell

reopen /dev/con1
#[+session pri=10r] sh -c /etc/system/sysinit &
[+session pri=10r] fesh &

\

welcome

display_msg “…”
display_msg " Welcome to Neutrino on an embedded flash eide system "
display_msg " CHIPS, SIL. SAIC copyright 2003 "
display_msg " by: Miguel Simon, Oct, 2003 "
display_msg “…”

}
[dperms=0777 uid=0 gid=0]
[type=link] /tmp = /dev/shmem
[type=link] /dev/console = /dev/con1
[type=link] /usr/lib/ldqnx.so.2 = /proc/boot/libc.so.2
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/cat = /bin/cat
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/cp = /bin/cp
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/dd = /bin/dd
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/devb-eide =
/sbin/devb-eide
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/devb-fdc =
/sbin/devb-fdc
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/devb-ram =
/sbin/devb-ram
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/devc-con =
/sbin/devc-con
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/devc-pty =
/sbin/devc-pty
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/devc-ser8250 =
/sbin/devc-ser8250
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/df = /bin/df
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/dinit = /sbin/dinit
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/fesh = /bin/fesh
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/mqueue = /sbin/mqueue
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/ifconfig =
/sbin/ifconfig
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/ping = /usr/bin/ping
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/fs-cifs =
/usr/sbin/fs-cifs
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/fs-nfs2 =
/usr/sbin/fs-nfs2
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/fs-nfs3 =
/usr/sbin/fs-nfs3
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/fdisk = /sbin/fdisk
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/inetd =
/usr/sbin/inetd
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/io-net = /sbin/io-net
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/ls = /bin/ls
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/mv = /bin/mv
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/kill = /bin/kill
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/mount = /bin/mount
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/ln = /bin/ln
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/less = /usr/bin/less
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/mkdir = /bin/mkdir
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/netmanager =
/bin/netmanager
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/netstat =
/usr/bin/netstat
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/nfsd = /usr/sbin/nfsd
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/pci = /usr/sbin/pci
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/pci-bios =
/sbin/pci-bios
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/pidin = /bin/pidin
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/rm = /bin/rm
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/pipe = /sbin/pipe
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/route = /sbin/route
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/seedres =
/sbin/seedres
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/tinit = /sbin/tinit
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/slay = /bin/slay
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/sin = /bin/sin
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/sleep = /usr/bin/sleep
[gid=0 uid=0 perms=777 data=uip code=uip] /proc/boot/cam-disk.so =
/lib/dll/cam-disk.so
[gid=0 uid=0 perms=777 data=uip code=uip] /proc/boot/devn-speedo.so =
/lib/dll/devn-speedo.so
[gid=0 uid=0 perms=777 data=uip code=uip] /proc/boot/fs-qnx4.so =
/lib/dll/fs-qnx4.so
[gid=0 uid=0 perms=777 data=uip code=uip] /proc/boot/libcam.so.2 =
/lib/libcam.so.2
[gid=0 uid=0 perms=777 data=uip code=uip] /proc/boot/libsocket.so.2 =
/lib/libsocket.so.2
[type=link] /proc/boot/libsocket.so = /proc/boot/libsocket.so.2
[type=link] /proc/boot/libcam.so = /proc/boot/libcam.so.2
[gid=0 uid=0 perms=777 data=uip code=uip] /proc/boot/npm-qnet.so =
/lib/dll/npm-qnet.so
[gid=0 uid=0 perms=777 data=uip code=uip] /proc/boot/npm-tcpip-v4.so =
/lib/dll/npm-tcpip-v4.so
[type=link] /proc/boot/npm-tcpip.so = /proc/boot/npm-tcpip-v4.so
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/umount = /bin/umount
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/elvis = /bin/elvis
[type=link] /proc/boot/vi = /proc/boot/elvis
[gid=0 uid=0 perms=777 data=uip code=uip] /proc/boot/io-blk.so =
/lib/dll/io-blk.so
[gid=0 uid=0 perms=777 data=copy code=uip] /usr/bin/telnet = /usr/bin/telnet
[gid=0 uid=0 perms=777 data=copy code=uip] /usr/bin/ftp = /usr/bin/ftp
[gid=0 uid=0 perms=777 data=uip code=uip] /lib/libc.so.2 = /lib/libc.so.2
[gid=0 uid=0 perms=777 data=copy code=uip] /proc/boot/ksh = /bin/ksh
[type=link] /proc/boot/sh = /proc/boot/ksh

Miguel Simon <simon@ou.edu> wrote:

Hi…

QNX ver: 6.3.0 - PE

I can answer a couple of your questions, but I’ll leave the others for
someone else to answer.

  1. pardon my ignorance, but the drivers devf-* are not present in
    qnx.6.3 Is this suppose to be so? If it is, then I wonder why the
    documentation still refers to them?

They’re available separately in the Flash Filesystem & Embedding
Technology Development Kit. Unfortunately, we didn’t have time to go
through the docs and identify the pieces that are in the TDKs. I finished
doing that today.

  1. qnx.6.3 and 6.2.1 nodes do not see each other on /net/* Is this
    suppose to be so?

The default qnet in 6.3 isn’t compatible with the 6.2 version, but you
can use the compatible version instead. See the Using Qnet for Transparent
Distributed Processing chapter of the Neutrino User’s Guide.


Steve Reid stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems

Miguel Simon <simon@ou.edu> wrote:

Hi…

QNX ver: 6.3.0 - PE

  1. A classical issue: the following build file (which I copy as
    .altboot) worked with QXN 6.2.1.B, it does not work on 6.3.0. I wonder
    if you could give a hint as to what needs to be done? The error is:

I tried your file, yup.

But, the basic /boot/build/bios.build worked ok. mkifs did spit out
a bunch of warnings from your build file – though they didn’t relate
to seedres or pci-bios. Dunno what’s wrong.

  1. on a native QNX 6.3 system, the IDE does not refresh the workspace
    well, and I cannot see any thing after I do some random operations. I
    have to close/open/do-things to make the IDE come back. Any known
    workaround to force the IDE to refresh ok? (The IDE works well on windows).

The IDE self-hosted has a number of refresh/redraw problems.

  1. pardon my ignorance, but the drivers devf-* are not present in
    qnx.6.3 Is this suppose to be so? If it is, then I wonder why the
    documentation still refers to them?

They are no longer shipped as part of the core package, I think they
are part of the various (seperately available) BSP packages.

  1. qnx.6.3 and 6.2.1 nodes do not see each other on /net/* Is this
    suppose to be so?

Yes. New default qnet protocol, if you want to see 6.2.1 nodes from
6.3.0, you need to mount npm-qnet-compat.so instead of npm-qnet.so
(which defaults to the new npm-qnet-l4_lite.so).

-David

Please follow-up to newsgroup, rather than personal email.
David Gibbs
QNX Training Services
dagibbs@qnx.com

Hi Steve…

Thanks for the response.

As far as you know, the Flash Filesystem & Embedding TDK, is this a
separate purchased item? In other words, is this TDK not part of the PE
edition, or do I need to consult our sales rep?? Thanks.

Regards…

Miguel.


Steve Reid wrote:

Miguel Simon <> simon@ou.edu> > wrote:

Hi…


QNX ver: 6.3.0 - PE


I can answer a couple of your questions, but I’ll leave the others for
someone else to answer.


3. pardon my ignorance, but the drivers devf-* are not present in
qnx.6.3 Is this suppose to be so? If it is, then I wonder why the
documentation still refers to them?


They’re available separately in the Flash Filesystem & Embedding
Technology Development Kit. Unfortunately, we didn’t have time to go
through the docs and identify the pieces that are in the TDKs. I finished
doing that today.


4. qnx.6.3 and 6.2.1 nodes do not see each other on /net/* Is this
suppose to be so?


The default qnet in 6.3 isn’t compatible with the 6.2 version, but you
can use the compatible version instead. See the Using Qnet for Transparent
Distributed Processing chapter of the Neutrino User’s Guide.


Steve Reid > stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems

Hi David…

David Gibbs wrote:

Miguel Simon <> simon@ou.edu> > wrote:

Hi…


QNX ver: 6.3.0 - PE

\

  1. A classical issue: the following build file (which I copy as
    .altboot) worked with QXN 6.2.1.B, it does not work on 6.3.0. I wonder
    if you could give a hint as to what needs to be done? The error is:


    I tried your file, yup.

But, the basic /boot/build/bios.build worked ok. mkifs did spit out
a bunch of warnings from your build file – though they didn’t relate
to seedres or pci-bios. Dunno what’s wrong.

Ok, I suppose that I can restart from the basic build and go from there.

David, I do have a question. When I get an embedded hardrive, do I need
to reformat the hardrive for it to work with QNX 6.3 runtimes? In other
words, if I update the .boot, .altboot, the /bin directory and other
with 6.3 stock items, will this work, or do I still have to reformat the
hardrive? Thanks.

  1. on a native QNX 6.3 system, the IDE does not refresh the workspace
    well, and I cannot see any thing after I do some random operations. I
    have to close/open/do-things to make the IDE come back. Any known
    workaround to force the IDE to refresh ok? (The IDE works well on windows).


    The IDE self-hosted has a number of refresh/redraw problems.

I see. I suppose that you do not know of a work around then? Thanks.

Regards…

Miguel.

  1. pardon my ignorance, but the drivers devf-* are not present in
    qnx.6.3 Is this suppose to be so? If it is, then I wonder why the
    documentation still refers to them?


    They are no longer shipped as part of the core package, I think they
    are part of the various (seperately available) BSP packages.

    \
  2. qnx.6.3 and 6.2.1 nodes do not see each other on /net/* Is this
    suppose to be so?


    Yes. New default qnet protocol, if you want to see 6.2.1 nodes from
    6.3.0, you need to mount npm-qnet-compat.so instead of npm-qnet.so
    (which defaults to the new npm-qnet-l4_lite.so).

-David

Miguel Simon <simon@ou.edu> wrote:

Hi Steve…

Thanks for the response.

As far as you know, the Flash Filesystem & Embedding TDK, is this a
separate purchased item? In other words, is this TDK not part of the PE
edition, or do I need to consult our sales rep?? Thanks.

You need to purchase the TDKs separately, so yes, you should talk to your
sales rep.


Steve Reid stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems

Bill Caroselli <QTPS@earthlink.net> wrote:

There is a nwe protocol manager called npm-qnet-compat.so. This still
speaks the old QNX protoocol. So a 6.3 system can network with a 6.2
system.

I don’t think you can run both npm-qnet.so and npm-qnet-compat.so at the
same time.

Actually, npm-qnet.so is just a symlink. By default, it points to the new
module, npm-qnet-l4_lite.so, but you can make it point to
npm-qnet-compat.so instead.


Steve Reid stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems

“Miguel Simon” <simon@ou.edu> wrote in message
news:cba4aq$gef$1@inn.qnx.com

  1. qnx.6.3 and 6.2.1 nodes do not see each other on /net/* Is this
    suppose to be so?



    6.3 uses a new native network protocolm which is NOT compatable with the old

native network protocol. BUT . . . .

There is a nwe protocol manager called npm-qnet-compat.so. This still
speaks the old QNX protoocol. So a 6.3 system can network with a 6.2
system.

I don’t think you can run both npm-qnet.so and npm-qnet-compat.so at the
same time.

Someone else will have to comment on the other issues.

Miguel Simon <simon@ou.edu> wrote:

Hi David…

David, I do have a question. When I get an embedded hardrive, do I need
to reformat the hardrive for it to work with QNX 6.3 runtimes? In other
words, if I update the .boot, .altboot, the /bin directory and other
with 6.3 stock items, will this work, or do I still have to reformat the
hardrive? Thanks.

No, you don’t have to reformat the drive. The dev system installer
does a partition install, rather than an update, but for a target/embedded
hard drive, as long as you know where everything went, you can do the
update as you described.


  1. on a native QNX 6.3 system, the IDE does not refresh the workspace
    well, and I cannot see any thing after I do some random operations. I
    have to close/open/do-things to make the IDE come back. Any known
    workaround to force the IDE to refresh ok? (The IDE works well on windows).


    The IDE self-hosted has a number of refresh/redraw problems.

I see. I suppose that you do not know of a work around then? Thanks.

Um…use Windows based IDE?

-David

Please follow-up to newsgroup, rather than personal email.
David Gibbs
QNX Training Services
dagibbs@qnx.com

Hi David…

David Gibbs wrote:

Miguel Simon <> simon@ou.edu> > wrote:

I see. I suppose that you do not know of a work around then? Thanks.


Um…use Windows based IDE?

I think that I will wait for a patch to come along. I am trying to get
away from Windows. Will try Linux next. Thanks again; I appreciate your
help.

Regards…

Miguel.


-David

What new stuff was added to the new QNET protocol? Can I read about this
somehwere?

Thanks
Kevin

“Bill Caroselli” <QTPS@Earthlink.net> wrote in message
news:cbbu0s$t9a$1@inn.qnx.com

“Miguel Simon” <> simon@ou.edu> > wrote in message
news:cba4aq$gef$> 1@inn.qnx.com> …

  1. qnx.6.3 and 6.2.1 nodes do not see each other on /net/* Is this
    suppose to be so?



    6.3 uses a new native network protocolm which is NOT compatable with the
    old
    native network protocol. BUT . . . .

There is a nwe protocol manager called npm-qnet-compat.so. This still
speaks the old QNX protoocol. So a 6.3 system can network with a 6.2
system.

I don’t think you can run both npm-qnet.so and npm-qnet-compat.so at the
same time.

Someone else will have to comment on the other issues.

Kevin Stallard <kevin@fflyingrobots.com> wrote:
KS > What new stuff was added to the new QNET protocol? Can I read about this
KS > somehwere?

KS > Thanks
KS > Kevin

Can someone answer this? I’m curious too.