<?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のトピックPEMicro TraceLink trace ends prematurely</title>
    <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/PEMicro-TraceLink-trace-ends-prematurely/m-p/683258#M13985</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm having a problem using my PEMicro Tracelink with CodeWarrior, attempting to trace the execution of firmware on a Cortex-M0+. &amp;nbsp;The trace ends prematurely, well before the 128Mb of configured trace buffer is filled. &amp;nbsp;Oddly, each trace seems to stop after a different number of trace records, sometimes in the 3k range, sometime in the 5k range. &amp;nbsp;When the trace stops, it halts the processor and drops me into the debugger at a return from a function, in code that I was expecting to be running. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have the "Trace Max Buffer Size" option set to 128 Mb in the target settings, and in the Trace and Profile settings I have the "Trace Buffer Size" set to 0x2000, with "Continuous" selected. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm tracing third-party code, so I'm stuck without source, but I can set a breakpoint where I want to begin trace and that works well. &amp;nbsp;The problem is that the assembly should clearly be looping for a very long time but something is happening that exits the loop and I want to know what. &amp;nbsp;Interrupts are disabled, but I was hoping a trace would catch an interrupt if that was the culprit and I was simply misunderstanding the assembly. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance for the assistance.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 26 Jul 2017 01:37:31 GMT</pubDate>
    <dc:creator>robertgrimshaw</dc:creator>
    <dc:date>2017-07-26T01:37:31Z</dc:date>
    <item>
      <title>PEMicro TraceLink trace ends prematurely</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/PEMicro-TraceLink-trace-ends-prematurely/m-p/683258#M13985</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm having a problem using my PEMicro Tracelink with CodeWarrior, attempting to trace the execution of firmware on a Cortex-M0+. &amp;nbsp;The trace ends prematurely, well before the 128Mb of configured trace buffer is filled. &amp;nbsp;Oddly, each trace seems to stop after a different number of trace records, sometimes in the 3k range, sometime in the 5k range. &amp;nbsp;When the trace stops, it halts the processor and drops me into the debugger at a return from a function, in code that I was expecting to be running. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have the "Trace Max Buffer Size" option set to 128 Mb in the target settings, and in the Trace and Profile settings I have the "Trace Buffer Size" set to 0x2000, with "Continuous" selected. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm tracing third-party code, so I'm stuck without source, but I can set a breakpoint where I want to begin trace and that works well. &amp;nbsp;The problem is that the assembly should clearly be looping for a very long time but something is happening that exits the loop and I want to know what. &amp;nbsp;Interrupts are disabled, but I was hoping a trace would catch an interrupt if that was the culprit and I was simply misunderstanding the assembly. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance for the assistance.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Jul 2017 01:37:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/PEMicro-TraceLink-trace-ends-prematurely/m-p/683258#M13985</guid>
      <dc:creator>robertgrimshaw</dc:creator>
      <dc:date>2017-07-26T01:37:31Z</dc:date>
    </item>
    <item>
      <title>Re: PEMicro TraceLink trace ends prematurely</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/PEMicro-TraceLink-trace-ends-prematurely/m-p/683259#M13986</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Robert,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this problem of the trace ending prematurely just happening with this project? Which CodeWarrior version are you using? I think that the following posts created by our colleague Erich Styger might be helpful for you:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://mcuoneclipse.com/2013/04/07/first-steps-with-the-pe-tracelink/" title="https://mcuoneclipse.com/2013/04/07/first-steps-with-the-pe-tracelink/"&gt;First Steps with the P&amp;amp;E Tracelink | MCU on Eclipse&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://mcuoneclipse.com/2013/01/13/debugging-arm-cortex-m0-hard-fault-with-mtb-trace/" title="https://mcuoneclipse.com/2013/01/13/debugging-arm-cortex-m0-hard-fault-with-mtb-trace/"&gt;Debugging ARM Cortex-M0+ Hard Fault with MTB Trace | MCU on Eclipse&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;BR /&gt;Carlos Mendoza&lt;BR /&gt;Technical Support Engineer&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Jul 2017 21:58:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/PEMicro-TraceLink-trace-ends-prematurely/m-p/683259#M13986</guid>
      <dc:creator>Carlos_Mendoza</dc:creator>
      <dc:date>2017-07-27T21:58:37Z</dc:date>
    </item>
    <item>
      <title>Re: PEMicro TraceLink trace ends prematurely</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/PEMicro-TraceLink-trace-ends-prematurely/m-p/683260#M13987</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I never did get to the bottom of this, but the premature trace stops may have been occurring when the watchdog timer was resetting the chip. &amp;nbsp;Code I added was not servicing the timer and this was causing resets. &amp;nbsp;I got no indication of that in CodeWarrior, but that may have been what was happening. &amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Aug 2017 18:37:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/PEMicro-TraceLink-trace-ends-prematurely/m-p/683260#M13987</guid>
      <dc:creator>robertgrimshaw</dc:creator>
      <dc:date>2017-08-18T18:37:54Z</dc:date>
    </item>
    <item>
      <title>Re: PEMicro TraceLink trace ends prematurely</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/PEMicro-TraceLink-trace-ends-prematurely/m-p/683261#M13988</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV class=""&gt;&lt;P&gt;Hi Robert,&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I agree with you, the watchdog reset was most likely causing the trace to stop.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;BR /&gt;Carlos Mendoza&lt;BR /&gt;Technical Support Engineer&lt;/P&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Aug 2017 19:22:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/PEMicro-TraceLink-trace-ends-prematurely/m-p/683261#M13988</guid>
      <dc:creator>Carlos_Mendoza</dc:creator>
      <dc:date>2017-08-18T19:22:44Z</dc:date>
    </item>
  </channel>
</rss>

