<?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>LayerscapeのトピックRe: Watchdog timer for LX2160A - reset identification</title>
    <link>https://community.nxp.com/t5/Layerscape/Watchdog-timer-for-LX2160A-reset-identification/m-p/1702788#M13052</link>
    <description>&lt;P&gt;The RSTRQSR contains status bits to record the reasons for RESET_REQ_B assertion. The bits here are set independent of the RSTRQMR. This means if a reset occurs and is masked by RSTRQMR, it will still be recoreded in RSTRQSR. Excludes core watchdog timer sources ).&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="yipingwang_0-1691656079745.png" style="width: 721px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/235924i41B878C60DD96D4B/image-dimensions/721x408?v=v2" width="721" height="408" role="button" title="yipingwang_0-1691656079745.png" alt="yipingwang_0-1691656079745.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;TrustZone WDOG second timeout goes &lt;STRONG&gt;to&lt;/STRONG&gt; HREST_REQ&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 10 Aug 2023 08:33:04 GMT</pubDate>
    <dc:creator>yipingwang</dc:creator>
    <dc:date>2023-08-10T08:33:04Z</dc:date>
    <item>
      <title>Watchdog timer for LX2160A - reset identification</title>
      <link>https://community.nxp.com/t5/Layerscape/Watchdog-timer-for-LX2160A-reset-identification/m-p/1702704#M13048</link>
      <description>&lt;P&gt;Hi&lt;BR /&gt;&lt;BR /&gt;I am working with LX2160A processor and SDK 20.12. when the watchdog timer is about to reset, is there any application or any other way to identify that the reset is due to this?&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Aug 2023 07:01:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/Watchdog-timer-for-LX2160A-reset-identification/m-p/1702704#M13048</guid>
      <dc:creator>anjana1</dc:creator>
      <dc:date>2023-08-10T07:01:19Z</dc:date>
    </item>
    <item>
      <title>Re: Watchdog timer for LX2160A - reset identification</title>
      <link>https://community.nxp.com/t5/Layerscape/Watchdog-timer-for-LX2160A-reset-identification/m-p/1702788#M13052</link>
      <description>&lt;P&gt;The RSTRQSR contains status bits to record the reasons for RESET_REQ_B assertion. The bits here are set independent of the RSTRQMR. This means if a reset occurs and is masked by RSTRQMR, it will still be recoreded in RSTRQSR. Excludes core watchdog timer sources ).&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="yipingwang_0-1691656079745.png" style="width: 721px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/235924i41B878C60DD96D4B/image-dimensions/721x408?v=v2" width="721" height="408" role="button" title="yipingwang_0-1691656079745.png" alt="yipingwang_0-1691656079745.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;TrustZone WDOG second timeout goes &lt;STRONG&gt;to&lt;/STRONG&gt; HREST_REQ&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 10 Aug 2023 08:33:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/Watchdog-timer-for-LX2160A-reset-identification/m-p/1702788#M13052</guid>
      <dc:creator>yipingwang</dc:creator>
      <dc:date>2023-08-10T08:33:04Z</dc:date>
    </item>
  </channel>
</rss>

