Problem debugging with S32DS and S32K146EVB

[leonidborshchak]

My debugging platform - Windows7.

Development environment "S32 Design Studio for ARM". Version 2018.R1. Build id: 180815.

Connection to S32K146EVB through OpenSDA.

I tried connection through "USB Multilink" from P&E Micro, but connection is even less stable than with OpenSDA.   

Break points are disabled, no Expressions.

Please, find attached image of the messages from debug console after debug session interrupted.

Please, find attached project.

Thank you,

Leonid Borshchak

[jiri_kral]

Hi, 

do you know when is the debug session disconnected? It is right after

CAN_InstallEventCallback((can_instance_t)instance, (can_callback_t)&canCallBack, NULL);

function is called? 

For me is your code working okay. 

[leonidborshchak]

Hi Jiri,

Thank you for the reply.

Debugger operates for 30min or more, up to one hour and then disconnects.

Unit continue to operate and respond to CAN messages.

Thank you,

Leonid Borshchak.

On Thu, Dec 13, 2018 at 10:30 AM jiri.kral@nxp.com <admin@community.nxp.com>

[jiri_kral]

Hi,

thanks for info. Well, I'm afraid that in this case there is no solution. PE Micro is low cost probe and has some limitations. I'll try reproduce your issue, if I can reliably reproduce it, I'll create ticket for PE Micro team.

If you need some kind of long term monitoring - the UART ans serial terminal output is good solution. Or use more reliable probe. 

Jiri 

[leonidborshchak]

Hi Jiri,

Thank you for your reply. Please, advice about more reliable probe for

debugging.

Thank you,

Leonid Borshchak.

On Thu, Dec 13, 2018 at 12:52 PM jiri.kral@nxp.com <admin@community.nxp.com>

[jiri_kral]

Hi, 

I can reproduce your issue. Thanks for report.  The PE Micro probe is disconnected after some time - up to one hour. I'll create Ticket for this bug. 

So, I tried same scenario with Segger j-link - and connection looks stable. 

J-Link Debug Probes | SEGGER - The Embedded Experts 

Jiri

[leonidborshchak]

Hi Jiri,

Thank you for the E-mail.

Could you mention the model of J-link tested?

Thank you,

Leonid Borshchak.

On Fri, Dec 14, 2018 at 4:25 AM jiri.kral@nxp.com <admin@community.nxp.com>

[jiri_kral]

Hi Leonid, 

I'm using Segger j-link lite: 

J-Link LITE Cortex-M | SEGGER - The Embedded Experts 

Jiri 

[leonidborshchak]

Hi Jiri,

J-Link LITE sold only for development board manufacturers.

S32DS officially doesn't support Segger, see link:

https://www.nxp.com/support/developer-resources/run-time-software/s32-design-studio-ide/s32-design-s...

May be this link is outdated and you have new info.

I saw some discussions on the forum about use of Segger with S32DS.

May be J-link plus can work as well with S32DS and S32K146?

Thank you,

Leonid Borshchak.

On Fri, Dec 14, 2018 at 8:08 AM jiri.kral@nxp.com <admin@community.nxp.com>

[jiri_kral]

Hi, 

According to S32DS Arm v2018.R1 release notes - segger j-link is officially supported and all examples has debug configuration set to PE Micro and segger. 

The j-link plus should be okay for S32K146 debugging. 

Jiri

[leonidborshchak]

Thank you!

Leonid Borshchak.

On Fri, Dec 14, 2018 at 8:51 AM jiri.kral@nxp.com <admin@community.nxp.com>