<?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: Problem debug MCUxpresso in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Problem-debug-MCUxpresso/m-p/1583017#M200152</link>
    <description>&lt;P&gt;Anyone have any ideas on what could be causing this anomalous behavior?&lt;/P&gt;</description>
    <pubDate>Mon, 16 Jan 2023 08:45:26 GMT</pubDate>
    <dc:creator>michelet1</dc:creator>
    <dc:date>2023-01-16T08:45:26Z</dc:date>
    <item>
      <title>Problem debug MCUxpresso</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Problem-debug-MCUxpresso/m-p/1581633#M199995</link>
      <description>&lt;P&gt;Hello everybody,&lt;/P&gt;&lt;P&gt;Lately a strange error came out using MCUxpresso 11.6.1[build 8255]&lt;/P&gt;&lt;P&gt;The error happens when i run debugging using LPC-LINK2.&lt;/P&gt;&lt;P&gt;error is as follow:&lt;/P&gt;&lt;P&gt;/mnt/workspace/workspace/GCC-10-pipeline/jenkins-GCC-10-pipeline-338_20211018_1634516203/src/gdb/gdb/utils.c:671: internal-error: virtual memory exhausted: can't allocate 4064 bytes.&lt;BR /&gt;A problem internal to GDB has been detected,&lt;BR /&gt;further debugging may prove unreliable.&lt;BR /&gt;Quit this debugging session? (y or n) [answered Y; input not from terminal]&lt;/P&gt;&lt;P&gt;This is a bug, please report it. For instructions, see:&lt;BR /&gt;&amp;lt;&lt;A href="https://www.gnu.org/software/gdb/bugs/" target="_blank"&gt;https://www.gnu.org/software/gdb/bugs/&lt;/A&gt;&amp;gt;.&lt;/P&gt;&lt;P&gt;/mnt/workspace/workspace/GCC-10-pipeline/jenkins-GCC-10-pipeline-338_20211018_1634516203/src/gdb/gdb/utils.c:671: internal-error: virtual memory exhausted: can't allocate 4064 bytes.&lt;BR /&gt;A problem internal to GDB has been detected,&lt;BR /&gt;further debugging may prove unreliable.&lt;BR /&gt;Create a core file of GDB? (y or n) [answered Y; input not from terminal]&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I can't figure out how to deal with this problem, i didn't find any possible solution on NXP doc.&lt;/P&gt;&lt;P&gt;Thanks in advance to anyone who can help me&lt;/P&gt;</description>
      <pubDate>Thu, 12 Jan 2023 09:59:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Problem-debug-MCUxpresso/m-p/1581633#M199995</guid>
      <dc:creator>michelet1</dc:creator>
      <dc:date>2023-01-12T09:59:10Z</dc:date>
    </item>
    <item>
      <title>Re: Problem debug MCUxpresso</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Problem-debug-MCUxpresso/m-p/1583017#M200152</link>
      <description>&lt;P&gt;Anyone have any ideas on what could be causing this anomalous behavior?&lt;/P&gt;</description>
      <pubDate>Mon, 16 Jan 2023 08:45:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Problem-debug-MCUxpresso/m-p/1583017#M200152</guid>
      <dc:creator>michelet1</dc:creator>
      <dc:date>2023-01-16T08:45:26Z</dc:date>
    </item>
    <item>
      <title>Re: Problem debug MCUxpresso</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Problem-debug-MCUxpresso/m-p/1584142#M200269</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;I suggest you try to update the firmware, I find this document maybe could help you with the steps.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.nxp.com/docs/en/supporting-information/Debug_Probe_Firmware_Programming.pdf" target="_blank"&gt;LPC-Link2 Debug Probe Firmware Programming (nxp.com)&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Best regards,&lt;BR /&gt;Pavel&lt;/P&gt;</description>
      <pubDate>Tue, 17 Jan 2023 18:39:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Problem-debug-MCUxpresso/m-p/1584142#M200269</guid>
      <dc:creator>Pavel_Hernandez</dc:creator>
      <dc:date>2023-01-17T18:39:10Z</dc:date>
    </item>
  </channel>
</rss>

