<?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: Reset Cause in LPC Microcontrollers</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/Reset-Cause/m-p/562201#M16444</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by JohnR on Thu Sep 06 05:49:39 MST 2012&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;While we are beefing -- NXP manuals, at least the one for the LPC4350 devices, never show a list of changes from the previous version. This makes it very difficult to see if there has been a change that might affect one's usage of the device.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;John.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 15 Jun 2016 18:46:25 GMT</pubDate>
    <dc:creator>lpcware</dc:creator>
    <dc:date>2016-06-15T18:46:25Z</dc:date>
    <item>
      <title>Reset Cause</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Reset-Cause/m-p/562198#M16441</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by PhilYoung on Mon Sep 03 05:39:56 MST 2012&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;I'm debugging a boot loader that verifies and runs one of multiple images in a failsafe mode, for this I need to determine if a reset was caused by the watchdog, an app call, or a HW reset.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;According to the UM LPC_RGU-&amp;gt;RESET_EXT_STAT0 should return the reset cause, however when I enter the code I find this is always zero.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Is this being cleared by the boot rom code, and if so where is it storing the status?.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Has anybody found this yet?.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 18:46:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Reset-Cause/m-p/562198#M16441</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T18:46:22Z</dc:date>
    </item>
    <item>
      <title>Re: Reset Cause</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Reset-Cause/m-p/562199#M16442</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by fcarlo on Tue Sep 04 23:39:48 MST 2012&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;The errata sheet has been updated recently. Please check the latest version:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;RGU.1: CORE_RST status bits in the RESET_STATUS0 register do not work&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The CORE_RST bits in the RGU's status register do not properly indicate the cause of the &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;core reset. When th e core is reset the RGU is also reset and as a result the state of these &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;bits will always read with their default values.&amp;nbsp; As a result, these status bits cannot be used &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;to determine the cause of the core reset.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 18:46:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Reset-Cause/m-p/562199#M16442</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T18:46:23Z</dc:date>
    </item>
    <item>
      <title>Re: Reset Cause</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Reset-Cause/m-p/562200#M16443</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by PhilYoung on Wed Sep 05 05:41:13 MST 2012&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;It would really help if the documents on this site were managed correctly.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The errata for LPC43xx eppears in resources as updated 2012-02-23 19:55.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;actually downloading the document it was updated to Rev 2.2 on 8 August 2012, the previous update ( rev 2.1 ) which still has the same document name was updated on 13 July.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;How are we supposed to know when there is a new errata for a device if the document date or version number in the resources list is not updated.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;This really makes life difficult.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 18:46:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Reset-Cause/m-p/562200#M16443</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T18:46:24Z</dc:date>
    </item>
    <item>
      <title>Re: Reset Cause</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Reset-Cause/m-p/562201#M16444</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by JohnR on Thu Sep 06 05:49:39 MST 2012&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;While we are beefing -- NXP manuals, at least the one for the LPC4350 devices, never show a list of changes from the previous version. This makes it very difficult to see if there has been a change that might affect one's usage of the device.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;John.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 18:46:25 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Reset-Cause/m-p/562201#M16444</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T18:46:25Z</dc:date>
    </item>
    <item>
      <title>Re: Reset Cause</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Reset-Cause/m-p/562202#M16445</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by starblue on Wed Sep 12 00:53:53 MST 2012&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;There is a new manual dated September 3, which contain relevant updates.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 18:46:25 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Reset-Cause/m-p/562202#M16445</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T18:46:25Z</dc:date>
    </item>
  </channel>
</rss>

