Due to communication with the USB2ANY for firmware updates succeeding, it does not appear to me that this is a USB2ANY issue.įurther, I finally obtained a new laptop for which TI ALP has not yet been installed.
Uninstall TI Analog LaunchPad, then reinstall TI Analog LaunchPadĪt this point I have no further ideas for how to resolve this issue, and it appears to be persistent across reinstallations. 
Firmware downgraded and upgraded successfully, but ALP has same issue. Downgrade firmware of USB2ANY then reupdate firmware of USB2ANY. Firmware updated successfully, but ALP still has same issue. I have tried the following resolutions to no avail Thus I am stuck in a state where I cannot configure the USB2ANY to communicate with an EVM. For some reason, Tools > USB2ANY/Aardvark Setup tool does not open when clicked. However when Analog LaunchPad is opened, the USB2ANY does not appear in the device list.Īs you can see, the device list is empty, despite the hardware being connected. In the current state, the laptop is connected to the USB2ANY device via USB. I believe the issue lies with the Analog LaunchPad software or configuration. How can this issue be resolved, so I can use ALP on this computer? Registry - The "ConfigFlags" entry was 00000000Ģ.Other Parts Discussed in Thread: ALP,, DS90UB953-Q1EVM, MSP430F5529Īfter using the Analog LaunchPad software without issue for about 7 months with a DS90UB954Q1-EVM, it has now entered a state where it does not allow me to communicate with the USB2ANY or any evaluation module. 
I then selected a different drive to make sure the test drive was free.ĭevice manager - The USB stick appeared as a 'normal' device Registry entry - accessed by right-clicking on its InstanceID cell in the USBDeview results table & selecting Open in RegEditġ.1 I ran USBDeview to get the InstanceID, which was USB\VID_05DC&PID_A81D\AA5Y3C390RITMT0Nįile explorer - The drive was shown and I had access to it. Similarly, I closed all applications that might access it.ĭevice mgr - check it is shown I checked these before starting, after disabling & again after re-enabling the USB stick:įile explorer - check access to the drive then select a different drive to make sure the test drive was left free before issuing any commands that affected it. I just tried the NirSoft USBDeview tool and it worked.
0 kommentar(er)
