<?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: Debug Speed? in LPCXpresso IDE</title>
    <link>https://community.nxp.com/t5/LPCXpresso-IDE/Debug-Speed/m-p/557102#M14441</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by CodeRedSupport on Fri Jun 25 02:25:45 MST 2010&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Things that affect the single stepping speed include:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- the number of peripherals you have displayed&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- the number of memory views you have open&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- (to a lesser extent) the number of local/globals shown in the&amp;nbsp; variables and expression windows&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;After every step, all of this information has to be re-fetched from the&amp;nbsp; target (as well as the core registers). &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You will definitely see an improvement by using Red Probe, which uses a&amp;nbsp; dedicated chip to handle the debug interface, whereas for LPC-Link (and&amp;nbsp; RDB1768v2), this is done in software on the host.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 15 Jun 2016 22:12:57 GMT</pubDate>
    <dc:creator>lpcware</dc:creator>
    <dc:date>2016-06-15T22:12:57Z</dc:date>
    <item>
      <title>Debug Speed?</title>
      <link>https://community.nxp.com/t5/LPCXpresso-IDE/Debug-Speed/m-p/557101#M14440</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by Mark_O on Fri Jun 25 01:48:05 MST 2010&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;We're using the LPCXpresso/Red Suite with the RDB1768v2 development kit to evaluate the development environment. We've noticed that single-stepping in the debugger is quite slow, even though it was improved in one of the recent releases (it used to be much worse).&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Currently it still takes about 1 second to step a single instruction, on fairly fast dev. systems. This is significantly slower than the other debug environments we have experience with, including those based on Eclipse.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Questions are:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;1) why is this as slow as it is?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2) can/will the speed be improved in the future?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;3) is there anything we can do to optimize this in our configuration settings?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;4) would alternate hardware debug interfaces offer better speed?&amp;nbsp; (e.g the Red Probe, or LPCLink)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- Mark&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 22:12:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPCXpresso-IDE/Debug-Speed/m-p/557101#M14440</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T22:12:56Z</dc:date>
    </item>
    <item>
      <title>Re: Debug Speed?</title>
      <link>https://community.nxp.com/t5/LPCXpresso-IDE/Debug-Speed/m-p/557102#M14441</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by CodeRedSupport on Fri Jun 25 02:25:45 MST 2010&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Things that affect the single stepping speed include:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- the number of peripherals you have displayed&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- the number of memory views you have open&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- (to a lesser extent) the number of local/globals shown in the&amp;nbsp; variables and expression windows&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;After every step, all of this information has to be re-fetched from the&amp;nbsp; target (as well as the core registers). &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You will definitely see an improvement by using Red Probe, which uses a&amp;nbsp; dedicated chip to handle the debug interface, whereas for LPC-Link (and&amp;nbsp; RDB1768v2), this is done in software on the host.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 22:12:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPCXpresso-IDE/Debug-Speed/m-p/557102#M14441</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T22:12:57Z</dc:date>
    </item>
    <item>
      <title>Re: Debug Speed?</title>
      <link>https://community.nxp.com/t5/LPCXpresso-IDE/Debug-Speed/m-p/557103#M14442</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by Mark_O on Fri Jun 25 14:25:02 MST 2010&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks for the quick and informative response.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- Mark&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 22:12:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPCXpresso-IDE/Debug-Speed/m-p/557103#M14442</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T22:12:57Z</dc:date>
    </item>
  </channel>
</rss>

