ADS7142-Q1: BOOSTXL-ADS7142-Q1 GUI software Initial Setup issue

Hi Jimmy,

Sorry to hear that you are having PAMB issues!  Did you find this FAQ page:

https://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/914940/faq-how-do-i-resolve-pamb-evm-connectivity-and-or-driver-installation-issues/3380582

Did that resolve your problem?

Hi Tom,

The PAMB board USB driver is not an issue, as shown in the screen shot 2 of the attached file

The issue is the popped out "Firmware Update" window. I could not bypass it but I have to click "LOAD FIRMWARE" button at the time of launching BOOSTXL-ADS7142-Q1 TI website application. Actually when I press   button on the low left corner, the PAMB board is connected to PC, as shown on the top left corner of red circled area, as shown in screen shot 1 of the attached file. How to bypass "Firmware Update..." window and directly go the application GUI? Please advise

Thanks,

Jimmy

TICloudScreenShot1.docx

Hi Jimmy,

Let me get with our SW guys and see if I can find a reason why the firmware didn't update.

Thanks, Tom, for the follow up.

Is there a standalone SW version which could be downloaded so the "Firmware Update.." step could be skipped?

Jimmy

Hi Jimmy,

We think it might be related to the USB Device Firmware Update (DFU) driver.  That may need to be updated before the 'Firmware Update' works properly.  Can you try the link I provided yesterday and update the bootloader code?

Hi Tom -- I tried to update the PAMB USB driver. However I could not find it in the location as shown in below

Could you send me a link of PAMB USB driver location so I can download it in my computer and then to point it for the installation of the driver?

My computer OS is Window 10 Enterprise version.

Thanks,

Jimmy

Hi Jimmy,

The link is the one provided in the FAQ: http://www.ti.com/lit/zip/sbac253 

Can you grab a screen shot of your ...Drivers>PAMB directory and show me the contents?  Mine looks like this, yours will be a little different:

Hi Tom -- I downloaded the PAMB driver. Following is the screen shot on my computer:

Please let me know what I should do next, or send me a list of instruction to install the driver.

Thanks,

Jimmy 

Hi Tom -- I ran the "run_pnputil.bat" file in Command window, but it is failed, as shown in following screen shot:

Please advise what I should do from here.

Thanks,

Jimmy

Hi Jimmy,

I'm a little more familiar with the GUI, so I will be taking over for Tom.  I'm sorry you are having issues.  The GUI requires a firmware update so that the communication and control of the EVM will work correctly.  What we suspect is happening is the device firmware update driver (DFU) was not installed correctly via the cloud and this is creating a timeout condition where the firmware download does not take place.

Based on the screen shot of the folder contents, it would appear that the installation of the executable did not install correctly.  This may mean that you do not have administrator rights for installing the driver files.  After running the executable you should see something very similar to what Tom shows for the driver folder contents.  This could also be the issue with the cloud driver install.  Drivers for the communication are native drivers for MS Windows, so they will install automatically.  The DFU driver is not native and must be installed correctly for the firmware download to complete correctly.

So if you can ensure that you have admin rights, try the exe installation again.  Or you could try installing the PAMB_USB_Driver_Install_x64-v1.0.0.msi driver installer package as shown in the folder.  Once the drivers information files are installed, the correct driver for the DFU driver is boot_usb.inf.

At this point you could try the GUI again to see if the firmware download works correctly.  If it does not, then the driver is not associated correctly with the USB enumeration.  If the download is still not working the next steps will depend on whether the device shows as an 'Unknown Device' or as something else.  As the DFU mode timing is very short, it may be difficult to tell how the device is being identified.  In this case you will need to go to Device Manager and under the View drop-down menu select 'Show Hidden Devices'.  Take a screen shot and post it so I can help identify what should be done next.  Hopefully these latter steps will be unnecessary.

Best regards,

Bob B

Hi Bob -- Thanks for your stepping in to help

It is still failed in "Firmware Update..." process. Following is the screen shot under Window Device Manager about the driver (Generic Bulk Device)

