Active
The QNX Neutrino RTOS is a POSIX compatible, robust real-time operating system, which meets the constrained resource requirements of real-time embedded systems. It has a structure similar to UNIX and has been ported to a number of platforms including PowerPC, x86-compatible, MIPS, SH-4, ARM, StrongARM and XScale CPUs.
The driver offers access to the Hilscher netX based hardware (e.g. CIFX / COMX / netPLC / netJACK) with the same functional API as the CIFX device driver for Windows and offers transparent access to the different devices. The driver is provided in source code and can be linked statically or dynamically to a user application.
| Product details | NXDRV-QNX |
|---|---|
| Associated products | CIFX / COMX / netPLC / netJACK |
| Network controllers | netX 500, netX 100, netX 50, netX 10, netX 51, netX 52 |
| Operating systems | QNX Neutrino RTOS V6.4.0 and higher |
| Driver type | 32-bit library |
| API | Shared / static library
Opening and closing the driver Initializing the PC cards Accessing process data image Writing/reading commands Writing parameters Reading status information Watchdog function |
| Operating modes | Polling / Interrupt / DMA |
| Hardware support | DPM, ISA, PCI / PCIe |
| Cards per system | Any number |
| Other characteristics | Support for development boards
No simultaneous access to one card from multiple applications |
| Product name | Part number | Brief description |
|---|---|---|
| NXDRV-QNX | 6211.060 | CIFX/netX Device Driver for QNX |
Most operating systems require a device driver to integrate hardware components. Hilscher CIFX/COMX components require such device drivers as well. Hilscher offers a series of device drivers for a wide variety of operating systems. All Hilscher drivers have a standard user interface (CIFX-API) and are based on a C toolkit also usable for independent device driver development. The drivers are fully responsible for managing the communication components, including loading firmware and configuration files. The user interface contains all of the functions needed to initialize, parametrize, exchange I/0 data and acquire status information. Depending on the operating system, the user interface is contained in a DLL or library. As far as possible, the drivers support existing bus connections such as ISA, PCI, PCIe and dual-port memory connections. The C toolkit, and therefore the basis of the driver code, is designed in such a way that an unlimited number of communication components can be used simultaneously. However, the specific characteristics of each operating system must be taken into account.
