[S32DS 3.5] Debugging problem on GDB

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

[S32DS 3.5] Debugging problem on GDB

Jump to solution
3,284 Views
JunchanKwon
Contributor I

Deal all,

in order to connect to S32K116 board via J-Link using S32DS , it failed and report error:

"Could not determine GDB version after sending: C:\NXP\S32DS_ARM_v2.2\eclipse\../S32DS/build_tools/gcc_v6.3/gcc-6.3-arm32-eabi/bin/arm-none-eabi-gdb --version, response: "

JunchanKwon_0-1674023803964.png

 

I use

- OS:Windows10 Pro

- Debugger: J-Link Base

- IDE: S32DS 3.5

 

I alread read https://community.nxp.com/t5/S32-Design-Studio/Could-not-determine-GDB-version-when-i-try-to-connect... 

and to remove

warning: Couldn't determine a path for the index cache directory.

as in https://github.com/Marus/cortex-debug/issues/199 by system variable 'XDG_CACHE_HOME' as 'c:\Users\[myName]\.cache', and a result:

JunchanKwon_1-1674023918604.png

 

To verify H/W, I made a sample F/W with IAR IDE and programmed via same J-Link Base and it had no problem to do.

 

Please let me know how to solve this issue.

Thanks

 

0 Kudos
Reply
1 Solution
3,058 Views
mikedoidge
NXP Employee
NXP Employee

The path displayed in the error message does not match the path to the command. The correct path is:

"C:\NXP\S32DS_ARM_v2.2\S32DS\build_tools\gcc_v6.3\gcc-6.3-arm32-eabi\bin\arm-none-eabi-gdb.exe"

Notice, the 'eclipse' folder is not in the path. Probably this is a clue to your issue.

Best Regards,

Mike

View solution in original post

0 Kudos
Reply
4 Replies
3,043 Views
JunchanKwon
Contributor I

Thank you, Mr. Mike! You're the only one who helps my issue.

Frankly speaking, this issue cause from the security program at my company.

Sorry for my late response,

and have a nice day Mr. Mike! 

0 Kudos
Reply
3,270 Views
mikedoidge
NXP Employee
NXP Employee

Hello @JunchanKwon,

The information you have provided is confusing. The error message text you shared indicates you are using S32DS Arm v2.2, but the error message image shows S32DS 3.5. The error message text indicates you used GDB from GCC 6.3, however, there is no GCC 6.3 in S32DS 3.5. Please clarify the exact details of what version of GCC was used to compile the project and which version of GCC is the GDB you are using coming from. Perhaps your issue is due to some incompatible mix of GCC 6.3 and some other version of GDB?

Best Regards,

Mike

0 Kudos
Reply
3,267 Views
JunchanKwon
Contributor I

Thank you for your reply, and you are right (sorry for confusion, it's my mistake). 

I tried two IDE, S32DS 3.5 and S32DS Arm 2.2. First I tried S32DS 3.5 and later I installed S32DS Arm 2.2 and tried. (I formatted my notebook pc for these trials and reinstall Windows 10...)

However I got same results as below:

JunchanKwon_0-1674086017243.png

JunchanKwon_1-1674086222321.png

and the result of gdb version command lines:

JunchanKwon_3-1674086573123.png

 

JunchanKwon_2-1674086452446.png

Best regards,

Junchan

0 Kudos
Reply
3,059 Views
mikedoidge
NXP Employee
NXP Employee

The path displayed in the error message does not match the path to the command. The correct path is:

"C:\NXP\S32DS_ARM_v2.2\S32DS\build_tools\gcc_v6.3\gcc-6.3-arm32-eabi\bin\arm-none-eabi-gdb.exe"

Notice, the 'eclipse' folder is not in the path. Probably this is a clue to your issue.

Best Regards,

Mike

0 Kudos
Reply