<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: can not debug with S32 debug probe in S32G</title>
    <link>https://community.nxp.com/t5/S32G/can-not-debug-with-S32-debug-probe/m-p/1392657#M349</link>
    <description>&lt;P&gt;If you cannot normally pause and inspect where the program stopped, it means &lt;BR /&gt;your program code in memory has been destroyed during uncontrollable execution &lt;BR /&gt;or modified in a way that the debugger cannot get in sync with it. Use S32DS &lt;BR /&gt;trace and analysis feature to see where your processor gets out of control. &lt;BR /&gt;Details can be found in S32 Design Studio Tracing and Analysis User Guide. &lt;BR /&gt;This document is located at S32DS\help\ path from your S32DS installation &lt;BR /&gt;directory. &lt;/P&gt;
&lt;P&gt;Best Regards,&lt;BR /&gt;Platon&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 28 Dec 2021 11:19:58 GMT</pubDate>
    <dc:creator>bpe</dc:creator>
    <dc:date>2021-12-28T11:19:58Z</dc:date>
    <item>
      <title>can not debug with S32 debug probe</title>
      <link>https://community.nxp.com/t5/S32G/can-not-debug-with-S32-debug-probe/m-p/1392191#M342</link>
      <description>&lt;P&gt;After loading image with debug probe, the program stays in the very beginning main(). I can step into/ step over/ run(if there is already a break and the program will run to this break point by default) .&lt;/P&gt;&lt;P&gt;However, if there's no break point, after clicking "run", the program seems losing control. I can not pause,&amp;nbsp; read variables, or read registers. The only thing I can do is stop the whole debug project and relaunch again.&lt;/P&gt;&lt;P&gt;Any solution?&lt;/P&gt;</description>
      <pubDate>Mon, 27 Dec 2021 09:00:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/can-not-debug-with-S32-debug-probe/m-p/1392191#M342</guid>
      <dc:creator>Green1</dc:creator>
      <dc:date>2021-12-27T09:00:04Z</dc:date>
    </item>
    <item>
      <title>Re: can not debug with S32 debug probe</title>
      <link>https://community.nxp.com/t5/S32G/can-not-debug-with-S32-debug-probe/m-p/1392657#M349</link>
      <description>&lt;P&gt;If you cannot normally pause and inspect where the program stopped, it means &lt;BR /&gt;your program code in memory has been destroyed during uncontrollable execution &lt;BR /&gt;or modified in a way that the debugger cannot get in sync with it. Use S32DS &lt;BR /&gt;trace and analysis feature to see where your processor gets out of control. &lt;BR /&gt;Details can be found in S32 Design Studio Tracing and Analysis User Guide. &lt;BR /&gt;This document is located at S32DS\help\ path from your S32DS installation &lt;BR /&gt;directory. &lt;/P&gt;
&lt;P&gt;Best Regards,&lt;BR /&gt;Platon&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Dec 2021 11:19:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/can-not-debug-with-S32-debug-probe/m-p/1392657#M349</guid>
      <dc:creator>bpe</dc:creator>
      <dc:date>2021-12-28T11:19:58Z</dc:date>
    </item>
  </channel>
</rss>

