Driver Development Kit (DDK)

cancel
Showing results for 
Search instead for 
Did you mean: 

Problems with Tru64 UNIX 5.1b PCI-GPIB driver development

I am using your NI488.DDK product to develop a PCI-GPIB device driver for Tru64 UNIX 5.1b3. I have experience porting other device driver from 4.x to 5.1b and thought that this would not be too hard.  The driver that I have developed loads and configures ok.  It allows for the IBFIND of /dev/gpib0 minor #255 to work fine because a bus table is built for it during the probe/attach. When I try an IBFIND on /dev/gpib_dev/dev1 I get an error from ni_Cp2BusPtr for minor #51 because no table is created for the devx devices during driver initialization. I don't see where this was done in the example ib.c code provided for Tru64 Unix 4.x,  am I missing something?

 

0 Kudos
Message 1 of 2
(6,503 Views)

This is really an update to my original posting for those of you who may have similar concerns.

The source code provided as part of the NI488DDK kit is not really a fully functional driver with the same capabilities as they provided in the device driver that they devloped for Tru64 UNIX 3.x and 4.x.  The the "ib" commands supported by the DDK driver is a subset of the entire ni488 suite.  None of the device specific "ib" command are supported, neither is ibask.  Device commands are written to the bus as character strings that contain device addresses and command.

0 Kudos
Message 2 of 2
(6,477 Views)