<?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: Runtime of Freemaster recorder is too much! in CodeWarrior Development Tools</title>
    <link>https://community.nxp.com/t5/CodeWarrior-Development-Tools/Runtime-of-Freemaster-recorder-is-too-much/m-p/634134#M5464</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Kidd,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We also have the same problem. We cannot use Freemaser at every 100us but yet we want to capture the data to see what is happening in the algorithm.&lt;/P&gt;&lt;P&gt;We are evaluating other options:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Use P&amp;amp;E micro's Multilink Universal debugger to connect to JTAG and connect the FreeMaster to it via JTAG for the above purpose.&lt;/LI&gt;&lt;LI&gt;&amp;nbsp;Use Vector's VX1000 tool box to connect to JTAG and use CANape to capture the data.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With 2nd option, we have been able to capture 32bytes at every 100us successfully at worst case execution!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps.&lt;BR /&gt;&lt;BR /&gt;Sagar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 09 Nov 2018 14:50:51 GMT</pubDate>
    <dc:creator>sagardhavali</dc:creator>
    <dc:date>2018-11-09T14:50:51Z</dc:date>
    <item>
      <title>Runtime of Freemaster recorder is too much!</title>
      <link>https://community.nxp.com/t5/CodeWarrior-Development-Tools/Runtime-of-Freemaster-recorder-is-too-much/m-p/634133#M5463</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I put the FMSTR_Recorder in PWM reload interrupt service routine, and tested its runtime. When triggered, its runtime could be more than 50us at most!&lt;/P&gt;&lt;P&gt;PWM frequency is 10kHz and period is 100us, if Recorder function takes too much time, then it will infuence algorithm running in PWM reload interrupt very badly.&lt;/P&gt;&lt;P&gt;How could this problem be solved?&lt;/P&gt;&lt;P&gt;P.S. If I use only scope, its runtime still could be more than 25us, which is also not acceptable.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Mar 2017 08:09:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-Development-Tools/Runtime-of-Freemaster-recorder-is-too-much/m-p/634133#M5463</guid>
      <dc:creator>kiddyang</dc:creator>
      <dc:date>2017-03-30T08:09:45Z</dc:date>
    </item>
    <item>
      <title>Re: Runtime of Freemaster recorder is too much!</title>
      <link>https://community.nxp.com/t5/CodeWarrior-Development-Tools/Runtime-of-Freemaster-recorder-is-too-much/m-p/634134#M5464</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Kidd,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We also have the same problem. We cannot use Freemaser at every 100us but yet we want to capture the data to see what is happening in the algorithm.&lt;/P&gt;&lt;P&gt;We are evaluating other options:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Use P&amp;amp;E micro's Multilink Universal debugger to connect to JTAG and connect the FreeMaster to it via JTAG for the above purpose.&lt;/LI&gt;&lt;LI&gt;&amp;nbsp;Use Vector's VX1000 tool box to connect to JTAG and use CANape to capture the data.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With 2nd option, we have been able to capture 32bytes at every 100us successfully at worst case execution!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps.&lt;BR /&gt;&lt;BR /&gt;Sagar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Nov 2018 14:50:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-Development-Tools/Runtime-of-Freemaster-recorder-is-too-much/m-p/634134#M5464</guid>
      <dc:creator>sagardhavali</dc:creator>
      <dc:date>2018-11-09T14:50:51Z</dc:date>
    </item>
  </channel>
</rss>

