https://community.nxp.com/t5/S32K/S32DS-for-ARM-2018-R1-debug-Problem/m-p/2414160#M61055 <P>S32DS for ARM 2018.R1 have a problem when I debug S32K146 chip, As follow:</P><P>Could not determine GDB version after sending: D:\S32DS\eclipse\../Cross_Tools/gcc-arm-none-eabi-4_9/bin/arm-none-eabi-gdb --version, response:</P><P>But, Jlink can cnonect and erase and program chip. Now, I do not debug using&nbsp;S32DS for ARM 2018.R1, Please help me, Thanks!</P> Thu, 17 Sep 2026 01:52:45 GMT lyz 2026-09-17T01:52:45Z https://community.nxp.com/t5/S32K/S32DS-for-ARM-2018-R1-debug-Problem/m-p/2414160#M61055 <P>S32DS for ARM 2018.R1 have a problem when I debug S32K146 chip, As follow:</P><P>Could not determine GDB version after sending: D:\S32DS\eclipse\../Cross_Tools/gcc-arm-none-eabi-4_9/bin/arm-none-eabi-gdb --version, response:</P><P>But, Jlink can cnonect and erase and program chip. Now, I do not debug using&nbsp;S32DS for ARM 2018.R1, Please help me, Thanks!</P> Thu, 17 Sep 2026 01:52:45 GMT https://community.nxp.com/t5/S32K/S32DS-for-ARM-2018-R1-debug-Problem/m-p/2414160#M61055 lyz 2026-09-17T01:52:45Z https://community.nxp.com/t5/S32K/S32DS-for-ARM-2018-R1-debug-Problem/m-p/2414228#M61059 <P>Hi@lyz</P> <P>I didn't quite understand your question. Could you post a screenshot of the error?</P> Thu, 17 Sep 2026 08:45:37 GMT https://community.nxp.com/t5/S32K/S32DS-for-ARM-2018-R1-debug-Problem/m-p/2414228#M61059 Senlent 2026-09-17T08:45:37Z