MPC83XX : cannot Put the target in DEBUG Mode..

[SergAn]

Hi every one,

Programming NOR Flash over PA Flash Programmer Task [CW 10.5.1 > CodeWarrior TAP > Custom Board (MPC8321)] - generate Error:

fl::target -lc "MPC8323-core00_RAM_8323_Attach"
fl::target -b 0x0 0x40000
fl::target -v off -l off
cmdwin::fl::device -d "IN28F128J3" -o "8Mx16x1" -a 0xff000000 0xffffffff
cmdwin::fl::dump -range 0xff000000 0xff00ffff -t "Binary/Raw Format" -o "C:\\nxp\\u-boot.bin"
Beginning Operation ...
-------------------------
Performing target initialization ...
Error: Connect Failed.
Failed to reset the target
[CCS last error: mpc83xx: cannot put the target into DEBUG mode ](CCSProtocolPlugin)
Error: Connect Failed.

Log file from CSS: log.txt 

.....

Starting Arbitrary TAP State Move test ...
Test result: PASSED

Detected JTAG IDCODEs: OK
Device 0 IDCODE: 0x1698701D

ccs_jtag_unlock
serverh = 25
cc = 0
ccs_jtag_unlock; ccs_error = 0
ccs_config_chain
serverh = 25
cc = 0
device_list: (size = 1)
device[0]:: core_type=mpc83xx(55)
ccs_config_chain; ccs_error = 0
ccs_config_template
coreh = [serverh:25;cc_index:0;chain_pos:0]
config_reg = 1
config_data = 1
ccs_config_template; ccs_error = 0
ccs_config_template
coreh = [serverh:25;cc_index:0;chain_pos:0]
config_reg = 2
config_data = 1107624067
ccs_config_template; ccs_error = 0
ccs_config_template
coreh = [serverh:25;cc_index:0;chain_pos:0]
config_reg = 3
config_data = -1537212416
ccs_config_template; ccs_error = 0
ccs_get_config_chain
serverh = 25
device_list: (size = 1)
ccs_get_config_chain; ccs_error = 0
ccs_get_config_chain
serverh = 25
device_list: (size = 1)
device[0]:: core_type=mpc83xx(55)
ccs_get_config_chain; ccs_error = 0
ccs_send_message
coreh = [serverh:25;cc_index:0;chain_pos:0]
message = 3
ccs_send_message; ccs_error = 0
ccs_stop_core
coreh = [serverh:25;cc_index:0;chain_pos:0]
ccs_stop_core; ccs_error = -2147483639
Error message: cannot put the target into DEBUG mode
ccs_read_register
coreh = [serverh:25;cc_index:0;chain_pos:0]
index = 287
count = 1
size = 4
value: (size = 4)
7E021F00
ccs_read_register; ccs_error = -2147483638; duration=4 ms
Error message: MBIST: core is RUNNING!
ccs_stop_core
coreh = [serverh:25;cc_index:0;chain_pos:0]
ccs_stop_core; ccs_error = -2147483639
Error message: cannot put the target into DEBUG mode
ccs_get_messages
coreh = [serverh:25;cc_index:0;chain_pos:0]
message: (size = 0)
ccs_get_messages; ccs_error = 0
ccs_close
serverh = 25
ccs_close; ccs_error = 0
ccs_core_run_mode
coreh = [serverh:25;cc_index:0;chain_pos:0]
mode = 78446626
ccs_core_run_mode; ccs_error = 7
Error message: Invalid handle

In Configurations

- Connection Type - CodeWarrior TAP

- Target Type - 8323RDB_HRCW_jtag.txt => 8323 (1 1) (2 0x42050083) (3 0xA4600000)

What is the problem?

All ports connect only to CPU (no other resistors).

Thank!

[yipingwang]

When you create CodeWarrior project to do flash programming, in Debug Target Settings, please select "Download/Connect" launch configuration.

In your JTAG interface hardware design, please make sure HRESET exclusive to COP/JTAG header: problems arise when the core is reset and the debugger doesn’t know about it.

Usually the debugger will report the processor can not be put into STOP mode.

Please refer to page 5 in the attached PPT.

[SergAn]

Thanks for the answer!
I found the reason. Probably Accidentally shorted while connecting the TMS and VREF circuits on the CodeWarrior TAP cable. Now the TMS circuit at the TAP output is logic 1 and does not change when trying to connect to my board. Strange, I have always considered Freescale to be reliable, usually all output signals are protected from possible short circuits. Can you tell me which chip in CodeWarrior TAP is broken?

[yipingwang]

Please download CodeWarrior® TAP Schematic from the following link.

https://www.nxp.com/design/software/development-software/codewarrior-development-tools/run-control-d...