I can not connect my target board with USB TAP(code warrior 10.5.1)，report “CCSProtocolPlugin::Could not connect to the requested core #0.”

[chuxiankai]

I can not connect my new target board(P1010)with USB TAP(code warrior 10.5.1) ，code warrior reports “CCSProtocolPlugin::Could not connect to the requested core #0.”，but I can connect P1010RDB demo board and program bootrom. My target borad CPU is P1010NXE5HHB(industrial 800MHz/800MHz)；

On target board I measure some signals:

1.AFTER reset IFC_CS0 signal always is high.

2.CPU_CHECK_STOP_OUT# always is high.

3.After several times CPU_READY signal will pull high.

I check somes hardware info(these configs is same as P1010RDB demo):

1.core voltage: 1.0V is ok.

3.+3.3V voltage is ok.

4.+1.8V & +1.5V  voltage is ok.

5.+2.5V voltage is ok.

6.sysclk 66.67MHz is ok.

7.por config of frequency，this config is same as P1010RDB demo por config:

   7.1.CCB clock/sysclk is 6:1(400MHz) and IFC_PAR1 is 1（CCB clock frequency is greater than or equal to 300MHz）

   7.2 DDR clk/ sysclk is 10:1(667MHz)

   7.3 core/ccb is 2:1 (800MHz) and IFC_AD6 is 1(Core clock frequency is greater than or equal to 450MHz)

8.boot location is 16bit NOR.

9.boot sequence is disable.

10.BVDD config is 3.3V.

CCS logs as follow:

ccs_open
ipaddr = 127.0.0.1
port = 41475
timeout = 15
serverh = 0
ccs_open; ccs_error = 10
Error message: Connection refused
ccs_open
ipaddr = 127.0.0.1
port = 41475
timeout = 15
serverh = 0
ccs_open; ccs_error = 0
ccs_get_connection_count
serverh = 0
count = 1
ccs_get_connection_count; ccs_error = 0
ccs_available_connections
serverh = 0
count = 0
ccs_available_connections; ccs_error = 0
ccs_available_connections
serverh = 0
count = 0
ccs_available_connections; ccs_error = 0
ccs_config_cc
serverh = 0
config_string = utap:0
ccs_config_cc; ccs_error = 0
ccs_available_connections
serverh = 0
count = 1
ccs_available_connections; ccs_error = 0
ccs_cc_version
serverh = 0
cc = 0
version.major = 1
version.minor = 3
ccs_cc_version; ccs_error = 0
ccs_set_timeout
serverh = 0
timeout = 15
ccs_set_timeout; ccs_error = 0
ccs_available_connections
serverh = 0
count = 1
ccs_available_connections; ccs_error = 0
ccs_config_server
serverh = 0
cc = 0
server_config = 0
value = 1002
ccs_config_server; ccs_error = 0
ccs_config_chain
serverh = 0
cc = 0
device_list: (size = 1)
device[0]:: core_type=test core(20)
ccs_config_chain; ccs_error = 0
ccs_jtag_lock
serverh = 0
cc = 0
ccs_jtag_lock; ccs_error = 0
JTAG Diagnostics

Starting Power at Probe test ...
Test result: PASSED

Starting IR Scan test ...
Error measuring IR length
ccs_jtag_unlock
serverh = 0
cc = 0
ccs_jtag_unlock; ccs_error = 0
ccs_config_chain
serverh = 0
cc = 0
device_list: (size = 1)
device[0]:: core_type=p1010(219)
ccs_config_chain; ccs_error = 0
ccs_get_config_chain
serverh = 0
device_list: (size = 1)
ccs_get_config_chain; ccs_error = 0
ccs_get_config_chain
serverh = 0
device_list: (size = 1)
device[0]:: core_type=p1010(219)
ccs_get_config_chain; ccs_error = 0
ccs_core_run_mode
coreh = [serverh:0;cc_index:0;chain_pos:0]
mode = 4
ccs_core_run_mode; ccs_error = 5
Error message: Core not responding
ccs_available_connections
serverh = 0
count = 1
ccs_available_connections; ccs_error = 0
ccs_delete_cc
serverh = 0
count = 0
ccs_delete_cc; ccs_error = 0
ccs_kill_server
serverh = 0
ccs_kill_server; ccs_error = 0

Please help me, Thanks！

Original Attachment has been moved to: 201704181913_DiagnosticInfo.zip

[chuxiankai]

Hi Yiping

I modify my cpld file and this Issue has resolved

Thanks

[yipingwang · Accepted solution]

Hello chu xiankai,

It seems that there is JTAG interface hardware design problem on your target board.

According to the JTAG diagnostic information in the CCS log, there is an error "Error measuring IR length", this error might be due to one or more of the following reasons, please check your hardware design.

• TRST stuck low: This may hold the target JTAG logic in reset, preventing any shifts to occur.
• TMS disconnected or stuck: This may prevent the target from making any JTAG state changes.
• TCK disconnected or stuck: This may prevent any state changes or clocking of data.
• TDI disconnected or stuck: This may prevent the test pattern data from getting into the target.
• TDO disconnected or stuck: This may prevent the test pattern data from getting out of the target.

Please compare your design with page 6 of the attached ppt.

Have a great day,
TIC

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