VxWorks vs GPIB-1014

[Mike Wlodarczyk]

Hello,

The basic problem I'm having is that with VxWorks 5.4.2 + MVME2700 BSP + NI GPIB-1014 generic driver modified for VxWorks, the 2700 locks up solid when it tries to read data from a device on the GPIB bus.

This stuff works ok on an old Vxworks 5.3.1/MVME2700 kernel as well as a VxWorks 5.5.1/MVME5500 kernel, both of which use the same driver code.

The GPIB board configures and otherwise appears to send data and do polls without any problems, so why it fails with the 5.4.2/2700 setup is rather perplexing. Using a JTAG BDM pod, the CPU is either tightly looping between the interrupt vector table and somewhere else I wouldn't expect or it is not responsive to the BDM pod control at all.

The system appears to handle the VME interrupts from the GPIB board properly, so I'm not sure what to make of what the BDM pod shows anyway.

Any suggestions ?

Thanks.

[MichaelChaney]

Hi Mike,

I'm not sure what is different about the 5.4.2 kernel that causes your driver not to work. The GPIB-1014 is not supported on VxWorks by our NI-488.2 driver and since you noted your driver version as being 1.0, it sounds like this driver was written using our ESP-488 development package. Here's a link to the manual for the ESP-488:

http://digital.ni.com/manuals.nsf/websearch/B51B124AF86E75F38625665E006358ED?OpenDocument&node=132100_US

Because of the nature of the ESP-488, our support is limited to specific questions about using the ESP-488 software. Unfortunately, we are unable to debug code or support the actual drivers created using the ESP-488 software.  Hopefully someone who has developed a driver for the 5.4.2 kernel will reply with some insight into this issue.