Driver for NI-VISA for ADS1274EVM

Hi Mike,

Your attachment did not post correctly - can you tell us what the Device Manager sees when you power up the ADS1274EVM-PDK and plug in the USB cable?

Since I posted the original message I have received a new PC.  The new PC uses Windows 7 64bit.  I have tried to load the software into the system.  The ADCPro package is available but the device manager sees my evm as an Unknown Device.  I have not had any luck getting a driver to load.  Can anyone point me to a Windows 7 device driver for the ADS1274EVM?  The EVM board has the markings:

6492534 PCA

6492531 BOM

and  Tool# 14106 NIX-6-0 5009

The Control motherboard has markings:

MMB0 Modular EVM Motherboard

6462011 BOM Rev    with an empty silkscreen box

6462012 PWB D

I am beginning to wonder whether ther is any code in the Motherboard.

Sincerely,

Mike Fontes

Mr Fontes -

Where did the software you loaded come from?  Is it from the TI site or was it included on a disk in the kit?  If it is software included on a provided disk, please download the latest software from the TI site since the software on the disk is an older version that does not support Win7.

Greg,

I started by loading the software from the cd from the EVM.  That was where my original question started.  After I got the ADCPro running, but not seeing the EVM, I downloaded the Version 1.01 diwnloader and let it get me the updates.  Howevere that updates ADCPro but didn't seem to get me a new working USB Device Driver, which is what I need forst to check on whether the new ADCPro finds the EVM.

Sincerely,

Mike Fontes

Mr Fontes -

OK...the driver should update as part of the software, so it may be relatively transparent to you during the installation process.

Is it the NI-VISA driver the isn't loading? You shouldn't need any software working to get this driver, just plug in the hardware to USB and connect power.  Then you see the NI-VISA in the Device Manager (as shown in user guide).

If you get this driver loaded, the other driver will not load until the software is started and the plug-in loads firmware before trying to use the new driver.  Hopefully, this is the point that is causing problems.
If this (second driver) is the problem point, try running the attached file and see if that helps.  If the first driver is the problem, let me know and we'll investigate further.

Greg,

The Device Manager does NOT see the NI-VISA device on the Windows 7 machine.  It sees a USB Device it defines as "Unknown Device". It does not know what driver to look for, and I don't know what driver to tell it to look for.  That is why I am suspicious about the Motherboard Programming.  I would expect that after enumeration that Windows would know more about the motherboard than it seems to based on the properties shown in Device Manager.

I need to know where I should run the setup utility you gave me.  I have tried running it in a couple of folders but it keeps failing with a message that it can't find the libusb.dll file.  I see several copies of the dll in different directories of the ADCPro directory tree in Program files, but setup is obviously not looking in those folders for the dll.

I appreciate your help and I am looking forward to getting a good connection soon.

Sincerely,

Mike Fontes

Mr Fontes -

So if the NI-VISA device isn't showing up, please ignore the file I sent.  This is for the second driver, which we can't get to without the first.

The MMB0 does not have any programming, the firmware is downloaded when the software is started.  However, the DSP should be recognized by default (NI-VISA) without running any software.

A couple more questions -

Is jumper J12 installed? This is located just below and between the USB connector and DC power jack.

Greg,

Could you please call me Mike?  Only my daughter's friends call me Mr. Fontes.

I checked, and J12 is installed on the board.

Just a reminder, I am running Windows 7 64 bit, just in case it matters to the system.  Is there a way to manually load the firmware onto the MMB0? It surprises me that the DSP isn't able to indicate that it is a NI-VISA device.

Sincerely,

Mike Fontes

Mike -

So let me back up a little.

The NI-VISA driver is recognized based on the PID&VID of the DSP; there is no firmware on the MMB0 as shipped or when not running ADCPro/other TI tools.  The NI-VISA driver recognizes the hardware settings of the DSP (based on the inf/driver files that get installed during installation).  So you should be able to just connect the MMB0, power, and have the PC recognize install/configure the NI-VISA driver and see it in the Device Manager (at least that is how it is supposed to work).  After this, when you start the software, firmware is downloaded to the DSP and then the DSP restarts with the new firmware.  This causes the PID & VID to change, causing the second driver (USBStyx) to be installed/configured...before the software and hardware ultimately "connect".

So it sounds like the second driver is of little concern, since we can't get the first to install.  Do you have anything else that uses NI-VISA or LabVIEW installed on the PC?  Although it may be time consuming, you might want to try removing all the software and re-installing (if you haven't already).  The update should have done this, but maybe something was missed.

Greg,

I have included a file with several screen captures showing what Device Manager reports for the device.  If there are other properties required let me know and I will get them.  At this point I am pretty sure indows does not know how to handle the device based on how the Device Manager is seeing it.  Please let me know what you want me to try.

Sincerely,

