MPC5674F + P&E Micro probe: Breakpoints in VS Code jump to RCHW with SIGINT/IVOR6 (works in S32 Design Studio)

[Narendra019]

Hello,

Debugging NXP MPC5674F (PowerPC e200z7, VLE) with VS Code + P&E Micro probe.

Toolchain: GCC powerpc-eabivle-gcc, GDB powerpc-eabivle-gdb

Debugger: P&E GDB Server (localhost:7224)

VS Code: [version], C++ / Cortex-Debug extension

Problem:

Breakpoints hit once, but on resume the PC jumps to 0x00000004 (RCHW).

Debugger log:
Program received signal SIGTRAP, Trace/breakpoint trap.
0x00000004 in RCHW ()
Program received signal SIGINT, Interrupt.
0x00000650 in IVOR6_Vector ()

Question:

Why does VS Code drop into RCHW + SIGINT/IVOR6 while S32DS works fine?

Is breakpoint/resume handling different in VS Code vs S32DS?

{
"name": "Debug MPC5674F",
"type": "cppdbg",
"request": "launch",
"program": "program.elf",
"MIMode": "gdb",
"miDebuggerPath": "C:/path/to/powerpc-eabivle-gdb.exe",
"miDebuggerServerAddress": "localhost:7224",
"stopAtEntry": true,
"setupCommands": [
{ "text": "target remote localhost:7224" },
{ "text": "monitor reset halt" },
{ "text": "load" }
]
}

[alefragnani]

Hi @Narendra019 ,

It seems you are having an issue with this Cortex-Debug extension, so I would suggest you to report the issue directly to the team behind this extension, on their support channel.

A Quick Look in the marketplace shows a few extension with similar name, so I’m not sure which one you use, to direct you to them. No matter if you access the marketplace via web or inside VS Code, you may look at Project Details area for their issues link.

Hope this helps