<?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: S32K146 RCM_SRS Register value for SWD reset in S32K</title>
    <link>https://community.nxp.com/t5/S32K/S32K146-RCM-SRS-Register-value-for-SWD-reset/m-p/998713#M5918</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Adria,&lt;/P&gt;&lt;P&gt;Yes, it makes sense.&lt;/P&gt;&lt;P&gt;Please refer to&amp;nbsp;J-Link / J-Trace User Guide&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://www.segger.com/downloads/jlink/UM08001" title="https://www.segger.com/downloads/jlink/UM08001"&gt;https://www.segger.com/downloads/jlink/UM08001&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;7.10&amp;nbsp; &amp;nbsp; Reset strategies&lt;/P&gt;&lt;P&gt;7.10.2&amp;nbsp; &amp;nbsp; Strategies for Cortex-M devices&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;BR,&amp;nbsp;Daniel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 27 Nov 2019 15:03:16 GMT</pubDate>
    <dc:creator>danielmartynek</dc:creator>
    <dc:date>2019-11-27T15:03:16Z</dc:date>
    <item>
      <title>S32K146 RCM_SRS Register value for SWD reset</title>
      <link>https://community.nxp.com/t5/S32K/S32K146-RCM-SRS-Register-value-for-SWD-reset/m-p/998710#M5915</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I&amp;nbsp;perform&amp;nbsp;a software reset by calling "SystemSoftwareReset()"&amp;nbsp;I read SW (bit 10) as reset cause int the RCM_SRS register. That is perfect.&lt;/P&gt;&lt;P&gt;But when I perform a reset through&amp;nbsp;SWD from the IDE (S32 Design Studio) I am getting the same reset cause.&lt;/P&gt;&lt;P&gt;Is that the correct behaviour?&lt;/P&gt;&lt;P&gt;I can see there is a bit field in the&amp;nbsp;&lt;SPAN&gt;RCM_SRS&amp;nbsp;register for a reset caused by JTAG, shouldn't this be the one active when the reset is caused by SWD?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Adria&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Nov 2019 16:16:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K146-RCM-SRS-Register-value-for-SWD-reset/m-p/998710#M5915</guid>
      <dc:creator>adria</dc:creator>
      <dc:date>2019-11-15T16:16:03Z</dc:date>
    </item>
    <item>
      <title>Re: S32K146 RCM_SRS Register value for SWD reset</title>
      <link>https://community.nxp.com/t5/S32K/S32K146-RCM-SRS-Register-value-for-SWD-reset/m-p/998711#M5916</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Adria,&lt;/P&gt;&lt;P&gt;What debugger are you using?&lt;/P&gt;&lt;P&gt;Have you tried resetting the MCU while running an empty project?&lt;/P&gt;&lt;P&gt;The&amp;nbsp;JTAG flag is set only if the debugger selects a certain&amp;nbsp;IR codes.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/94547iE100CBF55F04E464/image-size/large?v=v2&amp;amp;px=999" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/94572iDD97040EBFE0BDE3/image-size/large?v=v2&amp;amp;px=999" title="pastedImage_2.png" alt="pastedImage_2.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;But the debugger can reset the MCU using&amp;nbsp;external reset pin as well.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR, Daniel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Nov 2019 14:51:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K146-RCM-SRS-Register-value-for-SWD-reset/m-p/998711#M5916</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2019-11-19T14:51:11Z</dc:date>
    </item>
    <item>
      <title>Re: S32K146 RCM_SRS Register value for SWD reset</title>
      <link>https://community.nxp.com/t5/S32K/S32K146-RCM-SRS-Register-value-for-SWD-reset/m-p/998712#M5917</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Daniel,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am using Segger J-Link.&amp;nbsp;When I perform the reset through the IDE (S32 Design Studio) I get a Software reset, and this bit says:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"Software&lt;BR /&gt; Indicates a reset has been caused by software setting of SYSRESETREQ bit in Application Interrupt and&lt;BR /&gt; Reset Control Register in the Arm core.&lt;BR /&gt; 0 Reset not caused by software setting of SYSRESETREQ bit&lt;BR /&gt; 1 Reset caused by software setting of SYSRESETREQ bit"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Instead, when&amp;nbsp;I use PE Micro Multilink Universal as debugger, I get External Reset Pin, and this bit says:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"External Reset Pin&lt;BR /&gt; Indicates a reset has been caused by an active-low level on the external RESET (RESET_b) pin.&lt;BR /&gt; 0 Reset not caused by external reset pin&lt;BR /&gt; 1 Reset caused by external reset pin"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This last one (with&amp;nbsp;Multilink debugger) makes more sense for me because the debugger can write on the MCU reset pin and so cause a reset through that pin. But in the case of the&amp;nbsp;J-Link debugger, it just felt weird that a reset cause by a user through the debugger triggers a Software reset, which normally is done programmatically from the code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The only thing I would like to know if it all makes sense?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Adria&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Nov 2019 19:11:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K146-RCM-SRS-Register-value-for-SWD-reset/m-p/998712#M5917</guid>
      <dc:creator>adria</dc:creator>
      <dc:date>2019-11-26T19:11:37Z</dc:date>
    </item>
    <item>
      <title>Re: S32K146 RCM_SRS Register value for SWD reset</title>
      <link>https://community.nxp.com/t5/S32K/S32K146-RCM-SRS-Register-value-for-SWD-reset/m-p/998713#M5918</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Adria,&lt;/P&gt;&lt;P&gt;Yes, it makes sense.&lt;/P&gt;&lt;P&gt;Please refer to&amp;nbsp;J-Link / J-Trace User Guide&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://www.segger.com/downloads/jlink/UM08001" title="https://www.segger.com/downloads/jlink/UM08001"&gt;https://www.segger.com/downloads/jlink/UM08001&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;7.10&amp;nbsp; &amp;nbsp; Reset strategies&lt;/P&gt;&lt;P&gt;7.10.2&amp;nbsp; &amp;nbsp; Strategies for Cortex-M devices&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;BR,&amp;nbsp;Daniel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Nov 2019 15:03:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K146-RCM-SRS-Register-value-for-SWD-reset/m-p/998713#M5918</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2019-11-27T15:03:16Z</dc:date>
    </item>
    <item>
      <title>Re: S32K146 RCM_SRS Register value for SWD reset</title>
      <link>https://community.nxp.com/t5/S32K/S32K146-RCM-SRS-Register-value-for-SWD-reset/m-p/998714#M5919</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Daniel,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Adria&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Nov 2019 16:31:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K146-RCM-SRS-Register-value-for-SWD-reset/m-p/998714#M5919</guid>
      <dc:creator>adria</dc:creator>
      <dc:date>2019-11-27T16:31:55Z</dc:date>
    </item>
  </channel>
</rss>

