Renesas M32R-FPU Uživatelský manuál stáhnout pdf (Strana 11)

M32R Debugger and Trace 1 1 F A Q

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.

M32R

Compiler

Option for

Debug

Information

Why can I get just symbols and no code information loading a DWARF/ELF

file generated by Greenhills Compiler?

Greenhills has (at least for some families) a special compiler switch to generate

debug info in

ELF/DWARF format. Usually this is called "-dual_debug".

1 2 ... 6 7 8 9 10 11 12 13 14 15 16 ... 33 34

Žádné komentáře

Renesas M32R-FPU Uživatelský manuál Strana 11