Following is the screen shot shows the Details of Generic Bulk Device:

I noticed that there is no *.inf in the directory:

At the time of updating the driver or reinstall the driver, it would be failed if no correct *.inf in the fold. How do you think?

Jimmy

Hi Jimmy,

The PAMB actually uses 3 drivers.  One is CDC which is a virtual COM port, the second is Bulk and the third is DFU.  Nothing is showing as I would expect.  I'm quite sure that you either do not have administrator rights or your IT department (anti-virus software) is blocking the installation. 

Malicious software often attempts to reside under the program files directories.  Software is often blocked or limited to write to these locations without special permissions.  Perhaps you can get someone from your IT department to help you with the driver installer.

Best regards,

Bob B

Hi Bob -- I do have administration privilege right to install any software as long as I enter my company credential information for unknow software installation in the pop out window as screen shot below: 

Do you think the Driver SW package Tom provided to me yesterday is a completed driver package?

Thanks,

Jimmy

Hi Jimmy,

Yes, the installer is the complete package.  I downloaded from the same link and installed it myself to verify.  Did you try the .msi installer that is showing up within the folder?

Best regards,

Bob B

Hi Bob -- I do tried the .msi installer by clicking the .msi file

Do you think there is some other method for the installation?

Do you think we could have a web meeting (i.e. MS TEAM meeting) so you could guide me for the installation?

Thanks,

Jimmy

I reinstalled .msi file again just minutes ago, as screen shot below:

The result is the same as before, failed.

Regards,

Jimmy

Hi Jimmy,

When you say it failed, are you saying that the .inf files are not in the folder?  Before we attempt a call, can you post any log information you have from the install for me to review?  There actually should be 2 log files:

• install_log.txt
• pamb_x64_driver_install.log

Please post what you have available.  And one other thing, could you do a file search on your hard drive for boot_usb.inf?  That would be in case the file is copied to someplace we don't expect.

Thanks,

Bob B

Hi Bob,

Here is the install_log.txt file. I could not locate the pamb_x64_driver_install.log ifle in the directory of "C:\Program Files (x86)\Texas Instruments\Drivers\PAMB"

