Specifications

Table Of Contents
ARM Debugger 1 3 F A Q
©1989-2014 Lauterbach GmbH
Setting a
Software
Breakpoint fails
What can be the reasons why setting a software breakpoint fails?
Setting a software breakpoint can fail when the target HW is not able to
implement the wanted breakpoint.
Possible reasons:
The wanted breakpoint needs special features that are only possible to
realize by the trigger unit inside the controller.
Example: Read, write and access (Read/Write) breakpoints ("type" in Break.Set
window). Breakpoints with checking in real-time for data-values ("Data").
Breakpoints with special features ("action") like TriggerTrace, TraceEnable,
TraceOn/TraceOFF.
TRACE32 can not change the memory.
Example: ROM and Flash when no preparation with FLASH.Create,
FLASH.TARGET and FLASH.AUTO was made. All type of memory if the
memory device is missing the necessary control signals like WriteEnable or
settings of registers and SpecialFunctionRegisters (SFR).
Contrary settings in TRACE32.
Like: MAP.BOnchip for this memory range. Break.SELect.<breakpoint-type>
Onchip (HARD is only available for ICE and FIRE).
RTOS and MMU:
If the memory can be changed by Data.Set but the breakpoint doesn't work it
might be a problem of using an MMU on target when setting the breakpoint to a
symbolic address that is different than the writable and intended memory
location.
Data values
onchip
breakpoints
Is it possible to set onchip breakpoints with data values?
ARM7/9 support setting onchip breakpoints with data values. ARM11, CORTEX
A/R does not support this capability. However, if the processor has an ETM
logic, TRACE32 can provide this functionality by using two of the address and
data comparators provided in the ETM. By setting the option
ETM.ReadWriteBreak, the resource management of TRACE32 is reconfigured
so that two address/data comparators of the ETM can be used as standard
read/write breakpoints. If the CPU does not support data values breakpoints and
the ETM is not used, TRACE32 will stop the CPU when the data address is
accessed, compare the data value with the condition and restart the CPU if the
values are not equal.
Error Message
Emulator Berr
Error
The message "emulator berr error" is displayed in some windows.
This message indicates that the ARM has entered the ABORT mode as result of
a system speed access from debug mode. The reason is, that at least one
memory access which was necessary to update the window was terminated
with active ABORT (if AMBA: ERROR) signal.