Hi，
I am using PE to debug NXP S32K314, the IDE is VS Code.
I disabled MCU JTAG without HSE enabled and used the authenticate_password_mode.py to authenticate the debugger. How can I secure debug the MCU in VS Code? I don't know how to configure the launch file.
Using pe micro gdb server: com.pemicro.debug.gdbjtag.pne_5.8.7.202407171925.
Thanks
Yumi,
Unfortunately, our VS Code extension does not support the S32K314 micro. If you want to debug any S32K device with the PEmicro Multilink or Cyclone, the only compatible IDE is the eclipsed based S32 Design Studio.
https://www.nxp.com/design/design-center/software/automotive-software-and-tools/s32-design-studio-ide:S32-DESIGN-STUDIO-IDE
Regards,
Johnny
PEmicro
Johnny，
We already used VSCode to develop S32K314，the configuration is as below. The problem is I can't select the device to S32K314-SECUREDEBUG. We already choose VS Code as IDE, and lock JTAG in production. When failure occurs, we need to analyze the software, if I want to secure debug S32K314, what should I do?
{
"configurations": [
{
"cwd": "${workspaceFolder}",
"executable": "./_build/PROJ_PL000001_PL_LVBMS_BOOT_CHERY.elf",
"name": "Debug with PEMicro",
"request": "launch",
"type": "cortex-debug",
"device": "NXP_S32K3xx_S32K314",
"runToEntryPoint": "main",
"showDevDebugOutput": "none",
"servertype": "pe",
"armToolchainPath": "C:/toolbox/gcc/gcc_v10.2/gcc-10.2-arm32-eabi/bin",
"gdbPath": "C:/toolbox/gdb/gdb-arm/arm32-eabi/bin/arm-none-eabi-gdb.exe",
"serverpath": "C:/toolbox/gdb/com.pemicro.debug.gdbjtag.pne_5.8.7.202407171925/win32/pegdbserver_console.exe",
"svdPath": "${workspaceFolder}/Tools/debug/svd/S32K314_M7.svd"
}
]
}
Hi Yumi,
You can try changing
"device": "NXP_S32K3xx_S32K314",
to
"device": "NXP_S32K3xx_S32K314-SECUREDEBUG",
But I have no idea if that is the correct fix. We cannot support the debugging of S32K3xx with VS Code. We can only help you if you use S32 Design Studio and eclipse.
Regards,
Johnny
Hi Johnny，
Yes, it works. I tried to do this before asking this question, but it failed for some reason. Yesterday I tried again, it just worked miraculously.
Thanks for your replying~~