Log started 04/17/2023 at 20:26:03
Preferred installation mode : win32
Trying to init installer in mode win32
Mode win32 successfully initialized
[20:26:07] ---INITIALIZATION ACTIONS---
[20:26:07] Logging system information to installation log file  to assist with troubleshooting installation issues. 
If you encounter an issue during installation, please email this log file with a discription of the problem to pa_deltasigma_apps@ti.com.
[20:26:07] Operating System: Windows 10 Professional Service Pack 0 (Version #: 10.0)
[20:26:07] OS is 64-bits
[20:26:07] System Locale: en
[20:26:07] Detected an active Windows antivirus program...
[20:26:07] Detected an active firewall program...
[20:26:07] UAC Enabled: 1
[20:26:07] Installer is running as administrator: 1
[20:26:07] The installation directory is located at:
C:\Program Files (x86)\Texas Instruments\Drivers\PAMB

[20:26:07] The temporary installation directory is located at:
C:\Users\jxu189\AppData\Local\Temp\2\PAMB

[20:26:07] Software version to be installed: 1.0.1
[20:26:07] Free disk space = 138239900 KB (37721 KB required).
[20:26:07] ---PRE-INSTALLATION ACTIONS---
Preparing to Install
[20:26:19] ---READY TO INSTALL ACTIONS---
Preparing to Install
Creating directory C:\Users\jxu189\AppData\Local\Temp\2\PAMB
Unpacking files
Unpacking C:\Users\jxu189\AppData\Local\Temp\2\PAMB\PAMB_USB_Driver_Install_x64-v1.0.0.msi
Unpacking C:\Users\jxu189\AppData\Local\Temp\2\PAMB\PAMB_USB_Driver_Install_x86-v1.0.0.msi
Creating directory C:\Program Files (x86)\Texas Instruments
Creating directory C:\Program Files (x86)\Texas Instruments\Drivers
Creating directory C:\Program Files (x86)\Texas Instruments\Drivers\PAMB
Creating directory C:\Program Files (x86)\Texas Instruments\Drivers\PAMB\license
Unpacking files
Unpacking C:\Program Files (x86)\Texas Instruments\Drivers\PAMB\license\PAMB-USB-DRIVERS_1.0.0_manifest.html
Unpacking C:\Program Files (x86)\Texas Instruments\Drivers\PAMB\license\TI Internal Use License Agreement.pdf
Unpacking C:\Program Files (x86)\Texas Instruments\Drivers\PAMB\run_pnputil.bat
Unpacking C:\Program Files (x86)\Texas Instruments\Drivers\PAMB\PAMB_USB_Driver_Install_x64-v1.0.0.msi
Unpacking C:\Program Files (x86)\Texas Instruments\Drivers\PAMB\PAMB_USB_Driver_Install_x86-v1.0.0.msi
[20:26:20] ---POST-INSTALLATION ACTIONS---
Executing msiexec /i "C:\Users\jxu189\AppData\Local\Temp\2\PAMB\PAMB_USB_Driver_Install_x64-v1.0.0.msi" TARGETDIR="C:\Program Files (x86)\Texas Instruments\Drivers\PAMB" /norestart /qn /log "C:\Program Files (x86)\Texas Instruments\Drivers\PAMB\pamb_x64_driver_install.log"
Script exit code: 0

Script output:
 

Script stderr:
 

Creating Uninstaller
Creating uninstaller 25%
Creating uninstaller 50%
Creating uninstaller 75%
Creating uninstaller 100%
Installation completed
Log finished 04/17/2023 at 20:26:24
[20:26:26] ---FINAL PAGE ACTIONS---

The boost_usb.inf is now in the same directory as shown in the following screen shot:

Thanks,

Jimmy

Hi Jimmy,

Where were the files hiding?  I think overall what appears to have happened is the main executable ran, but inside the installer the msi installer was called and I think your anti-virus didn't allow the execution of the msi installer that actually contains all of the inf files.  In other words an executable within an executable was not allowed.

We are almost there.  Now let's go back to the Device Manager and make sure that you Show Hidden Devices from the View drop-down.  I need to see the whole window so I can determine what needs the driver update.

Best regards,

Bob B

Hi Bob , Following is the screen shot under Device Manager 

I don't know if those three unknown USB devices are the three drivers you talked before. If yes, I can manually install/update those three drivers. But I don't know what is the relations with CDC, Bulk, and DFU device for those three unknow device.

Thanks,

Jimmy

Hi Jimmy,

The CSC and Bulk connect automatically.  They will show up as a composite device and also as a COM port and Generic Bulk device.  This appears to already be working.  It is the DFU driver that is causing the issues.  The DFU device will normally show up as a Tivaware Device Firmware Upgrade.  It may or may not be showing as an unknown device.  That is why I asked for the entire window contents and not just a portion.  It would also be helpful to know where you found the files?  Can you provide me with this complete info?  The unknown devices you show appear to be error information as opposed to an unrecognized device.

You could also try a different USB port to see if the board will enumerate properly as the driver files appear to be installed.  Also, when attempting to flash the firmware, you should be able to see what changes in the Device Manager when the PAMB is placed into DFU mode.

Best regards,

Bob B

 ComputerDeviceManagerScreenShot.docx

Hi Bob -- Please find a complete computer Device Manager screen shot file as attached.

I do switch to another USB port. At the first time, the PAMB is connected to PC and "Firmware Update..." is bypassed/successful. However, once I unplug the USB cable and then plug it back to the computer, everything is the same as before, could not pass the "Firmware Update.." process, and "Firmware Update.." is failed.

To save the time for this issue trouble shooting, could we connect it through MS TEAM meeting so I can share my screen and you can guide me to resolve this issue?

Thanks for your time and help.

Jimmy

Hi Jimmy,

I see now where the driver needs to be be associated under Tiva Device Firmware Update.  I will contact you via email at the email address you provided when you signed up for your MyTI account.

Best regards,

Bob B