<?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>S32 Design StudioのトピックRe: Problem debugging with S32DS and S32K146EVB</title>
    <link>https://community.nxp.com/t5/S32-Design-Studio/Problem-debugging-with-S32DS-and-S32K146EVB/m-p/781904#M3071</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jiri,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for the reply.&lt;/P&gt;&lt;P&gt;Debugger operates for 30min or more, up to one hour and then disconnects.&lt;/P&gt;&lt;P&gt;Unit continue to operate and respond to CAN messages.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Leonid Borshchak.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On Thu, Dec 13, 2018 at 10:30 AM jiri.kral@nxp.com &amp;lt;admin@community.nxp.com&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 13 Dec 2018 16:08:15 GMT</pubDate>
    <dc:creator>leonidborshchak</dc:creator>
    <dc:date>2018-12-13T16:08:15Z</dc:date>
    <item>
      <title>Problem debugging with S32DS and S32K146EVB</title>
      <link>https://community.nxp.com/t5/S32-Design-Studio/Problem-debugging-with-S32DS-and-S32K146EVB/m-p/781902#M3069</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My debugging platform - Windows7.&lt;/P&gt;&lt;P&gt;Development environment "S32 Design Studio for ARM". Version 2018.R1. Build id: 180815.&lt;/P&gt;&lt;P&gt;Connection to&amp;nbsp;S32K146EVB through OpenSDA.&lt;/P&gt;&lt;P&gt;I tried connection through "USB Multilink" from P&amp;amp;E Micro, but connection is even less stable than with OpenSDA.&amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;Break points are disabled, no Expressions.&lt;/P&gt;&lt;P&gt;Please, find attached image of the messages from debug console after debug session interrupted.&lt;/P&gt;&lt;P&gt;Please, find attached project.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Leonid Borshchak&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Dec 2018 17:19:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-Design-Studio/Problem-debugging-with-S32DS-and-S32K146EVB/m-p/781902#M3069</guid>
      <dc:creator>leonidborshchak</dc:creator>
      <dc:date>2018-12-10T17:19:50Z</dc:date>
    </item>
    <item>
      <title>Re: Problem debugging with S32DS and S32K146EVB</title>
      <link>https://community.nxp.com/t5/S32-Design-Studio/Problem-debugging-with-S32DS-and-S32K146EVB/m-p/781903#M3070</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;do you know when&amp;nbsp;is the debug session disconnected? It is right after&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CAN_InstallEventCallback((can_instance_t)instance, (can_callback_t)&amp;amp;canCallBack, NULL);&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;function is called?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For me is your code working okay.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Dec 2018 15:30:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-Design-Studio/Problem-debugging-with-S32DS-and-S32K146EVB/m-p/781903#M3070</guid>
      <dc:creator>jiri_kral</dc:creator>
      <dc:date>2018-12-13T15:30:02Z</dc:date>
    </item>
    <item>
      <title>Re: Problem debugging with S32DS and S32K146EVB</title>
      <link>https://community.nxp.com/t5/S32-Design-Studio/Problem-debugging-with-S32DS-and-S32K146EVB/m-p/781904#M3071</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jiri,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for the reply.&lt;/P&gt;&lt;P&gt;Debugger operates for 30min or more, up to one hour and then disconnects.&lt;/P&gt;&lt;P&gt;Unit continue to operate and respond to CAN messages.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Leonid Borshchak.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On Thu, Dec 13, 2018 at 10:30 AM jiri.kral@nxp.com &amp;lt;admin@community.nxp.com&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Dec 2018 16:08:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-Design-Studio/Problem-debugging-with-S32DS-and-S32K146EVB/m-p/781904#M3071</guid>
      <dc:creator>leonidborshchak</dc:creator>
      <dc:date>2018-12-13T16:08:15Z</dc:date>
    </item>
    <item>
      <title>Re: Problem debugging with S32DS and S32K146EVB</title>
      <link>https://community.nxp.com/t5/S32-Design-Studio/Problem-debugging-with-S32DS-and-S32K146EVB/m-p/781905#M3072</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you need some kind of long term monitoring - the UART ans serial terminal output is good solution. Or use more reliable probe.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jiri&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Dec 2018 17:51:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-Design-Studio/Problem-debugging-with-S32DS-and-S32K146EVB/m-p/781905#M3072</guid>
      <dc:creator>jiri_kral</dc:creator>
      <dc:date>2018-12-13T17:51:58Z</dc:date>
    </item>
    <item>
      <title>Re: Problem debugging with S32DS and S32K146EVB</title>
      <link>https://community.nxp.com/t5/S32-Design-Studio/Problem-debugging-with-S32DS-and-S32K146EVB/m-p/781906#M3073</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jiri,&lt;/P&gt;&lt;P&gt;Thank you for your reply. Please, advice about more reliable probe for&lt;/P&gt;&lt;P&gt;debugging.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Leonid Borshchak.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On Thu, Dec 13, 2018 at 12:52 PM jiri.kral@nxp.com &amp;lt;admin@community.nxp.com&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Dec 2018 18:11:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-Design-Studio/Problem-debugging-with-S32DS-and-S32K146EVB/m-p/781906#M3073</guid>
      <dc:creator>leonidborshchak</dc:creator>
      <dc:date>2018-12-13T18:11:15Z</dc:date>
    </item>
    <item>
      <title>Re: Problem debugging with S32DS and S32K146EVB</title>
      <link>https://community.nxp.com/t5/S32-Design-Studio/Problem-debugging-with-S32DS-and-S32K146EVB/m-p/781907#M3074</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can reproduce your issue. Thanks for report.&amp;nbsp; The PE Micro probe is disconnected after some time - up to one hour. I'll create Ticket for this bug.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, I tried same scenario with Segger j-link - and connection looks stable.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://www.segger.com/products/debug-probes/j-link/" title="https://www.segger.com/products/debug-probes/j-link/"&gt;J-Link Debug Probes | SEGGER - The Embedded Experts&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jiri&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Dec 2018 09:25:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-Design-Studio/Problem-debugging-with-S32DS-and-S32K146EVB/m-p/781907#M3074</guid>
      <dc:creator>jiri_kral</dc:creator>
      <dc:date>2018-12-14T09:25:06Z</dc:date>
    </item>
    <item>
      <title>Re: Problem debugging with S32DS and S32K146EVB</title>
      <link>https://community.nxp.com/t5/S32-Design-Studio/Problem-debugging-with-S32DS-and-S32K146EVB/m-p/781908#M3075</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jiri,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for the E-mail.&lt;/P&gt;&lt;P&gt;Could you mention the model of J-link tested?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Leonid Borshchak.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On Fri, Dec 14, 2018 at 4:25 AM jiri.kral@nxp.com &amp;lt;admin@community.nxp.com&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Dec 2018 13:01:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-Design-Studio/Problem-debugging-with-S32DS-and-S32K146EVB/m-p/781908#M3075</guid>
      <dc:creator>leonidborshchak</dc:creator>
      <dc:date>2018-12-14T13:01:30Z</dc:date>
    </item>
    <item>
      <title>Re: Problem debugging with S32DS and S32K146EVB</title>
      <link>https://community.nxp.com/t5/S32-Design-Studio/Problem-debugging-with-S32DS-and-S32K146EVB/m-p/781909#M3076</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Leonid,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm using Segger j-link lite:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://www.segger.com/products/debug-probes/j-link/models/j-link-lite/j-link-lite-cortex-m/" title="https://www.segger.com/products/debug-probes/j-link/models/j-link-lite/j-link-lite-cortex-m/"&gt;J-Link LITE Cortex-M | SEGGER - The Embedded Experts&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jiri&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Dec 2018 13:07:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-Design-Studio/Problem-debugging-with-S32DS-and-S32K146EVB/m-p/781909#M3076</guid>
      <dc:creator>jiri_kral</dc:creator>
      <dc:date>2018-12-14T13:07:53Z</dc:date>
    </item>
    <item>
      <title>Re: Problem debugging with S32DS and S32K146EVB</title>
      <link>https://community.nxp.com/t5/S32-Design-Studio/Problem-debugging-with-S32DS-and-S32K146EVB/m-p/781910#M3077</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jiri,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;J-Link LITE sold only for development board manufacturers.&lt;/P&gt;&lt;P&gt;S32DS officially doesn't support Segger, see link:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.nxp.com/support/developer-resources/run-time-software/s32-design-studio-ide/s32-design-studio-ide-for-arm-based-mcus:S32DS-ARM?tab=Hardware_Tab" target="test_blank"&gt;https://www.nxp.com/support/developer-resources/run-time-software/s32-design-studio-ide/s32-design-studio-ide-for-arm-based-mcus:S32DS-ARM?tab=Hardware_Tab&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;May be this link is outdated and you have new info.&lt;/P&gt;&lt;P&gt;I saw some discussions on the forum about use of Segger with S32DS.&lt;/P&gt;&lt;P&gt;May be J-link plus can work as well with S32DS and S32K146?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Leonid Borshchak.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On Fri, Dec 14, 2018 at 8:08 AM jiri.kral@nxp.com &amp;lt;admin@community.nxp.com&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Dec 2018 13:43:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-Design-Studio/Problem-debugging-with-S32DS-and-S32K146EVB/m-p/781910#M3077</guid>
      <dc:creator>leonidborshchak</dc:creator>
      <dc:date>2018-12-14T13:43:30Z</dc:date>
    </item>
    <item>
      <title>Re: Problem debugging with S32DS and S32K146EVB</title>
      <link>https://community.nxp.com/t5/S32-Design-Studio/Problem-debugging-with-S32DS-and-S32K146EVB/m-p/781911#M3078</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The j-link plus should be okay for S32K146 debugging.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jiri&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Dec 2018 13:50:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-Design-Studio/Problem-debugging-with-S32DS-and-S32K146EVB/m-p/781911#M3078</guid>
      <dc:creator>jiri_kral</dc:creator>
      <dc:date>2018-12-14T13:50:19Z</dc:date>
    </item>
    <item>
      <title>Re: Problem debugging with S32DS and S32K146EVB</title>
      <link>https://community.nxp.com/t5/S32-Design-Studio/Problem-debugging-with-S32DS-and-S32K146EVB/m-p/781912#M3079</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Leonid Borshchak.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On Fri, Dec 14, 2018 at 8:51 AM jiri.kral@nxp.com &amp;lt;admin@community.nxp.com&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Dec 2018 14:01:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-Design-Studio/Problem-debugging-with-S32DS-and-S32K146EVB/m-p/781912#M3079</guid>
      <dc:creator>leonidborshchak</dc:creator>
      <dc:date>2018-12-14T14:01:30Z</dc:date>
    </item>
  </channel>
</rss>

