Connection failed

[Taurus]

Hello Everyone,

I am using the CodeWarrior IDE Version 5.9.0. ( Build 2489 ) under LINUX.

When I try to program the Flash Memory of the Target I am getting the following Message:

"Error:  Connect Failed.  "

"Show Log" outputs:

"Connecting...
Flash Programmer: CCSProtocolPlugin::Could not connect to the requested core core #0."


After Enabling the Logging ( Preferences ), the Content of the generated Log File is as follows:

------------------------------------------------------------------

CCS: 0000    :    ccs_open
CCS:        :        ipaddr = 127.0.0.1
CCS:        :        port = 40114
CCS:        :        timeout = 60
CCS:        :        serverh = 0
CCS:        :    ccs_open; ccs_error = 0
CCS: 0000    :    ccs_get_connection_count
CCS:        :        serverh = 0
CCS:        :        count = 1
CCS:        :    ccs_get_connection_count; ccs_error = 0
CCS: 0000    :    ccs_set_timeout
CCS:        :        serverh = 0
CCS:        :        timeout = 60
CCS:        :    ccs_set_timeout; ccs_error = 0
CCS: 0000    :    ccs_available_connections
CCS:        :        serverh = 0
CCS:        :        count = 1
CCS:        :    ccs_available_connections; ccs_error = 0
CCS: 0000    :    ccs_available_connections
CCS:        :        serverh = 0
CCS:        :        count = 1
CCS:        :    ccs_available_connections; ccs_error = 0
CCS: 0000    :    ccs_supported_connections
CCS:        :        serverh = 0
CCS:        :        count = 7
CCS:        :    ccs_supported_connections; ccs_error = 0
CCS: 0000    :    ccs_config_server
CCS:        :        serverh = 0
CCS:        :        cc = 0
CCS:        :        server_config = 0
CCS:        :        value = 8000
CCS:        :    ccs_config_server; ccs_error = 0
CCS: 0000    :    ccs_get_config_chain
CCS:        :        serverh = 0
CCS:        :        device_list: (size = 0)
CCS:        :    ccs_get_config_chain; ccs_error = 0
CCS: 0000    :    ccs_config_chain
CCS:        :        serverh = 0
CCS:        :        cc = 0
CCS:        :        device_list: (size = 1)
CCS:        :            device[0]:: core_type=80;    device_descr=[ir_length:0;dr_bypass_length:0;bypass_instruction:0]
CCS:        :    ccs_config_chain; ccs_error = 0
CCS: 0000    :    ccs_get_config_chain
CCS:        :        serverh = 0
CCS:        :        device_list: (size = 4)
CCS:        :            device[0]:: core_type=0;    device_descr=[ir_length:0;dr_bypass_length:0;bypass_instruction:0]
CCS:        :            device[1]:: core_type=0;    device_descr=[ir_length:0;dr_bypass_length:0;bypass_instruction:0]
CCS:        :            device[2]:: core_type=0;    device_descr=[ir_length:0;dr_bypass_length:0;bypass_instruction:0]
CCS:        :            device[3]:: core_type=0;    device_descr=[ir_length:0;dr_bypass_length:0;bypass_instruction:0]
CCS:        :    ccs_get_config_chain; ccs_error = 0
CCS: 0000    :    ccs_get_config_chain
CCS:        :        serverh = 0
CCS:        :        device_list: (size = 4)
CCS:        :            device[0]:: core_type=80;    device_descr=[ir_length:0;dr_bypass_length:0;bypass_instruction:0]
CCS:        :            device[1]:: core_type=81;    device_descr=[ir_length:0;dr_bypass_length:0;bypass_instruction:0]
CCS:        :            device[2]:: core_type=81;    device_descr=[ir_length:0;dr_bypass_length:0;bypass_instruction:0]
CCS:        :            device[3]:: core_type=82;    device_descr=[ir_length:0;dr_bypass_length:0;bypass_instruction:0]
CCS:        :    ccs_get_config_chain; ccs_error = 0
CCS: 0000    :    ccs_available_connections
CCS:        :        serverh = 0
CCS:        :        count = 1
CCS:        :    ccs_available_connections; ccs_error = 0
CCS: 0000    :    ccs_available_connections
CCS:        :        serverh = 0
CCS:        :        count = 1
CCS:        :    ccs_available_connections; ccs_error = 0
CCS: 0000    :    ccs_supported_connections
CCS:        :        serverh = 0
CCS:        :        count = 7
CCS:        :    ccs_supported_connections; ccs_error = 0
CCS: 0000    :    ccs_close
CCS:        :        serverh = 0
CCS:        :    ccs_close; ccs_error = 0

