Problem with Codewarrior USB TAP

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Problem with Codewarrior USB TAP

4,248 Views
Etxeondo
Contributor I

  Hi

   I have buy a new 56F8037 demo board, I have installed CW R8.0, when a I connect the USB TAP the System operation install it correctly, after the install a can see:

  - Control Panel \ System \ Hardware \ Management Devices \ Device of system \ Codewarrior USB TAP

  Light TX/RX is in green and blinking the light RUN/PAuse is off.

   I inicialize a new project wizard with Processor expert.The program compiles, links and when it is going to communicate with the DSP56F8037 it gives an error me:

                                        CCSPrtocolPlugin: CCS Disconnected Cable

 In Codewarrior Connection server, I have the following messages:

CodeWarrior Connection Server console display active (Tcl8.4.6 / Tk8.4.6)
Loading CCSAPI Tcl interface (C:/Archivos de programa/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 LAB-W2000-2 at Sat May 05 07:27:47 2007
Connection #1 from LAB-W2000-2 closed at Sat May 05 07:27:54 2007
Connection #1 accepted from LAB-W2000-2 at Sat May 05 07:34:56 2007
Connection #1 from LAB-W2000-2 closed at Sat May 05 07:35:03 2007
Connection #1 accepted from LAB-W2000-2 at Sat May 05 07:35:39 2007
Connection #1 from LAB-W2000-2 closed at Sat May 05 07:35:46 2007
Connection #1 accepted from LAB-W2000-2 at Sat May 05 08:14:23 2007
Connection #1 from LAB-W2000-2 closed at Sat May 05 08:14:30 2007
Connection #1 accepted from LAB-W2000-2 at Sat May 05 08:19:46 2007
Connection #1 from LAB-W2000-2 closed at Sat May 05 08:19:54 2007
Connection #1 accepted from LAB-W2000-2 at Sat May 05 08:38:38 2007
Connection #1 from LAB-W2000-2 closed at Sat May 05 08:38:45 2007
(bin) 1 %

   I have and other demo board (DSP56F8013), all works correctly with the parallel programmer of AXIOm (JTAG-DSP/AXM0337), I prove the board of the DSP56F8037 with the parallel programmer and works correctly and connect USB TAP in board of 56F8013 and have the same error (CCSPrtocolPlugin: CCS Disconnected Cable). When I prove with a programmer the other is disconnects. I have verified which the configuration of CW R8.0 with USB TAP is correct:

 Edit \ Preferences \ Debugger \ Remote Connection \ (see attach image for configuraion)

 It seems that It is all correct one. I do not know where it is the problem.
Labels (1)
Tags (1)
0 Kudos
4 Replies

516 Views
J2MEJediMaster
Specialist I
Let me summarize what you've seen just to make sure I've got things straight.

1) The parallel port programmer works with both boards, so you know it isn't a board problem.
2) The USB cable doesn't work with either board.

This leads me to conclude that either the USB cable is bad, or there's a driver problem. Looking at your communications log, I see that the IDE is still trying to use the parallel port, lpt1. So, things aren't happening because the IDE still thinks it's talking to a parallel port. (Look at the line just past the "Executing autoexec.tcl..." phrase.)

How to correct this? See if there are any debugger settings for the project (Edit | YourProjectName Settings...), where you might pick the debugger interface. (The IDE setting should take care of this, but obviously it hasn't.) You may want to select the device driver in the Window hardware panel and right-click it to see if the driver is actually enabled.

Also, try building a project from scratch using the CodeWarrior Project Wizard and see if you can select the USB cable as the debugger interface, then try that on the board. HTH.

---Tom

0 Kudos

516 Views
Etxeondo
Contributor I
  Hi, TOM

  I think that the problem is in the IDE(CW R8.0) configurations but nothing with the documentation is said that it encloses with the development kit.

  I can see that the driver in Window hardware panel is actually enabled.

  I'm using wizard of CW, At any moment the any wizard (Simple Wizard, Processor Expert Wizard,..) asks that type of programmer you are going to use, for that reason I consult the options of configuration of remote to debugger,.

  I consult the menu Edir\preferences\Debugger\ Remote connection. I do not completely understand the options that are indicated, (en imatge attach) are 6 types of "connections", three for old cores and three for new cores.
1. - Local Hardware Connection - Paralel connection?
2. - The Premises USBTAP Connection - Usbtap
3. - Simulator.

 If I want to form some option of the USBTAP I press on change button (attached image), but there is no option to choose this programmer like favourite, I dont know what I must modify to indicate to CW that my present programmer is the USBTAP and not the parallel.


   Thanks.

0 Kudos

516 Views
Etxeondo
Contributor I
In the previous answer there is some error

Hi, TOM

  I think that the problem is in the IDE(CW R8.0) configurations but nothing with the documentation is said that it encloses with the development kit.

  I can see that the driver in Window hardware panel is actually enabled.

  I'm using wizard of CW, At any moment the any wizard (Simple Wizard, Processor Expert Wizard,..) asks that type of programmer you are going to use, for that reason I consult the options of configuration of remote to debugger,.

  I consult the menu Edir\preferences\Debugger\ Remote connection. I do not completely understand the options that are indicated, (en imatge attach) are 6 types of "connections", three for old cores and three for new cores.
1. - 56800E Local Hardware Connection - Paralel connection?
2. - 56800E Local USBTAP Connection - Usbtap
3. - 56800E Simulator.

 If I want to form some option of the USBTAP I press on change button (attached image), but there is no option to choose this programmer like favourite, I dont know what I must modify to indicate to CW that my present programmer is the USBTAP and not the parallel.


   Thanks.


 
0 Kudos

516 Views
Etxeondo
Contributor I
  
   Thanks, TOM

    I have understood a little better the operation of CW, the election of the type of debugger is not made from main menu:
 edit \ preferences \ debugger \ remote connections

They are made from main menu:

edit \ smm pROM_xRAM settings... \ Debugger \ remote debugging.

Now I have selected the USBTAP and I believe that everything works correctly.

Thanks, by everything.

0 Kudos