Lauterbach Support
Dashboard
Lauterbach Support
- [Arm] Does TRACE32 need access to the CoreSight ROM table?
- [Arm] How to access the memory on Cortex-A/R on run-time?
- [Arm] Break command returns "emulation running"
- [Arm] Can I attach to an Arm target without resetting the on-chip trace?
- Can I set an on-chip breakpoint on a physical address when the MMU is enabled?
- Using multiple USB devices with several TRACE32 instances
- How to force a connection to a debug module which is already in use?
- Why do I get the error message "Plugged debug cable is not suitable for CPU"?
- Is it possible to use both µTrace® connectors, A and B to debug two targets?
- What is the operational temperature range of TRACE32 hardware tools?
- Can I execute a PRACTICE script or command when a specific event occurs?
- Can I execute a PRACTICE script when a breakpoint is hit?
- Is it possible to run an external program from within TRACE32 PowerView?
- Is it possible to use PRACTICE macros inside dialogs?
- What do abbreviated TRACE32 commands mean?
- HARDERRORs, FIFOFULLs and FLOWERRORs in the trace
- What can cause a "BAD TRACE PACKET" indication in the trace?
- I get a target crash when processing the trace
- Trace.LOAD returns "incompatible analyzer data"
- Using trace STREAM mode, the PowerTrace buffer overflows. What are the prerequisites to use the STREAM mode?
- Erased FLASH cells are flickering or do not show the default erase value
- How can I improve the FLASH programming time?
- "FLASH algorithm did not execute completely" error occured when programming or erasing a FLASH memory
- "bus errors" when dumping FLASH memory during program/erase
- Which FLASH devices are currently supported?
Understanding PRACTICE through Script Debugging
This guide provides a basic introduction to PRACTICE and its execution model. It is primarily intended for new TRACE32 users who want to learn how PRACTICE scripts are executed and how to use TRACE32 to debug and understand their scripts.
View Guide