Check section 3 of the CCSv6_Getting_Started_Guide for install instructions.
Check if the target configuration file (.ccxml) accurately describes your JTAG debug probe (Connection) and target (Device or Board) and use the Test Connection button to determine whether your JTAG connection is working at the lowest level.
If you are using one of the newer boards that do not have the JTAG connector populated (Beagle Bone, AM3359 ICE, AM3358 SK, etc.), keep in mind they usually need additional hardware changes other than simply populating the JTAG header. If you are working with electronics that are near motors or other electrical components that could induce currents, then shielding and isolation may be important.
An example, instructions for the Beaglebone White can be found here. There are some older products which cannot handle newer targets with 1.8V I/O as they were designed to operate with 3.3V and 5V targets. This typically manifests itself as the connection to CCS becoming unstable or intermittent. The explanation is: An attempt to connect to the XDS110 failed.
An error occurred while soft opening the controller. The explanation is: The hardware or software support only limited values of port addresses.
-----[An error has occurred and this utility has aborted]-------------------- This error is generated by TI's USCIF driver or utilities. This error means the JTAG debugger is sending data to the device via the TDI pin but is not receiving anything back on the TDO pin.
-----[An error has occurred and this utility has aborted]-------------------- This error is generated by TI's USCIF driver or utilities. The cause may be one or more of: invalid XDS100 serial number, blank XDS100 EEPROM, missing FTDI drivers, faulty USB cable.
So, simply restoring the custom i OS 4.0 you i Phone/i Pod Touch will be jailbroken. So, only Mac users are able to create custom i OS 4 firmware using Pwnage Tool. and do not own a Mac or don’t want to go through the Pwnage Tool procedure?? Here you can download i OS 4.0 Custom firmware for i Phone 3GS, i Phone 3G and i Pod Touch 2G.If the ICEPick driver reports this error immediately upon connect, it's likely a hard fail with the JTAG connection itself (loose cables or connections, etc.).However, if the error happens later in the debug session the reasons are different (perhaps the reliability of the JTAG connection due to noise, etc.).Note: If using So C and multicore devices, it is always a good idea to manually launch the target configuration and connect to each core individually instead of clicking on the Debug Active Project button .For details please check item 8 of the next section Determine whether the debug probe is correctly setup in the Host by checking either the Windows System Devices control panel or using Linux command line tools (details here).TVRef should be connected to the IO voltage through a small current limiting resistor. See XDS Target Connection Guide for more information on the connection of these and other emulator signals.