A breakpoint in PCP code seems not to work.

After loading of a TriCore/PCP application, setting of a breakpoint in PCP code and starting of the TriCore application the breakpoint seems not to work.

The reason is that a PCP breakpoint is realized by code exchange. The TriCore startup code of all known compilers initializes the PCP code memory (RAM) and therefore overwrite the breakpoint code. For debugging of PCP code it is necessary to execute the TriCore application at least until main function and then set the PCP breakpoints.

Microcontroller Architecture Support

Architectures vs UDE Product Features

Newest TriCore derivatives AURIX TC4x, TC39x, TC27x, TC29xED, Power Architecture / PowerPC derivatives as MPC5744P, MPC5744K, MPC5746M, MPC5777M and Cortex-M0, Cortex-M0+, Cortex-M3, Cortex-M4, Cortex-M7, Cortex-R4, Cortex-R52 Stellar, Cortex-A8, Cortex-A9, Cortex-A53 S32V, i.MX25, i.MX31 derivatives, SuperH SH-2A, XC2000, XE166, XMC1000, XMC4500, STM32, Stellar, S32, S32K, S32R are supported ... read more

Microcontroller Debugging Product finder

Go to

A breakpoint in PCP code seems not to work.

Microcontroller Architecture Support

Microcontroller Debugging Product finder

Webinars on Debugging with UDE

UDE DataSheets and Manuals

Contact