FAQs for MPC74XX Debugger
|Is there a workaround for MP7448 chip errata #24? (MPC7448)|
Due to MPC7448 chip errata #24, the processor may hang when store type instructions are single stepped with a JTAG debugger.
If you encounter this problem while single stepping through code in RAM, there is also a workaround implemented in the debugger. Enable this workaround using the command:
See Processor Architecture Manual for details about this command.
|SYStem.UP fails with MPC744x/MPC745x or MPC86xx. (MPC744X/745X/MPC86XX)|
SYStem.UP of MPC744X/5X/MPC86XX can fail if the instruction at the reset address is invalid. This is a side effect of a chip errata (e.g. MPC7448 chip errata #7)
If the FLASH memory at the reset address (0xFFF00100) is not programmed, the CPU will not stop at the reset address. The debugger will print an error message to the AREA window that the CPU stopped at a wrong address (0xFFF00800). In this case, use the sequence:
to stop the CPU.
If the SYStem.UP fails as described above, but it is known that the FLASH is programmed (e.g. boot loader running), usually the problem is that JTAG_HReset resets only the processor, but not other devices on the board, esp. the memory controller. If the memory controller will not be reset, the FLASH contents for the reset address are probably not mapped correctly. Make sure that JTAG_HReset resets processor and memory controller.
|The debugger can not display flash data and/or memory mapped registers, although the target program can access this memory/registers. (MPC744X/745X)|
The MPC744X/5X debug controller only supports burst accesses for the debugger. Some devices however, like flash devices or peripherial controllers do not support burst accesses.
There is a workaround, which can be activated using MAP.DENYBURST [address-range]. This workaround enables variable size memory accesses for the given address range. Please be aware that this workaround is very slow. Keep data.list/dump windows as small as possible and select a high JTAG frequency.
This issue is documented in Freescale's MPC74XX chip errata, errata #8 "Variable size memory accesses via COP cannot be performed using the service bus". MPC7448 and newer are not affected.
|What causes "emulation pod configuration error" when trying to start the debug session?|
This error can have several sources:
Copyright © 2019 Lauterbach GmbH, Altlaufstr.40, 85635 Höhenkirchen-Siegertsbrunn, Germany
The information presented is intended to give overview information only.
Changes and technical enhancements or modifications can be made without notice. Report Errors
Last generated/modified: 05-Dec-2019