Problem with Debug in CW for DSC56800/E v.8.0

[Andik]

Hello,
I'm using a free version of CW for DSC56800/E v.8.0, and I would like to solve my problem which occurs when I try to "Debug" any of CodeWarrior_Examples. I allways get a message:

"CSSProtocolPlugin: CSS: Command Converter not present."

I had some problems with CW for HC12 in the past, and it disapeared after instalation of new license file (obtained from Metrowerks). Is this the same case?

Any suggestion?


SW: CW for DSC56800/E v.8.0
Target: MC56F8013
Installed plugins: see attached .zip

[BlackNight]

It seems to me that the ccs.exe is not running on your machine. Typically, the installer sets it up so it is launched automatically. You should check if you have a ccc.exe task running on your machine (e.g. consult your windows task mananger).
You can launch it by hand too, it is lockated inside your installation of Hawk 8.0, probably for you at this location:
C:\Program Files\Freescale\Hawk 8.0\ccs\bin\ccs.exe

Launch the .exe and check if the problem goes away.

Additional considerations:
If you have any special firewall software (e.g. ZoneAlarm) installed, you may check the settings, as the debugger and the ccs.exe are communicating through TCP/IP (local on your machine).

Hope this helps,
Erich

[Andik]

Hello Erich,
thank you for quick answer, it looks like "yes, that should be the reason of my troubles" but I tried both and the problem remains.

I have the ccs.exe started. Also my ZoneAlarm is configured to trust the CodeWarrior Connection Server (ccs.exe). For certainty, I shut down the Firewall, CCS, restarted the CCS and CW, but still the same problem.

Here is the CCS log.

CodeWarrior Connection Server console display active (Tcl8.4.6 / Tk8.4.6)
Loading CCSAPI Tcl interface (C:/Program Files/Metrowerks/CodeWarrior CW56_V8.0/ccs/bin/ccstcl.dll)...
Initializing arm namespace...
Initializing rnbo_sync namespace...
Initializing rnbo_mcore namespace...
Initializing rnbo_sc140 namespace...
Initializing rnbo_ipcm namespace...
Initializing sc140 namespace...
Initializing zassc namespace...
Initializing hawkv2 namespace...
Initializing dsp563 namespace...
Initializing dsp566 namespace...
Initializing dsp568 namespace...
Initializing msc8102_sync namespace...
Initializing msc8102_sc140 namespace...
Initializing ms116 namespace...
Initializing odyssey_sync namespace...
Initializing odyssey_ms1162 namespace...
Initializing mpc5500_sync namespace...
Initializing mpc5500_zen namespace...
Initializing mpc5500_npc namespace...
Initializing mpc5500_ndedi namespace...
Initializing mpc5500_nxdm namespace...
Initializing mpc5500_etpu namespace...
Initializing sjc namespace...
Initializing mpc603e namespace... Loading tppc.tcl...Done

Initializing mpc603ei namespace... Loading tppc.tcl...Done

Initializing e500 namespace... Loading te500.tcl...Done

Initializing mpc7410 namespace... Loading tmpc7410.tcl...Done

Initializing mpc74x7 namespace... Loading tmpc74x7.tcl...Done

Initializing mpc7447a namespace... Loading tmpc7447a.tcl...Done

Initializing j2i2c namespace...
Initializing mpc83xx namespace... Loading t83xx.tcl...Done

Initializing mpc755 namespace... Loading tmpc755.tcl...Done

Initializing arm11 namespace... Loading tarm11.tcl...Done

Initializing mpc7448 namespace... Loading tmpc7448.tcl...Done

Initializing coldfire namespace...
Initializing mpc8641 namespace... Loading tmpc8641.tcl...Done

Executing autoexec.tcl...
0: Parallel Port(SPP) (lpt:1) CC software ver. {3.3}
Server listening on port: 41475
Clients accepted from all hosts
Connection #1 accepted from localhost at Tue Apr 03 09:53:34 2007
Connection #1 from localhost closed at Tue Apr 03 09:53:34 2007
(bin) 1 %


Now I'm wondering, if it is possible to run the example code in simulation-like mode (without hardware connected). I just want to try, how the DSC56 core works to get a practice with ASM. The project target is set to "smm internal memory with pROM-to-xRAM copy"

[BlackNight]

Hello Andik,
yes, you can use the simulator. The easiest way is if you simply create a working base and go from there. You can do this with File > New, DSP56800x New Project Wizard > Simulators and go through the rest of the steps. You will see that this sets up a connection to the simulator (ALT-F7, or project preferences -> Debugger > Remote Debugging).

The setup and capabilities of the simulator vs hardware are a little bit different, but above sample should give you a good starting point.

As for your original problem (still existing): you may check the CCS console output. And check (of course) if your run control/connection to the hardware is working fine?

Erich