------------------------------------------------------------------

When I enable "Reset Target on Launch", the Content of the log File is:

------------------------------------------------------------------
CCS: 0000    :    ccs_open
CCS:        :        ipaddr = 127.0.0.1
CCS:        :        port = 40116
CCS:        :        timeout = 60
CCS:        :        serverh = 0
CCS:        :    ccs_open; ccs_error = 0
CCS: 0000    :    ccs_get_connection_count
CCS:        :        serverh = 0
CCS:        :        count = 1
CCS:        :    ccs_get_connection_count; ccs_error = 0
CCS: 0000    :    ccs_set_timeout
CCS:        :        serverh = 0
CCS:        :        timeout = 60
CCS:        :    ccs_set_timeout; ccs_error = 0
CCS: 0000    :    ccs_available_connections
CCS:        :        serverh = 0
CCS:        :        count = 1
CCS:        :    ccs_available_connections; ccs_error = 0
CCS: 0000    :    ccs_available_connections
CCS:        :        serverh = 0
CCS:        :        count = 1
CCS:        :    ccs_available_connections; ccs_error = 0
CCS: 0000    :    ccs_supported_connections
CCS:        :        serverh = 0
CCS:        :        count = 7
CCS:        :    ccs_supported_connections; ccs_error = 0
CCS: 0000    :    ccs_config_server
CCS:        :        serverh = 0
CCS:        :        cc = 0
CCS:        :        server_config = 0
CCS:        :        value = 8000
CCS:        :    ccs_config_server; ccs_error = 0
CCS: 0000    :    ccs_get_config_chain
CCS:        :        serverh = 0
CCS:        :        device_list: (size = 0)
CCS:        :    ccs_get_config_chain; ccs_error = 0
CCS: 0000    :    ccs_config_chain
CCS:        :        serverh = 0
CCS:        :        cc = 0
CCS:        :        device_list: (size = 1)
CCS:        :            device[0]:: core_type=80;    device_descr=[ir_length:0;dr_bypass_length:0;bypass_instruction:0]
CCS:        :    ccs_config_chain; ccs_error = 0
CCS: 0000    :    ccs_get_config_chain
CCS:        :        serverh = 0
CCS:        :        device_list: (size = 4)
CCS:        :            device[0]:: core_type=0;    device_descr=[ir_length:0;dr_bypass_length:0;bypass_instruction:0]
CCS:        :            device[1]:: core_type=0;    device_descr=[ir_length:0;dr_bypass_length:0;bypass_instruction:0]
CCS:        :            device[2]:: core_type=0;    device_descr=[ir_length:0;dr_bypass_length:0;bypass_instruction:0]
CCS:        :            device[3]:: core_type=0;    device_descr=[ir_length:0;dr_bypass_length:0;bypass_instruction:0]
CCS:        :    ccs_get_config_chain; ccs_error = 0
CCS: 0000    :    ccs_get_config_chain
CCS:        :        serverh = 0
CCS:        :        device_list: (size = 4)
CCS:        :            device[0]:: core_type=80;    device_descr=[ir_length:0;dr_bypass_length:0;bypass_instruction:0]
CCS:        :            device[1]:: core_type=81;    device_descr=[ir_length:0;dr_bypass_length:0;bypass_instruction:0]
CCS:        :            device[2]:: core_type=81;    device_descr=[ir_length:0;dr_bypass_length:0;bypass_instruction:0]
CCS:        :            device[3]:: core_type=82;    device_descr=[ir_length:0;dr_bypass_length:0;bypass_instruction:0]
CCS:        :    ccs_get_config_chain; ccs_error = 0
CCS: 0000    :    ccs_reset_to_debug
CCS:        :        serverh = 0
CCS:        :        cc = 0
CCS:        :    ccs_reset_to_debug; c
CCS:        :        Error message:
MPC8641 SAP: Core not responding

