<?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 Failed on connect: Ee(37). Priority 0 connection to this core already taken in LPCXpresso IDE FAQs</title>
    <link>https://community.nxp.com/t5/LPCXpresso-IDE-FAQs/Failed-on-connect-Ee-37-Priority-0-connection-to-this-core/m-p/469741#M48</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If the error "&lt;STRONG&gt;&lt;TT&gt;Failed on connect: Ee(37). Priority 0 connection to this core already taken&lt;/TT&gt;&lt;/STRONG&gt;"&amp;nbsp; is seen when trying to start a debug session, this normally means that the previous debug session has not been terminated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check the debug view and make sure that you do not still have a debug session still running. If you do, terminate it, then try launching your new debug session again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the debug view shows only a terminated debug session, then it is possible you have a defunct &lt;STRONG&gt;arm-none-eabi-gdb&lt;/STRONG&gt; or &lt;STRONG&gt;crt_emu_cm_redlink&lt;/STRONG&gt; process in your task list. Please check, and kill the &lt;STRONG&gt;arm-none-eabi-gdbprocess&lt;/STRONG&gt; (it terminates the other) if you see it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In addition, you may also have a default &lt;STRONG&gt;redlinkserv&lt;/STRONG&gt; process in your task list - terminate this too.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If terminating these processes still does not resolve the problem, try disconnecting and reconnecting the debug probe and restarting your debug session.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 31 Mar 2016 18:42:58 GMT</pubDate>
    <dc:creator>lpcware-support</dc:creator>
    <dc:date>2016-03-31T18:42:58Z</dc:date>
    <item>
      <title>Failed on connect: Ee(37). Priority 0 connection to this core already taken</title>
      <link>https://community.nxp.com/t5/LPCXpresso-IDE-FAQs/Failed-on-connect-Ee-37-Priority-0-connection-to-this-core/m-p/469741#M48</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If the error "&lt;STRONG&gt;&lt;TT&gt;Failed on connect: Ee(37). Priority 0 connection to this core already taken&lt;/TT&gt;&lt;/STRONG&gt;"&amp;nbsp; is seen when trying to start a debug session, this normally means that the previous debug session has not been terminated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check the debug view and make sure that you do not still have a debug session still running. If you do, terminate it, then try launching your new debug session again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the debug view shows only a terminated debug session, then it is possible you have a defunct &lt;STRONG&gt;arm-none-eabi-gdb&lt;/STRONG&gt; or &lt;STRONG&gt;crt_emu_cm_redlink&lt;/STRONG&gt; process in your task list. Please check, and kill the &lt;STRONG&gt;arm-none-eabi-gdbprocess&lt;/STRONG&gt; (it terminates the other) if you see it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In addition, you may also have a default &lt;STRONG&gt;redlinkserv&lt;/STRONG&gt; process in your task list - terminate this too.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If terminating these processes still does not resolve the problem, try disconnecting and reconnecting the debug probe and restarting your debug session.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Mar 2016 18:42:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPCXpresso-IDE-FAQs/Failed-on-connect-Ee-37-Priority-0-connection-to-this-core/m-p/469741#M48</guid>
      <dc:creator>lpcware-support</dc:creator>
      <dc:date>2016-03-31T18:42:58Z</dc:date>
    </item>
  </channel>
</rss>

