Specifications

Table Of Contents
ARM Debugger 1 7 F A Q
©1989-2014 Lauterbach GmbH
Cortex-A/-R
No information available
XSCALE
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 realize
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. Flash when no preparation with FLASH.Create,
FLASH.TARGET and FLASH.AUTO was made. All 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 is able to 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.
Arm Dongle
Modifications for ARM Debug Cable
http://www.lauterbach.com/faq/arm_dongle.pdf Modifications ARM Dongle