pxi-6259 addressing problems using PXI-8360 and QNX

[Leafman]

I am trying to upgrade an existing test system that uses the PXI-6259 mulfunction DAQ and PXI-6602 using a PXI-8360 bridge to an x86 target machine operating under QNX 641.  Previously, I had an PXI8331 (now obsolete) working with this configuration.  On boot up the QNX system advises that the PXI2::14:: cannot be attached.  This is the 6259 device in slot 2 of the PXI rack.  The 6602 device appears to be recognised.   I currently also sucessfully operate the PCI-6259 under an x86 target with QNX 641.  I have checked that the driver and configuration settings are identical for both systems.

Created threads OK
24/05/2016 16:06:54.155661964 ISR registered.
pci_attach_device: No such device
24/05/2016 16:06:54.155661964 Could not find PXI6259 at address 'PXI2::14::INS
TR'
24/05/2016 16:06:54.155661964 Failed to initialise DAQ cards
24/05/2016 16:06:54.156661811 Error 3: No such process
osiUserCode::acquireBoardStarting

Can anyone shed any light on why the 6259 is not recognised?

Thanks in advance

[Eirikur]

This does look like it could be an BIOS limitation, a low maximum limit on the bus number range set by the BIOS, which limits the amount of hardware that can be attached to the system.

This documetnt covers this in some detail and you can find tools to check your system's compatability. That being said, the tools are Windows executables, so these might not work on your QNX

Determining the Number and Range of PCI/PCI Express Root Bus Devices 

You might find it interresting to read these documents as well:

Tips to Help You Successfully Use NI MXI-Express Controllers

MXI-Express Setup and Compatibility Guide

Supported MXI-Express Products for the MXI-Express BIOS Compatibility Software

Hope this sheds some light on this for your.

[Eirikur]

Any update on this from your end?

[Leafman]

Eirikur

Many thanks for your suggestions.  I plan to try these out in the next few days.

I will get back to you with my findings.

[Leafman · Accepted solution]

Thanks for the response on this.  I have resolved it in the driver code.  The code was "hard wired to a bus/slot" and in upgrading to a new machine the code was simply looking in the wrong place!

Thanks for your support!