<?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>CodeWarrior for MCUのトピックworkflow: BDM debugging with interrupts?</title>
    <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/workflow-BDM-debugging-with-interrupts/m-p/211453#M8335</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey everyone.&amp;nbsp; I've got a high-level sort of workflow question.&amp;nbsp; I'm using CodeWarrior 6, on mostly HCS08QG8, and JS16 targets, i.e. I stay in the BDM world for ease of debug.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Until recently, I've tried to use pseudo-RTOS type program flow, e.g., efficient time slicing and complex state machines to poll through my code.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, now I'm requiring a lot more interrupt-driven inputs.&amp;nbsp; Hod do you all use the BDM debugger with your interrupts?&amp;nbsp; For instance, I have an input capture coming from a periodic input.&amp;nbsp; So that interrupt is happening all the time.&amp;nbsp; Another example is the USB interrupts, which are also happening regularly.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Stepping through code seems futile to me, as you get hung up in the ISR all the time.&amp;nbsp; Just wondering what your workflow is.&amp;nbsp; Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 07 Jul 2010 20:48:09 GMT</pubDate>
    <dc:creator>irob</dc:creator>
    <dc:date>2010-07-07T20:48:09Z</dc:date>
    <item>
      <title>workflow: BDM debugging with interrupts?</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/workflow-BDM-debugging-with-interrupts/m-p/211453#M8335</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey everyone.&amp;nbsp; I've got a high-level sort of workflow question.&amp;nbsp; I'm using CodeWarrior 6, on mostly HCS08QG8, and JS16 targets, i.e. I stay in the BDM world for ease of debug.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Until recently, I've tried to use pseudo-RTOS type program flow, e.g., efficient time slicing and complex state machines to poll through my code.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, now I'm requiring a lot more interrupt-driven inputs.&amp;nbsp; Hod do you all use the BDM debugger with your interrupts?&amp;nbsp; For instance, I have an input capture coming from a periodic input.&amp;nbsp; So that interrupt is happening all the time.&amp;nbsp; Another example is the USB interrupts, which are also happening regularly.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Stepping through code seems futile to me, as you get hung up in the ISR all the time.&amp;nbsp; Just wondering what your workflow is.&amp;nbsp; Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Jul 2010 20:48:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/workflow-BDM-debugging-with-interrupts/m-p/211453#M8335</guid>
      <dc:creator>irob</dc:creator>
      <dc:date>2010-07-07T20:48:09Z</dc:date>
    </item>
    <item>
      <title>Re: workflow: BDM debugging with interrupts?</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/workflow-BDM-debugging-with-interrupts/m-p/211454#M8336</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Rob,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My systems are also highly interrupt driven, and it does cause debugging problems.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My first, and most desirable solution is to write code without bugs. Ok, I haven't perfected that tecnique yet.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;One thing that helps a lot is that there is a option in the debugger to automatically set the interrupt mask upon encountering a breakpoint. It at least allows you to then single-step without vectoring to an ISR, but your interrupts still trip over each other.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Helps a little.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Jul 2010 02:28:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/workflow-BDM-debugging-with-interrupts/m-p/211454#M8336</guid>
      <dc:creator>rocco</dc:creator>
      <dc:date>2010-07-08T02:28:09Z</dc:date>
    </item>
    <item>
      <title>Re: workflow: BDM debugging with interrupts?</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/workflow-BDM-debugging-with-interrupts/m-p/211455#M8337</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, Mark.&amp;nbsp; I'll give that a try next time.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Jul 2010 03:26:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/workflow-BDM-debugging-with-interrupts/m-p/211455#M8337</guid>
      <dc:creator>irob</dc:creator>
      <dc:date>2010-07-08T03:26:44Z</dc:date>
    </item>
    <item>
      <title>Re: workflow: BDM debugging with interrupts?</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/workflow-BDM-debugging-with-interrupts/m-p/211456#M8338</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Strange.&amp;nbsp; With a simple MTIM interrupt example software, I can't step through the code even with the "Disable interrupts while stepping" checkbox turned on in the True-Time Simulator.&amp;nbsp; The checkbox doesn't seem to affect anything, as the debugger gets hung up in the MTIM ISR.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This makes me think that there is some special something I'm missing in my source, maybe?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Sep 2010 01:33:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/workflow-BDM-debugging-with-interrupts/m-p/211456#M8338</guid>
      <dc:creator>irob</dc:creator>
      <dc:date>2010-09-23T01:33:31Z</dc:date>
    </item>
    <item>
      <title>Re: workflow: BDM debugging with interrupts?</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/workflow-BDM-debugging-with-interrupts/m-p/211457#M8339</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Figured out my problem.&amp;nbsp; In order for stepping to work uninterrupted, you must start stepping (or Run To Cursor) immediately after reset.&amp;nbsp; If you hit the green Start/Continue (F5) button, and then stop, you'll get stuck in the ISR.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Nov 2010 03:03:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/workflow-BDM-debugging-with-interrupts/m-p/211457#M8339</guid>
      <dc:creator>irob</dc:creator>
      <dc:date>2010-11-17T03:03:44Z</dc:date>
    </item>
  </channel>
</rss>