Mike Fontes

Mike -

How are you including the files?  They are not coming through in the post.  If you reply, up at the top, there is a "Options" tab beside the "Compose".  Use this tab to add files to the post (unless this is what you are doing).

Greg,

I am using the paper clip insert file in the toolbar.  Can I get a different method because the images in word files don't work with the "paste from word " option.  If not can I send you a direct email?  The window captures give the best information.

Sincerely,

Mike Fontes

Mike -

Can we contact you using the email you provided in your profile?

Greg,

That would be fine.  It should facilitate getting the screens to you.

Sincerely,

Mike Fontes

I am posting a status because I have still not been able to get the kit going.  I have now tried two of the kits, each having a different MMB0 design board, on three different computers, with the 64bit Windows 7, and 2 Windows XP Pro systems.  I have downloaded the latest ADCPro on each system and installed it.  I have downloaded the ADS1274 EVM Plugin on each machine.

I am still stuck with the problem that none of the machines recognizes the kit board as the NI-VISA devices as the documentation indicates.  All machines recognize and "Unknown Device", and will not allow me to load a new driver.  When I Browse to the USBStyx.inf file the device manager tells me the file does not match the hardware installed.

When I run the ADCPro program it sees a device connected, says the device is not programmed, tries to reprogram it and fails.  If I try to do anything with the ADCPro after that which attempts to communicate to the kit, I receive messageboxes telling me that there were timeout failures when talking to the kit device.

Has anyone had these problems and made it past them?  I am looking for some things to try because I am at a standstill and cannot perform any of the tests I need to get completed before I can prove the part will meet my requirements.

Sincerely,

Mike Fontes

I have been working with the Windows 7 64bit machine this morning trying to figure out where the install failures.  I have the system recognizing the MMB0 as a TI TMS320VC5509A Device, that will not use the ISBStyx.inf to load drivers.  I have started looking at property windows and inf file contents and I see something that doesn't look right to me.look right to me. The device IDs from the Device manager properties and the inf file don't match.  Does anyone know if this is right or not?

Mike -

The driver that you are trying to force in is not the correct driver, so therefore your observations regarding the PID/VID are accurate.  You need the inf files located @ C:\Program Files (x86)\ADCPro\pdk_lib\libmmb0\Styx\mmb0_drivers (or similar, depending on your computer and platform).  The "vista&7" file is for Win7, the other for WinXP.  Some additional software information for the installation process is available @ http://www.ti.com/lit/ug/slau372a/slau372a.pdf.

At this point, there may be some issues caused by all the installation and different versions, given that Windows doesn't always forget everything that it is supposed to when you "remove" a driver.  You will probably want to uninstall the the software and ensure all driver related files are removed.  This may be a little tedious, but I don't know of any other methods.  There will be the dll files, and inf files, both the ones shown and the ones that have been incorporated into the oem files.  Care should be taken when doing this to prevent deleting any system files that might cause other things to work.

Greg,

I have removed all the old drivers I could find.  I am still having a problem.  I think it is important to note that:

1. I was not able to receive the setup.exe that was sent to me because my email system wouldn't allow it.  Therefore I don't know what additional instructions came with the email that it was attached to.

2. I have looked at the directions that are in the slau372a.pdf file and there is a very important difference between what I am getting and what the directions show.  At NO TIME do I ever get an indication from Windows that the device is an NI-VISA device.  It is ALWAYS and UNKNOWN DEVICE.  Therefore Windows is not able to find a correct driver for the new device.

3.  Out of curiosity I have attempted to point the device manager driver installation to every .inf file in the ADCPro subdirectory structure that I could find.  It does not accept any of them as a match for the mmb0 board hardware.

I am convinced that the correct dlls are in the directories I have but that Windows does not want to install the correct one.  Can you tell me a way to get past this problem?

Sincerely,

Mike Fontes

Mike -

When the device shows up as "Unknown", can you tell us what the VID/PID is showing?  Should be VID = 0451, PID=9001.

Additionally, do you have anything else on your computer that uses LabVIEW or NI-VISA?  Just looking for possible contentions.

Is there a good email that we can send emails with attachments to?

Greg,

The VID and PID are correct as you showed them.  You can see that in my previous posts. There are no other NI- VISA or Labview apps on this machine.  It is fairly new, and only has minimum installed programs at this point. I also share some questions as when I look up the VID and PID the board is reporting on the web it shows me a TI NI_VISA device.  The trouble is that Windows doesn't think that.  How far back do you want me to uninstall.  I can remove ADCPro again.  I'm not sure what registry entries to remove if you want me to go there.

You can send item to the address mfontes@mtiinstruments.com. The only limitations are size < 10Meg and no exe or zips.  I have successfully gotten by some zips by renaming them .zonk files.

Sincerely,

Mike Fontes