• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 45 subscribers
  • Views 733 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

ADS124S08EVM: Delta-sigma ADC EvaluaTIon software download link is broken

ADS124S08EVM: x386 64 bit version appear to be missing from the ..\Drivers\x386; usb_dev_bulk.inf cannot find them (neither can I)

Milan Trcka
Prodigy 30 points
Part Number: ADS124S08EVM

Hello,

Have two computers both running Windows 7 64-bit, one Pro, one Ultimate. One is a Dell Lattitude E6500 (Intel processor), the other is a Dell Lattitude D620 (Intel processor) ( I know, old dogs... but good)

Initial symptoms were: device ADS124S08EVM) not recognized; all controls greyed out. EVM has power and lights up. Several attempts using various combinations of running install with unit unplugged, plugged into USB, device specific files installed, uninstalled and both install sets uninstalled and reinstalled - no go.

All install attempts on two computers end with the following:

Snip from DSEvalSW-installLog.log>

[13:25:17] Running "C:\Program Files (x86)\Texas Instruments\DSEvalSW/Drivers/Installers/BulkUsb_driver_install_x64-v1.0.0.1.msi" ...
Installing USB drivers
Executing msiexec /qb /i "C:\Program Files (x86)\Texas Instruments\DSEvalSW/Drivers/Installers/BulkUsb_driver_install_x64-v1.0.0.1.msi" /l*v "C:\Program Files (x86)\Texas Instruments\DSEvalSW/Drivers/Installers/logfile.txt"
Script exit code: 1619

Script output:
T h i s i n s t a l l a t i o n p a c k a g e c o u l d n o t b e o p e n e d . V e r i f y t h a t t h e p a c k a g e e x i s t s a n d t h a t y o u c a n a c c e s s i t , o r c o n t a c t t h e a p p l i c a t i o n v e n d o r t o v e r i f y t h a t t h i s i s a v a l i d W i n d o w s I n s t a l l e r p a c k a g e .

Script stderr:

Program ended with an error exit code

USB Driver installer quit unexpectedly. This could be because the driver is already installed, hardware was connected during the installation, or other reasons. Manual driver installation may be required. See user guide for more details on verification and manual installation process.
[13:25:32] Error occurred during "C:\Program Files (x86)\Texas Instruments\DSEvalSW/Drivers/Installers/BulkUsb_driver_install_x64-v1.0.0.1.msi" installation.
[13:25:39] ---POST-INSTALLATION ACTIONS---
Creating Uninstaller
Creating uninstaller 25%
Creating uninstaller 50%
Creating uninstaller 75%
Creating uninstaller 100%
Installation completed
Log finished 06/15/2019 at 13:25:45
[13:27:16] ---FINAL PAGE ACTIONS---
Executing C:\Program Files (x86)\Texas Instruments\DSEvalSW\DSEvalSW.exe
Script exit code: 0

Script output:

Script stderr:

>SnipEnd

Following the instructions for manual installation:

Find offending driver in Device Manager - "unknown device"

Perform "update" - select "usb_dev_bulk.inf"

Error Message: The folder specified doesn't contain compatible driver for your device. If the folder contains a driver make sure it is designed to work with Windows for x64-based systems.

I tried to execute the install manually in CMD - same results.

Delved deeper into usb_dev_bulk.inf and find that listed lmusbdll64.dll and lmusbdll64.lib are MISSING from ..\Drivers\i386.    In the amd64 section drivers are present.  

Are the 64 bit drivers missing from the i386 ensemble??? Do they exist??? Can I have them? Please?

I would greatly appreciate help to get the eval kit going - my client is getting anxious to evaluate the ADC and use it in a project.

Thank you for your swift reply and help.

Registered TI user

Milan Trcka

milan.trcka@sparton.com

