I remember a problem with DSC V7.x but don't remember exactly the version (7.1, 7.1.1, ...).
I think it should be interresting to install the last version DSc v8.2.3.
Now it could have some problem with old USBTap.
See below some words about that.
==================================================================================================================================
CodeWarrior USBTAP Product Notification
An early revision of the CodeWarrior USBTAP has been sometime shown to be sensitive to Electrostatic Discharge (ESD) from human touch. Users should take care to ground themselves when handling the USBTAP unit.
This notification applies to following parts numbers and revisions:
CWH-UTP-STC-HX (900-20681)
CWH-UTP_PPPCD-HX (900-75094)
CWH-UTP-PPCC-HX (900-20659)
CWH-UTP-ONCE-HX (900-20681)
CWH-UTP-CF-HX (900-20682)
How to tell if your USBTAP is susceptible to ESD?
Look at bottom on UTAP case. The sticker on the bottom of the case will show 900-xxxxx. Check to see if this matches one of the numbers above.
How to tell if your USBTAP is affected:
If you suspect your USBTAP is no longer working due to ESD, try the following:
A. Setup was working fine and then stopped working.
Check to see if Windows can recognize your USBTAP:
- Plug your USBTAP into a USB Port of a computer running Windows XP
- Wait 30 seconds
- Does "Windows found new hardware dialog appear"? If yes, then your USBTAP has not been harmed by ESD
- Open windows "Device manager"
- Expand "System devices" category
- Does "CodeWarrior USBTAP" appear on the list? If yes, then your USBTAP has not been harmed by ESD
B. Having trouble during initial setup.
Update and reinstall the USBTAP driver
- Ensure you have the latest CodeWarrior release. Updated drivers may be included
- Drivers are found in the "CodeWarrior" program file directory under the ccs/drivers directory
- Reinstall with the directions are included in this directory
- Repeat step A.
If both A or B fail and the USBTAP is one of the 900-xxxxx series tap, you probably have experienced an ESD related failure and the unit needs to be replaced.
Returning you Unit:
If your unit has failed, please follow the RMA instructions at the following link:
===================================================================================================
and more ....
Did you tried with an example delivered on the installation ?
If you get the same problem with an example delivered on the installation, the problem should be:
- with the USBTap,
- or with the PC configuration,
- or with the board,
- or with the project config.
Check the USBTap.
When you plug it to the PC, the USBTap must be detected.
If this is not the case may be the interface is damaged.
When the interface is connected to the board and to the PC, the 2 light should be on. Is it the case ?
Check the board.
Check that the Jtag connection is selected. This is done by a jumper. This jumper define if the Jtag or the // connector is used. Is it working using a sample // cable as interface ? Do you have another board ?
Check the PC.
Can you install the tool on another PC ?
Check the project.
After to start the debug session, the ccs tool is automatically launched too.
Be sure that the right settings are selected in the target settings panels.
Open it and go to Debugger | Remote Debugging and select 56800 Local USBTAP connection.
Regards
Pascal