![]() Here's a log from the debug console (should contain all version info):Ĭonnection from "127.0.0.1" via 127.0.0.1. * Multlink FX and CycloneFX (both via USB) * tried bridging USB shielding to lab power supply (used to power DUT) I also don't see anything in the debugger logs that indicates trouble (see below). It first worked but after some updates it no longer worked. In addition I was having issues with v2018.R1 and installed v2.2 because of that. It definetly used to work with the exact same config and software - I reverted in git to verify that. For Segger it works with Segger Embedded Studio but shows quite the same behavior with S32DS. Since I had similar issues with Segger j-link Ultra+ I suspect it's a driver/software/gdb issue. So basically I can not set breakpoints while the device is running?! All I can do is start a new debug session (after manually clsoing all open debug processes in Eclipse/S32DS) or if I'm lucky trigger a pre-existing breakpoint I didn't disable and then set up new breakpoints while the device is stopped. However once I remove/disable all breakpoints and let the target run freely I can no longer get the target to stop. Breakpoints also work - even those in rarely called locations. I can connect to the board, start a debug session and step through just fine. I'm having some weird issues debugging custom S32K devices with S32DS ARM v2.2 and v2018.R1.
0 Comments
Leave a Reply. |