AnsweredAssumed Answered

Code Warrior LPT1, and Connection Server problems (MC56F801x)

Question asked by Mark Wyman on Jul 12, 2007
Latest reply on Nov 27, 2009 by Qiu Zhaopeng
Ok, my computer did not have a parallel port, and I am a little upset that the low-cost JTAG solution requires that... I had to go purchase an expansion card that allowed me to use a PCI-x to PCI bridge, and then to two serial and one parallel ports. It appears at first glance to be an acceptable card, though I hope it is not the problem.

I have the MC56F8013 Demo board, and I am simply trying to run the example LED flasher.

The parallel port init utility claims it cannot find LPT1, and does not execute properly. I am assuming that I don't necessarily nead this to perform JTAG operations, it is just to get the printer port in the right mode and exits. This I blame on the expansion card drivers.

I open the example project, and click the debug button.
The CodeWarrior connection server loads fine, and points to LPT1 (in the console)  This is the content of the console window right now:

loading history file ... 0 events added
CodeWarrior Connection Server console display active (Tcl8.4.6 / Tk8.4.6)
Loading CCSAPI Tcl interface (C:/Program Files/Freescale/CodeWarrior/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
Server listening on port: 41475
Clients accepted from all hosts
Connection #1 accepted from localhost at Wed Jul 11 22:30:35 2007
Connection #1 from localhost closed at Wed Jul 11 22:30:35 2007
Connection #1 accepted from localhost at Wed Jul 11 22:31:33 2007
Connection #1 from localhost closed at Wed Jul 11 22:31:33 2007
Connection #1 accepted from localhost at Wed Jul 11 22:42:44 2007
Connection #1 from localhost closed at Wed Jul 11 22:42:44 2007
Connection #1 accepted from localhost at Wed Jul 11 22:48:33 2007
Connection #1 from localhost closed at Wed Jul 11 22:48:33 2007
(bin) 1 %

So it looks happy. However when I try to debug, I get an error message dialog:

CCSProtocolPlugin : CCS: Command Converter Not Present.

What do I do now? I can clearly see the connection accepted, then it immediatly closes again. It seems to be on the Metrowerks side.
I cannot get beyond this point.

Thanks for your help!

-Mark W.

Outcomes