Hi,
I just installed QNX 6.2.1 (probably with armle) but don’t know how to
start device driver development. Can anyone please give me guideline
or tutorial links as reference for me to kick start?
The the reference I tried to follow is as follow:
http://eqip.openqnx.com/ipaq_bsp/cross_development.html
But I don’t know how to create the development enviornment like that
in QNX OS.
Your suggestion is highly appreciated.
Thanks
Sam
I just installed QNX 6.2.1 (probably with armle) but don’t know how to
You should use the current version, 6.3, instead. If you are a hobbyist, you
can use the compiler and command line tools free for non-commercial use. If
this is a commercial project, you can use it for evaluation for 30 days.
Just see:
http://www.qnx.com/products/eval/index.html
start device driver development.
What kind of driver do you want to develop? Either use the resource manager
framework described in “Writing a resource manager” chapter, or use one of
the Driver Development Kits from the QNX Website.
Can anyone please give me guideline
or tutorial links as reference for me to kick start?
Download the QNX Quickstart Guide, It is offered as first file in the
download list after you’ve chosen your dev host and accepted the Eula on the
weblink I mentioned above.
Cheers,
Malte
I don’t have license key for 6.3. Are the compiler and commandline
tools still available in 6.2.1?
Thanks
Sam
Thunderbladewrote:
[quote:28b9faf653]I just installed QNX 6.2.1 (probably with armle)
but don’t know how to
You should use the current version, 6.3, instead. If you are a
hobbyist, you
can use the compiler and command line tools free for non-commercial
use. If
this is a commercial project, you can use it for evaluation for 30
days.
Just see:
http://www.qnx.com/products/eval/index.html
start device driver development.
What kind of driver do you want to develop? Either use the resource
manager
framework described in “Writing a resource manager” chapter, or use
one of
the Driver Development Kits from the QNX Website.
Can anyone please give me guideline
or tutorial links as reference for me to kick start?
Download the QNX Quickstart Guide, It is offered as first file in
the
download list after you’ve chosen your dev host and accepted the Eula
on the
weblink I mentioned above.
Cheers,
Malte[/quote:28b9faf653]
sammmsammm wrote:
I don’t have license key for 6.3. Are the compiler and commandline
Easy enough to get one, it’s sent at the end of the main download of 6.3.0. Then, once you’ve signed up with the key you can install the ddks from http://www.qnx.com/download/group.html?programid=9380
tools still available in 6.2.1?
Doesn’t seem to be at qnx.com. I imagine it’ll be on openqnx.com, qnxzone.com, and bittorrent and the likes.
Evan
Evan Hillas wrote:
tools still available in 6.2.1?
Doesn’t seem to be at qnx.com. I imagine it’ll be on openqnx.com,
qnxzone.com, and bittorrent and the likes.
Err, I was thinking the QNX NC621 iso. Though, the recommendation still applies for the DDKs.
Evan
Malte Mundt wrote:
I just installed QNX 6.2.1 (probably with armle) but don’t know how to
You should use the current version, 6.3, instead. If you are a hobbyist, you
can use the compiler and command line tools free for non-commercial use. If
this is a commercial project, you can use it for evaluation for 30 days.
Just see:
http://www.qnx.com/products/eval/index.html
start device driver development.
Encourage this guy. QNX drivers for x86 have fallen so far
behind it’s hard to find x86 machines old enough to run QNX.
We need more people doing device drivers.
Getting rid of the “NC” version set QNX back considerably.
The open source community then dumped QNX. Support for
QNX in all the GNU software that QNX needs to run has
essentially stopped. And no, the “evaluation version” isn’t
the same thing, not with the self-destruct in “QCC”.
(Would someone please write a shell script to replace “QCC”?
It doesn’t really do anything substantive; it just rewrites
the options and calls GCC.)
QSSL needs to quit worrying about people “pirating” QNX,
and worry more about people ignoring it. Real-time Linux
isn’t a joke any more.
John Nagle
Team Overbot
QNX drivers for x86 have fallen so far
behind it’s hard to find x86 machines old enough to run QNX.
We need more people doing device drivers.
How many device drivers (networking, graphics or audio) have been done by
the community in the times of NC?
Malte
“Malte Mundt” <mmundt@qnx.de> wrote in message
news:df49o4$ojm$1@inn.qnx.com…
QNX drivers for x86 have fallen so far
behind it’s hard to find x86 machines old enough to run QNX.
We need more people doing device drivers.How many device drivers (networking, graphics or audio) have been done by
the community in the times of NC?
Very very little, from memory only one of each. Maybe two audios.
Malte