CCS: 0000    :    ccs_reset_to_debug
CCS:        :        serverh = 0
CCS:        :        cc = 0
CCS:        :    ccs_reset_to_debug; ccs_error = 39
CCS:        :        Error message:
MPC8641 SAP: Core not responding

CCS: 0000    :    ccs_available_connections
CCS:        :        serverh = 0
CCS:        :        count = 1
CCS:        :    ccs_available_connections; ccs_error = 0
CCS: 0000    :    ccs_available_connections
CCS:        :        serverh = 0
CCS:        :        count = 1
CCS:        :    ccs_available_connections; ccs_error = 0
CCS: 0000    :    ccs_supported_connections
CCS:        :        serverh = 0
CCS:        :        count = 7
CCS:        :    ccs_supported_connections; ccs_error = 0
CCS: 0000    :    ccs_close
CCS:        :        serverh = 0
CCS:        :    ccs_close; ccs_error = 0

------------------------------------------------------------------

I tried two Probes and three Target Boards. No Difference in Behavior.

The Flash Programming actually did work some 3 Months ago
and nothing has changed meanwhile.

What could be the Reason for this Failure ?


Many Thanks for your Help !

best reagrds
Taurus

[shab]

Hi,

I have faced this problem earlier while doing flash programming through Tools->Flash programmer.

At that time, the target memory buffer address range is conflicting with the processor's exception vector table. Once I changed the target memory buffer address range, the problem got resolved.

[Rajkumar]

Hi,

I am having problem as likeyou as follow,

CCSProtocolPlugin::Could not connect to the requested core core #0."

Build Environment : LTIB(Linux Target Image builder).
Processor         : MPC8315eRDB
Linux version     : 2.6.24.3-rt3
debugging Environment : Codewarrior for Power Architecture Linux Platform edition
Host PC OS         : Fedora Core 5

I am having problem in connecting the target board with Codewarrior using USB TAB.

When ever If I pressed Debug tab or run tab or connect tab under debug option It is displaying message as CCSProtocolplugin::Could not connect to requested core core #0.

Please help me to resolve the problem.
 

[J2MEJediMaster]

I can infer from the log that you're using CodeWarrior for PowerPC. You've also mentioned it's the Linux hosted version. It's not clear what the target board is. The log indicates that it's an MPC8641 which--unless the logger is being terse--is a single-core processor. Yet the debugger seems to be trying to access a specfic core, which means its configured to debug a dual-core MPC8641D system. Check your debugger settings regarding the target processor.

---Tom

[wolf_ca]

Hi All,

  I am having the exact same problem with the MPC8641D, "ccs_error=39".  Did you come up with a solution to resolve this problem? or have some directions?

Many Thanks,

Mike

[Taurus]

Hello Tom,

it's a Custom Board with a MPC8641D on it.

The .cfg File includes:

<targetprocessor>8641D</targetprocessor>


After Loading the Config File, the Programmer displays a Target Processor as 8641D
( Target Configuration ).

Is there any other Place, where the Processor has to be specified in Addition ?


regards

[Taurus]

I added a JTag Configuration File for Multi Core Debugging within the CodeWarrior Ethernet TAP Preferences.

Content:

---------------------------------
MPC8641D

---------------------------------

Result: Same Behavior.

In the Log File the MPC8641 instead of the MPC8641D is still mentioned ( what Source does the Flash Programmer get the CPU Type from ? )

Is there any other Setting to be taken into Account for just Flash Programming, not Debugging ?

[J2MEJediMaster]

Have you also selected a memory initialization file? You choose that under the EPPC Debugger Settings panel, and check the Use Memory Configuration Option. The .mem file I'm using is 8641DHPCN.mem, which is located in the Memory directory. Even if you use that .mem file, the memory map it uses may be different from your custom hardware.

---Tom

[Taurus]

The XML Configuration File I load within the Flash Programmer
has the following Entry

    <targetinitfile>board.cfg</targetinitfile>

The board.cfg File contains the complete Mapping of the Board.

The Flash Programmer worked using these Files ( .xml and .cfg ) 3 Months ago.

Thereafter nothing has changed ( neither Hardware, nor Config Files )


Is there some Kind of Selftest, which can be used to verify the JTag Connection ?

[J2MEJediMaster]

I don't know if there is a test program or not for that. I suggest you file a service request on your problem. You can start that by clicking here.

---Tom