milan.v.trcka@gmail.com

  • 0
    TI__Guru** 112785 points

    Hi Milan,

    Welcome to the E2E forum!  The software installation requires administrator rights.  As a part of the installation the drivers will be placed into the windows driver store.  Copies are also made in Program Files (x86)\DSEvalSW\Drivers.  Under the Drivers folder are copies of the drivers and another folder called Installers which has the .msi installers if the drivers need to be reinstalled for some reason.

    As there are two programs that need to be installed, you should install the DSEvaluaTIon application first, followed by the ADS124S08EVM-DVCPKG.  Again, this installation requires administrator rights.  If the driver was installed properly you should see in Device Manager a Tivaware Bulk Device.

    Can you verify that the EVM is showing as TivaWare Bulk Devices or is it showing as unknown device when plugged in?

    Can you also verify which folders are missing from the drivers folder?

    Best regards,

    Bob B

  • 0 in reply to Bob Benjamin
    Prodigy 30 points

    Hi Bob B

     

    1)      EVM does not show in as TivaWare Bulk Devices. It shows as Unknown Device. Repeatedly. It will “ding when plugged and unplugged.

    2)      As I mentioned in the title and in the body of my message, the ...\Drivers\x386\USB_dev_bulk.inf is expecting the 64-bit versions of the DLL and LIB. At least this is what I surmise, not knowing any better. The 64-bit versions are not in the x386 but they are in the AMD section. Here is the relevant observation:

    Error Message: The folder specified doesn't contain compatible driver for your device. If the folder contains a driver make sure it is designed to work with Windows for x64-based systems.I tried to execute the install manually in CMD - same results.

    Delved deeper into usb_dev_bulk.inf and find that listed lmusbdll64.dll and lmusbdll64.lib are MISSING from ..\Drivers\i386.    In the amd64 section drivers are present.  Are the 64 bit drivers missing from the i386 ensemble?

    Thank you for your help.

    Milan

  • 0 in reply to Milan Trcka
    TI__Guru** 112785 points

    Hi Milan,

    Keep in mind I cannot see what you see.  I showed some screen shots in my previous post.  I understand you are saying you are missing the dll's in the i386 folder, but what about the rest of the folder contents as I showed above?  In particular you should see the msi installer packages in the installer folder in the directory path as shown in the screen shot.  Can you also attach the logfile.txt in your next post if this exists in that folder?

    I ran the installer myself (as did a colleague) to make sure the download takes place as expected.  And yes, you should see contents in the i386 folder similar to the amd64 folder.  

    In the DSEvalSW folder there should also be "DSEvalSW-installLog.log".  Can you send me that log file as well?  This will give us some information as to what is not unpacking properly in your system.

    Best regards,

    Bob B

  • 0 in reply to Bob Benjamin
    Prodigy 30 points

    Hello Bob,

    I solved my problem. My mistake was when I tried to manually install the drivers, I pointed the installer to ... \drivers\x386 (since I have an Intel machine) instead one level higher to ..\drivers\...

    Installer found what it needed and all is happy. I believe the drivers are actually AMD drivers for the 64-bit architecture.

    All I can say that there is some sort of disconnect in the install script as it exists. It would be helpful to add a note to point the "driver update" to ...\drivers to update the bulk device entry in device manager. If I missed this, I apologize for the commotion.

    Thanks for your help.

    Milan

  • 0 in reply to Milan Trcka
    TI__Guru** 112785 points

    Hi Milan,

    I'm glad to hear you got things working.  Unfortunately that doesn't explain why the files were not properly copied to the folder.  There are similar file names as content in both the amd and i386 folders.  The DLLs are actually different between the 2 folders.  It is possible to 'trick' the driver installation using the amd files as the actual bulk driver is the Microsoft WinUSB driver native to the operating system.  The only reason we would need the DLLs is if we need to reflash the firmware.

    So just so we are clear, the actual driver is the WinUSB driver, and the DLLs are support for other applications not a part of the Delta-Sigma EvaluaTIon platform.  As we use a standard signed driver set provided by the TI embedded processing group we provide these additional files as well.  The 'inf' file is looking for these files and if they are not found the installation fails.  So we are still not sure as to why the driver installer was not properly unpacking these files to the folder.

    Best regards,

    Bob B