<?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>MCUXpresso IDE中的主题 Tips for speeding up debug launch?</title>
    <link>https://community.nxp.com/t5/MCUXpresso-IDE/Tips-for-speeding-up-debug-launch/m-p/1688017#M9087</link>
    <description>&lt;P&gt;I'm trying to optimize my debugging performance and nothing I do seems to get my launch time down much under 30 seconds. That's for a repeated launch with no build and no new upload.&lt;/P&gt;&lt;P&gt;I'm using a P&amp;amp;E Cyclone ACP, which is generally faster than my LPC-Link2 and MCU-Link interfaces, but it's got a lot of hang time in there that I can't account for. Throwing more PC performance at it hasn't made it any better (this is on a Core i7-13700KF with 32 GB RAM for reference) and there's no significant load showing up on the CPU or disk during this process.&lt;/P&gt;&lt;P&gt;I'm particularly interested in what's happening between the time gdb says "Continuing." and when it stops at main(). I suspect that's mostly the load that happens after the breakpoint, to populate the debug views, but if I disable the "set breakpoint at main" option then I'm not able to debug at all - it won't let me pause, continue, or anything. I have to kill the debug process and then I get:&lt;/P&gt;&lt;P&gt;warning: Exception condition detected on fd 584&lt;BR /&gt;Remote communication error. Target disconnected.: Not a directory.&lt;/P&gt;&lt;P&gt;So that's no good. The Cyclone is connected with a 100 Mbps Ethernet connection. I feel like it ought to be possible to do this all near-instantaneously when there's no new data to be programmed, but it's spending at least 20 seconds doing I don't know what.&lt;/P&gt;&lt;P&gt;I know this isn't a huge deal but shaving 20 seconds off every debug run would make my day go that much smoother.&lt;/P&gt;&lt;P&gt;Video is attached.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Scott&lt;/P&gt;</description>
    <pubDate>Fri, 14 Jul 2023 02:11:50 GMT</pubDate>
    <dc:creator>scottm</dc:creator>
    <dc:date>2023-07-14T02:11:50Z</dc:date>
    <item>
      <title>Tips for speeding up debug launch?</title>
      <link>https://community.nxp.com/t5/MCUXpresso-IDE/Tips-for-speeding-up-debug-launch/m-p/1688017#M9087</link>
      <description>&lt;P&gt;I'm trying to optimize my debugging performance and nothing I do seems to get my launch time down much under 30 seconds. That's for a repeated launch with no build and no new upload.&lt;/P&gt;&lt;P&gt;I'm using a P&amp;amp;E Cyclone ACP, which is generally faster than my LPC-Link2 and MCU-Link interfaces, but it's got a lot of hang time in there that I can't account for. Throwing more PC performance at it hasn't made it any better (this is on a Core i7-13700KF with 32 GB RAM for reference) and there's no significant load showing up on the CPU or disk during this process.&lt;/P&gt;&lt;P&gt;I'm particularly interested in what's happening between the time gdb says "Continuing." and when it stops at main(). I suspect that's mostly the load that happens after the breakpoint, to populate the debug views, but if I disable the "set breakpoint at main" option then I'm not able to debug at all - it won't let me pause, continue, or anything. I have to kill the debug process and then I get:&lt;/P&gt;&lt;P&gt;warning: Exception condition detected on fd 584&lt;BR /&gt;Remote communication error. Target disconnected.: Not a directory.&lt;/P&gt;&lt;P&gt;So that's no good. The Cyclone is connected with a 100 Mbps Ethernet connection. I feel like it ought to be possible to do this all near-instantaneously when there's no new data to be programmed, but it's spending at least 20 seconds doing I don't know what.&lt;/P&gt;&lt;P&gt;I know this isn't a huge deal but shaving 20 seconds off every debug run would make my day go that much smoother.&lt;/P&gt;&lt;P&gt;Video is attached.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Scott&lt;/P&gt;</description>
      <pubDate>Fri, 14 Jul 2023 02:11:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-IDE/Tips-for-speeding-up-debug-launch/m-p/1688017#M9087</guid>
      <dc:creator>scottm</dc:creator>
      <dc:date>2023-07-14T02:11:50Z</dc:date>
    </item>
    <item>
      <title>Re: Tips for speeding up debug launch?</title>
      <link>https://community.nxp.com/t5/MCUXpresso-IDE/Tips-for-speeding-up-debug-launch/m-p/1688266#M9089</link>
      <description>&lt;P&gt;Thanks for the sharing.&lt;/P&gt;
&lt;P&gt;We will feed it back to NXP person in charge for tool performance improvement.&lt;/P&gt;
&lt;P&gt;Best Regards&lt;/P&gt;
&lt;P&gt;Jun Zhang&lt;/P&gt;</description>
      <pubDate>Fri, 14 Jul 2023 08:18:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-IDE/Tips-for-speeding-up-debug-launch/m-p/1688266#M9089</guid>
      <dc:creator>ZhangJennie</dc:creator>
      <dc:date>2023-07-14T08:18:46Z</dc:date>
    </item>
  </channel>
</rss>

