2386593_en-US

[#1]

MPC5200 detected by Codewarrior TAP over JTAG

Hello,

I have been struggling for a while with attaching the Codewarrior TAP debugger to a custom application board which is equipped with MPC5200.

Probe is "FREESCALE CodeWarrior USB TAP CWH-CTP-BASE-HE".

Probe tip is built by myself. Basically I found the pinout/schematic of the 2x15 connector on the site and did my own wiring to the board. I placed 10Kohms resistor between pin 30 and ground. Tip is recognized as "Power Architecture/JTAG COP"

I have been using CCS console exclusively. I did not use Codewarrior IDE so far.

Current status:

• findcc detects the TAP correctly.
• scanboard detects the JTAG chain and reports:

Device 0: Altera FPGA (IDCODE 0x020B20DD)
Device 1: MPC5200B rev. 2.x (IDCODE 0x1001101D)

Devices 2....7: IDCODE: FFFFFFFF, Device: Unknown Device.

• OpenOCD also detects exactly the same two devices, so the JTAG chain appears to be correct.
• The target is powered and running its application.

Problem:

Any attempt to configure the processor in CCS fails:

ccs::config_chain mgt5200

returns:

mgt5200: no connection to the target or unrecognized processor

ccs::get_config_chain always reports "test core" instead of mgt5200.

Low level JTAG commands (like jtag::get_speed) always return: Internal failure.

Questions:

1. Does the MPC5200 support any hardware or software mechanism that disables JTAG debug while still allowing IDCODE scans?
2. Are there known requirements regarding TRST, HRESET, boot straps, or BDM/JTAG enable pins for CCS to recognize the MPC5200?
3. Is there a way to obtain a more detailed attach log from CCS to determine which step fails after the IDCODE scan?

Really appreciate your for taking the time to read this,

Mihai

Re: MPC5200 detected by Codewarrior TAP over JTAG

Hello,

The behavior you observe (IDCODE scan working but debug attach failing) is consistent with MPC5200 architecture.
According to the MPC5200 documentation, the device uses a two-level JTAG structure: a master TAP (for standard JTAG/IDCODE) and a slave TAP for CPU debug (e300 COP interface). If the slave TAP is not enabled or not correctly selected, JTAG detection works, but debugger attach will fail. 

Recommend check:

Proper handling of TRST and reset signals (TAP must be in correct state)
Ability to reset/hold the device during attach
That the CPU debug (COP) interface is accessible (not blocked by hardware or configuration)
Correct JTAG chain configuration and TAP selection, especially in multi-device chains

Best regards,

Peter