The CIFX toolkit consists of C-source and header files allowing abstract access to the dual-port memory (DPM) defined by Hilscher and offered by CIFX, COMX and netX. devices. It contains all of the user interface functions as well as the generic access functions needed to use the Hilscher DPM.
|Associated products||CIFX / COMX / netPLC / netJACK|
|Network controllers||netX 500, netX 100, netX 50, netX 10, netX 51, netX 52|
|Functions||Defining the CIFX-API interface
Downloading firmware and configuration files during startup
Initializing PC cards
Recognizing flash-based and non-flash-based netX devices
|Operating modes||Polling / Interrupt via generic ISR and DSR functions|
|Hardware support||Dual-port memory connection|
|Other characteristics||Operating-system-specific hardware functions (such as PCI functions) not included
Support for development boards (NXSB-PCA/NX-PCA-PCI) without interrupt
|Product name||Part number||Brief description|
|NXDRV-TKIT||6211.000||CIFX/netX device driver C toolkit source code|
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.