S32DS GDB launch failure when connected through VPN

cancel
Showing results for 
Search instead for 
Did you mean: 

S32DS GDB launch failure when connected through VPN

120 Views
mikesfn
Contributor III

When my PC is either not connected to the internet, or connected only via my home wifi, there is no problem - so I know this is not an issue of normal project/debug settings.

 

However, when I am connected through a work VPN, I have 2 problems:

1) Any Clean or Build takes very long to perform (ex. 2 minutes to do a Clean, compared to less than 10 seconds normally)

2) Worse, I am not at all able to start a debug session. When I try I get the following 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:

 

Why would this behaviour be different based on the network connection? Again, when there is no network connection, there is no problem. Builds run normally and debugging works fine. 

Tags (3)
0 Kudos
3 Replies

104 Views
mikedoidge
NXP Employee
NXP Employee

Hello @mikesfn,

For the Build and Clean issues, could you try to invoke the compiler from command line, both with and without VPN? This will help to determine if there is something occurring from the S32DS IDE which is impacting the execution time.

As to the debugger issue, this may or may not be related. It is difficult to say, based on the provided details. I am assuming you are using the P&E Debug Probe (likely either the USB Multilink or OpenSDA (exists on some EVBs). Is there anything that comes after the 'response:' part of the error message?

Best Regards,

Mike

0 Kudos

92 Views
mikesfn
Contributor III

Sorry, I haven't had a chance to try this approach yet. The eval board is an S32K146EVB so it is using the PEMicro debugger through an OpenSDA port on the EVB.

There is nothing that comes after the "response:". It is just blank. 

Thanks,

0 Kudos

88 Views
mikedoidge
NXP Employee
NXP Employee

Hi @mikesfn,

We have had some similar reports in the past, though they are only reporting slow builds when connected to their company network, no reports on debug issues. This is partly why I doubt if these two issues are connected. Anyway, it appears there may be something going on when the connection to the company network is made that is impacting S32DS. Since we are unable to reproduce the issue, it is very difficult to solve and we are heavily reliant on the information we receive from the users who are affected.

For reference, here are the similar threads on slow build times:

https://community.nxp.com/t5/S32-Design-Studio/Build-time-is-very-high-with-S32DS-for-ARM-V2-0/m-p/7...

https://community.nxp.com/t5/S32-Design-Studio/Slow-build-time-with-S32DS-for-ARM-V2-0/m-p/710903

https://community.nxp.com/t5/S32-Design-Studio/S32-DS-Power-IDE-is-too-slow/m-p/800936

Best Regards,

Mike

0 Kudos