Other Parts Discussed in Thread: UNIFLASH
Hello,
I have got a new cc3220 launchxl and I am following the getting started guide.
I first installed the SDK, then the XDS 110 drivers (from here http://processors.wiki.ti.com/index.php/XDS_Emulation_Software_Package)and then uniflash v4.2.1. when I plugged in the device, and started Uniflash, I couldn't connect to it because auto detect failed. I checked the device manager, and the XDS110 device was in "Other" device not under "Ports". The installation logs of XDS 110 emulation package has following errors:
Executing C:\ti\ccsv7/temp/vcredist15_x86.exe /q /nostart Script exit code: 1638 Script output: Script stderr: Program ended with an error exit code Error running C:\ti\ccsv7/temp/vcredist15_x86.exe /q /nostart: Program ended with an error exit code ... [18:57:06] Running XDS100 Driver Installer Executing C:\ti\ccsv7/ccs_base/emulation/windows/DPInst64.exe /SE /SW /SA /PATH "C:\ti\ccsv7/ccs_base/emulation/windows/xds100_drivers" Script exit code: 512 Script output: Script stderr: Program ended with an error exit code Error running C:\ti\ccsv7/ccs_base/emulation/windows/DPInst64.exe /SE /SW /SA /PATH "C:\ti\ccsv7/ccs_base/emulation/windows/xds100_drivers": Program ended with an error exit code [18:57:07] Running XDS560 Driver Installer Executing C:\ti\ccsv7/ccs_base/emulation/windows/DPInst64.exe /SE /SW /SA /PATH "C:\ti\ccsv7/ccs_base/emulation/windows/xds560_drivers" Script exit code: 256 Script output: Script stderr: Program ended with an error exit code Error running C:\ti\ccsv7/ccs_base/emulation/windows/DPInst64.exe /SE /SW /SA /PATH "C:\ti\ccsv7/ccs_base/emulation/windows/xds560_drivers": Program ended with an error exit code [18:57:08] Running XDS2xx Driver Installer Executing C:\ti\ccsv7/ccs_base/emulation/windows/DPInst64.exe /SE /SW /SA /PATH "C:\ti\ccsv7/ccs_base/emulation/windows/xds2xx_drivers" Script exit code: 256 Script output: Script stderr: Program ended with an error exit code Error running C:\ti\ccsv7/ccs_base/emulation/windows/DPInst64.exe /SE /SW /SA /PATH "C:\ti\ccsv7/ccs_base/emulation/windows/xds2xx_drivers": Program ended with an error exit code [18:57:09] Running XDS110 Driver Installer Executing C:\ti\ccsv7/ccs_base/emulation/windows/DPInst64.exe /SE /SW /SA /PATH "C:\ti\ccsv7/ccs_base/emulation/windows/xds110_drivers" Script exit code: 512 Script output: Script stderr: Program ended with an error exit code Error running C:\ti\ccsv7/ccs_base/emulation/windows/DPInst64.exe /SE /SW /SA /PATH "C:\ti\ccsv7/ccs_base/emulation/windows/xds110_drivers": Program ended with an error exit code ... Executing C:\ti\ccsv7/ccs_base/emulation/windows/DPInst64.exe /lm /sw /path "C:\ti\ccsv7/ccs_base/emulation/drivers/stellaris/icdi/" Script exit code: 768 Script output: Script stderr: Program ended with an error exit code Error running C:\ti\ccsv7/ccs_base/emulation/windows/DPInst64.exe /lm /sw /path "C:\ti\ccsv7/ccs_base/emulation/drivers/stellaris/icdi/": Program ended with an error exit code Executing C:\ti\ccsv7/ccs_base/emulation/windows/DPInst64.exe /lm /sw /path "C:\ti\ccsv7/ccs_base/emulation/drivers/stellaris/ftdi_208/" Script exit code: 512 Script output: Script stderr: Program ended with an error exit code Error running C:\ti\ccsv7/ccs_base/emulation/windows/DPInst64.exe /lm /sw /path "C:\ti\ccsv7/ccs_base/emulation/drivers/stellaris/ftdi_208/": Program ended with an error exit code ... Executing C:\ti\ccsv7/ccs_base/emulation/windows/DPInst64.exe /sw /sa /path "C:\ti\ccsv7/ccs_base/emulation/drivers/cc3200/ftdi" Script exit code: 512 Script output: Script stderr: Program ended with an error exit code Error running C:\ti\ccsv7/ccs_base/emulation/windows/DPInst64.exe /sw /sa /path "C:\ti\ccsv7/ccs_base/emulation/drivers/cc3200/ftdi": Program ended with an error exit code ....
Here, TI's emulation pack installer is really disappointing. If there is an error while installation atleast let the user know, and I would first check the installation logs. It took me two days to realize where the error is coming from. I manually browsed to C:\ti\ccs_base\emulation\windows\xds110_drivers and manually updated the drivers from device manager. Now I can connect to the device in uniflash but service pack button is disabled.
Assuming CCS studio will at least be able to connect and debug, I have got CCS v7.4 installed. After starting CCS I get message for available updates, so I updated XDS emulation pack to version 7.0.100.1 from its updates dialog. When I start to debug, it asks to update the debug probe firmware to same version and I press continue:
Warning: A firmware update is required for the debug probe. Click the "Update" button to update the firmware and connect to the debug target. DO NOT UNPLUG THE DEBUG PROBE DURING THE UPDATE. (Emulation package 7.0.100.1)
In notification bar, driver software started to update but it failed because no drivers were found for some Tiva Device Driver Updater (I don't have its screenshot).
Now, I tried to use xdsdfu.exe as shown in the error in CCS. xdsdfu -m runs successfully:
USB Device Firmware Upgrade Utility Copyright (c) 2008-2015 Texas Instruments Incorporated. All rights reserved. Scanning USB buses for supported XDS110 devices... <<<< Device 0 >>>> VID: 0x0451 PID: 0xbef3 Device Name: XDS110 Embed with CMSIS-DAP Version: 2.3.0.7 Manufacturer: Texas Instruments Serial Num: E0071009 Mode: Runtime Switching device into DFU mode.
But when I hit xdsdfu -f firmware.bin -r, it shows:
USB Device Firmware Upgrade Utility Copyright (c) 2008-2015 Texas Instruments Incorporated. All rights reserved. Scanning USB buses for supported XDS110 devices... The requested device was not found on the bus.
Lastly I tried to install the XDS drivers again in CCSv7 path separately. This time I installed it into c:/ti/ccsv7/. Now its installation completes successfully(again it doesn't show any problems), but its installation log has the same errors as above.
If I try to debug in CCS it shows this error:
IcePick_C: Error connecting to the target: (Error -260 @ 0x0) An attempt to connect to the XDS110 failed. The cause may be one or more of: no XDS110 is connected, invalid firmware update, invalid XDS110 serial number, or faulty USB cable. The firmware and serial number may be updated using the xdsdfu utility found in the .../ccs_base/common/uscif/xds110 directory of your installation. View the ReadMe.txt file there for instructions. (Emulation package 7.0.100.1)
Now I cannot run anything on this device, so please help.
