<?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: Debugging with TPM and Interrupts in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Debugging-with-TPM-and-Interrupts/m-p/290774#M11622</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Chuck，&lt;/P&gt;&lt;P&gt;if that means you will burn up the high-power circuit when you enable the TPM at long time.&lt;/P&gt;&lt;P&gt;how about disconnect the power mosfet or its driver before you finish debugging the TPM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Good day&lt;/P&gt;&lt;P&gt;River&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 08 Jan 2014 03:30:41 GMT</pubDate>
    <dc:creator>riverliang</dc:creator>
    <dc:date>2014-01-08T03:30:41Z</dc:date>
    <item>
      <title>Debugging with TPM and Interrupts</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Debugging-with-TPM-and-Interrupts/m-p/290772#M11620</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is there a way to hit a breakpoint and have either a MCU pin automatically go LOW or to have the TPM module become disabled (and a pin go low)?&amp;nbsp; I'm working on a power control system and I'm using a PIT to interrupt and enable/disable TPM output based on an input.&amp;nbsp; If I break in the code when the TPM output is enabled, the board will likely burn up since I am no longer monitoring the input.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas?&amp;nbsp; I'm at a complete loss here.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Jan 2014 01:26:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Debugging-with-TPM-and-Interrupts/m-p/290772#M11620</guid>
      <dc:creator>chuckh</dc:creator>
      <dc:date>2014-01-08T01:26:43Z</dc:date>
    </item>
    <item>
      <title>Re: Debugging with TPM and Interrupts</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Debugging-with-TPM-and-Interrupts/m-p/290773#M11621</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, Chuck&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to make a confirm with your question. Do you mean that if MCU run to a breakpoint you set when TPM output is enable, MCU temperature will be very high, right? If yes, I think that is relative with your circuit design. If TPM pins was floating, I think it will not happen. So if possible, would you please help to provide your schematic? Only TPM pins connection. Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards&lt;/P&gt;&lt;P&gt;Paul&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Jan 2014 03:16:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Debugging-with-TPM-and-Interrupts/m-p/290773#M11621</guid>
      <dc:creator>Paul_Tian</dc:creator>
      <dc:date>2014-01-08T03:16:02Z</dc:date>
    </item>
    <item>
      <title>Re: Debugging with TPM and Interrupts</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Debugging-with-TPM-and-Interrupts/m-p/290774#M11622</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Chuck，&lt;/P&gt;&lt;P&gt;if that means you will burn up the high-power circuit when you enable the TPM at long time.&lt;/P&gt;&lt;P&gt;how about disconnect the power mosfet or its driver before you finish debugging the TPM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Good day&lt;/P&gt;&lt;P&gt;River&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Jan 2014 03:30:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Debugging-with-TPM-and-Interrupts/m-p/290774#M11622</guid>
      <dc:creator>riverliang</dc:creator>
      <dc:date>2014-01-08T03:30:41Z</dc:date>
    </item>
    <item>
      <title>Re: Debugging with TPM and Interrupts</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Debugging-with-TPM-and-Interrupts/m-p/290775#M11623</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think you misunderstood.&amp;nbsp; It's not a hardware problem, just the result of how the hardware works.&amp;nbsp; Weihua is more on the money here.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Jan 2014 21:38:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Debugging-with-TPM-and-Interrupts/m-p/290775#M11623</guid>
      <dc:creator>chuckh</dc:creator>
      <dc:date>2014-01-08T21:38:21Z</dc:date>
    </item>
    <item>
      <title>Re: Debugging with TPM and Interrupts</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Debugging-with-TPM-and-Interrupts/m-p/290776#M11624</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, clearly that is an option, but I would prefer a way that doesn't involve a change to the software or hardware when debugging.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Jan 2014 21:38:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Debugging-with-TPM-and-Interrupts/m-p/290776#M11624</guid>
      <dc:creator>chuckh</dc:creator>
      <dc:date>2014-01-08T21:38:51Z</dc:date>
    </item>
    <item>
      <title>Re: Debugging with TPM and Interrupts</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Debugging-with-TPM-and-Interrupts/m-p/290777#M11625</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you are relying on software to be correct with no single event upsets, no power supply glitches, never having a watchdog reset etc&amp;nbsp; for the rest of time then it *is* a hardware problem.&lt;/P&gt;&lt;P&gt;Put some dead-man protection in the hardware before a fire starts.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Jan 2014 15:44:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Debugging-with-TPM-and-Interrupts/m-p/290777#M11625</guid>
      <dc:creator>bobpaddock</dc:creator>
      <dc:date>2014-01-09T15:44:57Z</dc:date>
    </item>
    <item>
      <title>Re: Debugging with TPM and Interrupts</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Debugging-with-TPM-and-Interrupts/m-p/290778#M11626</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN class="SpellE"&gt;&lt;SPAN lang="ES-TRAD" style="mso-ansi-language: ES-TRAD;"&gt;Hi&lt;/SPAN&gt;&lt;/SPAN&gt; &lt;SPAN lang="ES-TRAD" style="mso-ansi-language: ES-TRAD;"&gt;&lt;SPAN class="SpellE"&gt;Chuck&lt;/SPAN&gt;,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For motor control applications debugging &lt;SPAN class="SpellE"&gt;FreeMaster&lt;/SPAN&gt; was created. You can &lt;SPAN class="SpellE"&gt;read&lt;/SPAN&gt; and change variables in run time, stop the timer before the breakpoint, tune parameters, etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="SpellE"&gt;Hava&lt;/SPAN&gt; a look :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=FREEMASTER&amp;amp;tid=vanFREEMASTER"&gt;http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=FREEMASTER&amp;amp;tid=vanFREEMASTER&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&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;Luis&lt;/P&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Jan 2014 17:46:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Debugging-with-TPM-and-Interrupts/m-p/290778#M11626</guid>
      <dc:creator>LuisCasado</dc:creator>
      <dc:date>2014-01-09T17:46:44Z</dc:date>
    </item>
  </channel>
</rss>

