<?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: MC9S12 Hardware initialization in S12 / MagniV Microcontrollers</title>
    <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/MC9S12-Hardware-initialization/m-p/728459#M14878</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you for your reply.&lt;/P&gt;&lt;P&gt;I will try to figure out this problem as you mentioned.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 14 Feb 2018 14:00:51 GMT</pubDate>
    <dc:creator>rthym</dc:creator>
    <dc:date>2018-02-14T14:00:51Z</dc:date>
    <item>
      <title>MC9S12 Hardware initialization</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/MC9S12-Hardware-initialization/m-p/728457#M14876</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have some trouble recently when using MC9S12XDP512MAG MCU.&lt;/P&gt;&lt;P&gt;This MCU has been used in our product over 5 years, however, a trouble was found months ago.&lt;/P&gt;&lt;P&gt;This product serves as a communication board, in this board the MCU has been designed to be reset with a hardware watchdog &lt;SPAN class=""&gt;Supervisory&lt;/SPAN&gt;&amp;nbsp;IC(MAX705ESA). The COP function of MCU is not active.&lt;BR style="font-weight: normal;" /&gt;Once the assigned WDI(Watch Dog Input) pin on MCU was set to output, the&amp;nbsp;&lt;SPAN class=""&gt;Supervisory&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;IC will work.&amp;nbsp; WDI&amp;nbsp;will periodically(we use 500ms)&amp;nbsp; export a&amp;nbsp;5V signal to inform&amp;nbsp;&lt;SPAN class=""&gt;Supervisory&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;IC that MCU is all right. If the MCU pin WDI was set to output, and it does not export 5V signal&amp;nbsp;periodically,&amp;nbsp;&lt;SPAN class=""&gt;Supervisory&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;IC will generate a low-level voltage to reset the MCU.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;A problem was found when we using CAN measurement function, which means there were larger CAN messages interaction on CAN bus(we use CAN0 and CAN4)，the MCU stopped and the watchdog&amp;nbsp;&amp;nbsp;didn't reset the MCU successfully. After power-on again, the fault disappears.&lt;/P&gt;&lt;P&gt;More than one case was revealed and we have monitored the watchdog IC, the WDI pin was not set to output. I guess the MCU has ran to&amp;nbsp;initial state and stopped. One possibility was that MCU ran to exception that MCU pins become high-impedance state, or the MCU has been reset and it has not started successfully.&lt;/P&gt;&lt;P&gt;I want to know what can lead to this situation&amp;nbsp;that&amp;nbsp;MCU pins become unusual just like this case.&lt;/P&gt;&lt;P&gt;The can bus overloaded?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Software ran out of memory?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Feb 2018 05:44:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/MC9S12-Hardware-initialization/m-p/728457#M14876</guid>
      <dc:creator>rthym</dc:creator>
      <dc:date>2018-02-08T05:44:37Z</dc:date>
    </item>
    <item>
      <title>Re: MC9S12 Hardware initialization</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/MC9S12-Hardware-initialization/m-p/728458#M14877</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;The PORTs are in High impedance state out of reset.&lt;/P&gt;&lt;P&gt;So, the pin should stay in the output state unless a reset occurs.&lt;/P&gt;&lt;P&gt;Did you enable Clock monitor reset?&lt;/P&gt;&lt;P&gt;In this case it fetches Clock monitor reset vector instead of Reset vector.&lt;/P&gt;&lt;P&gt;In case of a stack overflow, it can do anything.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Daniel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Feb 2018 16:02:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/MC9S12-Hardware-initialization/m-p/728458#M14877</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2018-02-13T16:02:41Z</dc:date>
    </item>
    <item>
      <title>Re: MC9S12 Hardware initialization</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/MC9S12-Hardware-initialization/m-p/728459#M14878</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you for your reply.&lt;/P&gt;&lt;P&gt;I will try to figure out this problem as you mentioned.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Feb 2018 14:00:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/MC9S12-Hardware-initialization/m-p/728459#M14878</guid>
      <dc:creator>rthym</dc:creator>
      <dc:date>2018-02-14T14:00:51Z</dc:date>
    </item>
  </channel>
</rss>

