FAQ for JTAG-PPC600
Error Message: "emulation pod configuration error" (MPC600/7XX) !QACK Termination (MPC603/7XX/74XX) home Documents FAQ FAQ for JTAG-PPC600 PDF document ( 8KB / Nov-3-2008 )

FAQ for JTAG-PPC600

Error Message: "emulation pod configuration error" (MPC600/7XX)
		Error message "emulation pod configuration error" after starting the T32 ICD software
	This error can have three sources: The CPU selection in the SYStem window does not match the CPU on the target. Check if the selection matches the processor on the target. Try to use auto detection (PPC..XX selection) if available. The CPU detection failed. Check the JTAG connection to the target. The CPU on the target is not supported by the used debugger software release. In most cases there is additional information given in the AREA window.
!QACK Termination (MPC603/7XX/74XX)
		Strange behavior during or after system.up; Step/Go do not work correctly; External memory flicker
	The !QACK signal is a confirmation input for the CPU. The signal indicates that no other device will access/use the 603 bus and no bus snoop is necessary by the CPU. Only after this confimation the CPU changes from user mode back to debug mode. Normally this signal is served by any external memory controller/bridge or any other logic. In this case the signal needs a pll-up because it's LOW active. If there is no device using the 603 bus or serve this signal, !QACK must have an pull-down or be died to GND. On a target with a MPC107 bus controller, some boot loaders configure the MPC107 so, that !QACK is driven HIGH if it is not asserted. The MPC107 has to be configured to tristate the signal in this case. If the signal is LOW, the debugger is not able to control the CPU properly.