Code Warrior USB TAP Problem: Could not connect to CCS

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

Code Warrior USB TAP Problem: Could not connect to CCS

6,774 Views
filipjabin
Contributor I

Greetings everyone, 

I have a LS1021ATWR board which I want to flash using the CodeWarrior TAP probe.

I've installed Code Warrior Development Studio for Armv7 on Win7 x64

I have a problem when I'm trying to start the debugger on CodeWarrior:

 error.PNG

The problem is, when i'm trying to launch ccs.exe manually, it can detect the probe: 

probe_config.PNG

I've looked into this: Can't connect CCS 

and specifically: 

forum_output.PNG

I've tried writing these commands, and I don't have the same output, so I must think there might be some target connection error.

Here is my output: 

commands_output.PNG

Here is what happens when I launch the debugger from CodeWarrior: 

after_launching_debug.PNG

With log v :

after_launching_debug_verbose.PNG

It seems like a connection has been established and then immediatly closed. 

I've conncted the probe on my host pc with the USB cable and on my target jtag pins.

I have to mention that my SWITCHES are on default configuration as on Getting Started Guide for LS 1021ATWR here: http://www.farnell.com/datasheets/2000257.pdf 

When I power on the board, the LED D5 should turn off according to documentation, but it never does and it keeps lighting. The TX/RX of the probe is linking in a green color, but the RUN/PAUSE led is still in an orange color. 

Any help would be apreciated.

Thank you, 

Filip

0 Kudos
Reply
11 Replies

3,740 Views
mikedubya
Contributor I

@addiyi 

Was this ever resolved?  I'm seeing the same things on our custom LS1021A board...

(bin) 315 % delete all
(bin) 316 % config cc cwtap
(bin) 317 % ccs::config_server 0 10000
(bin) 318 %
(bin) 318 % ccs::config_chain {ls1020a dap sap2}
(bin) 319 % display ccs::get_config_chain
Chain Position 0: LS1020A
Chain Position 1: DAP
Chain Position 2: SAP2
(bin) 320 % source lsbp.tcl
(bin) 321 % lsbp::lsbp
reset_to_debug
LS1020A: Core not responding

(bin) 322 % source IDcode.tcl

Scanning for available TAPs connected via USB.....


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+
+ Available Remote Connections
+
+ 1 - CodeWarriorTAP - 00:04:9f:05:38:1f
+ 2 - CodeWarriorTAP - <Specify IP Address>
+ 3 - GigabitTAP - <Specify IP Address>
+
+ x - Exit Script without Changes
+
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Specify connection:
1

Configuring TAP Interface....

Configured Connection: cwtap : 00:04:9f:05:38:1f


TDO -----
|
* Device 0 IDCODE: 5BA00477 Device: ARM DAP rev 5.x
* Device 1 IDCODE: 16B0001D Device: NXP LS1021A rev 2.x
|
TDI -----

 

0 Kudos
Reply

3,738 Views
mikedubya
Contributor I

And here is the same without using the lsbp.tcl script:

(bin) 323 % delete all
(bin) 324 % config cc cwtap
(bin) 325 % ccs::config_chain {ls1020a dap sap2}
(bin) 326 % display ccs::get_config_chain
Chain Position 0: LS1020A
Chain Position 1: DAP
Chain Position 2: SAP2
(bin) 327 % ccs::config_template 0 4096 1
(bin) 328 % ccs::write_reg 0 rcw_src 0x9A
(bin) 329 % ccs::reset_to_debug
LS1020A: Core not responding

0 Kudos
Reply

5,539 Views
m_syed_ahmed
Contributor III

Hi @addiyi ,

We are facing similar issue. Please find the log when we run above command sequence.

loading history file ... 48 events added
CodeWarrior Connection Server console display active (Tcl8.4.6 / Tk8.4.6)
Loading CCSAPI Tcl interface (/home/firstview/Freescale/CW_ARMv7_v2019.10/CW_ARMv7/ARMv7/CodeWarrior/CodeWarrior_Plugins/Debugger/Protocols/../../../../../../Common/CCS/bin/ccstcl.so)...
Loading Svfburner (/home/firstview/Freescale/CW_ARMv7_v2019.10/CW_ARMv7/ARMv7/CodeWarrior/CodeWarrior_Plugins/Debugger/Protocols/../../../../../../Common/CCS/bin/svfburner.so)...
Server listening on port: 41475
Server listening on port: 41475
Clients allowed from all hosts
No clients denied
CCSAPI connection #1 accepted from localhost at Wed Dec 23 16:54:19 2020
(bin) 49 % log v
CCS Linux Release Build 490.0.0.190923-p0
verbose logging
(bin) 50 % config cc cwtap
Maximum number of Command Converters reached
config fail
(bin) 51 % ccs::config_chain {{8 1} ls1020a dap sap2}
(bin) 52 % display ccs::get_config_chain
Chain Position 0: Generic Device
Chain Position 1: LS1020A
Chain Position 2: DAP
Chain Position 3: SAP2
(bin) 53 % ccs::reset_to_debug
LS1020A: Core not responding
(bin) 54 %
(bin) 54 % delete all
(bin) 55 % config cc cwtap
(bin) 56 % ccs::config_chain {ls1020a dap sap2}
(bin) 57 % display ccs::get_config_chain
Chain Position 0: LS1020A
Chain Position 1: DAP
Chain Position 2: SAP2
(bin) 58 % ccs::reset_to_debug
LS1020A: Core not responding
(bin) 59 %

0 Kudos
Reply

5,721 Views
filipjabin
Contributor I

This is the output I received: 

3.PNG

Note: After I do ccs::reset_to_debug, the D5 led turns itself off.

Filip

0 Kudos
Reply

5,721 Views
yipingwang
NXP TechSupport
NXP TechSupport

Hello Filip,

Please check whether you are using LS1021A 1.0 processor.

In the CCS console, please run "source IDcode.tcl" to get more information.

If you are using reversion 1.0 CPU, please refer to the following procedure.

To debug a target with this processor revision you must use the CFG file "LS102xA_Rev1_ConfigChain.cfg" that can be found at the location
[CW install path]/ARMv7/ARM_Support/Configuration_Files/jtag_chains/. This file will be imported following the next steps:
1. Open "Debug Configurations..." and select your project;
2. Click on the "Edit..." button which can be found next to the drop list called "Connection" from the "Target Settings" view;
3. Click on the "Edit..." button which can be found next to the drop list called "Target";
4. Click on the "Edit..." button which can be found next to the drop list called "Target type";
5. Click "Import..." and then "File System..." and select the file specified above and then click OK until you return
to "Hardware or Simulator Target" window;
6. Select in the "Hardware or Simulator Target" window the initialization and memory files from the project;
7. Click OK until you return to "Debug Configurations..." window and click "Debug".


Have a great day,
TIC

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos
Reply

5,721 Views
addiyi
NXP Employee
NXP Employee

It could be because of missing RCW.

Try the followings:

delete all

config cc cwtap

ccs::config_chain {ls1020a dap sap2}

display ccs::get_config_chain

ccs::config_template 0 4096 1

ccs::write_reg 0 rcw_src 0x9A

ccs::reset_to_debug

Provide the output.

Adrian

0 Kudos
Reply

5,721 Views
filipjabin
Contributor I

This is my montage: 

20171107_173815.jpg

Note that the D5 led near the boards's jtag pins is always on, as opposed in the Getting Started Documentation I mentioned above.

The RUN/PAUSE Led is always on and orange 

and the TX/RX is blinking in a green color (The picture I Took is in between the blinks)

And these are my switches configuration (It's the default configuration as in the Documentation) :

20171107_173827.jpg

What can I do at this point ? The entire NOR flash of the board has been erased, that's why we've been trying to re-flash it with QorIQ 2.0 SDK included NOR Flash.bin on CodeWarrior.

0 Kudos
Reply

5,721 Views
filipjabin
Contributor I

The output for both commands is the same: 

LS1020A: Core Not responding

Does that mean that it's the connection between the probe and my target ? 

1.png

2.png

0 Kudos
Reply

5,721 Views
filipjabin
Contributor I

I have specifically the TWR-LS1021A 700-28040 revA 

0 Kudos
Reply

5,721 Views
addiyi
NXP Employee
NXP Employee

Can you try the followings commands in ccs:

config cc cwtap

ccs::config_chain {{8 1} ls1020a dap sap2}

display ccs::get_config_chain

ccs::reset_to_debug

after that:

delete all

config cc cwtap

ccs::config_chain {ls1020a dap sap2}

display ccs::get_config_chain

ccs::reset_to_debug

Provide the output.

Adrian

0 Kudos
Reply

5,721 Views
addiyi
NXP Employee
NXP Employee

Please provide info about the cpu version you use.

Adrian

0 Kudos
Reply