<?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: OM13085 module debug locks module under MCUXpressoIDE_10.1.1_606 on W7 Platform in MCUXpresso IDE</title>
    <link>https://community.nxp.com/t5/MCUXpresso-IDE/OM13085-module-debug-locks-module-under-MCUXpressoIDE-10-1-1-606/m-p/748617#M1645</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check in Task Manager that none of the debug executables are still running (arm-none-eabi-gdb, crt_emu_cm_redlink, redlinkserv).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then power your board down, and try turning it back on with ISP pulled - as described in :&amp;nbsp;&lt;A href="https://community.nxp.com/thread/389112"&gt;Regaining debug access to target MCU&lt;/A&gt;&amp;nbsp;.&amp;nbsp;Then do a mass erase using the GUI Flash Programmer tool built into the IDE - to overwrite whatever changes you made to the application that is in the flash.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now try debugging one of the standard examples again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note : you may also wish to check&amp;nbsp;that you have the latest CMSIS-DAP firmware installed for the LPC11U35 debug probe circuitry on your board :&amp;nbsp;&lt;A href="https://community.nxp.com/community/lpc/blog/2017/09/11/new-debug-probe-firmware-drivers-for-max-boards"&gt;https://community.nxp.com/community/lpc/blog/2017/09/11/new-debug-probe-firmware-drivers-for-max-boards&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;MCUXpresso IDE Support&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 14 May 2018 12:42:46 GMT</pubDate>
    <dc:creator>lpcxpresso_supp</dc:creator>
    <dc:date>2018-05-14T12:42:46Z</dc:date>
    <item>
      <title>OM13085 module debug locks module under MCUXpressoIDE_10.1.1_606 on W7 Platform</title>
      <link>https://community.nxp.com/t5/MCUXpresso-IDE/OM13085-module-debug-locks-module-under-MCUXpressoIDE-10-1-1-606/m-p/748616#M1644</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I recently purchase an OM13085 module which I've been trying to get started on.&amp;nbsp; I installed mCUXpressoIDE_10.1.1_606 and started with the blinky example for the LCU1769 chip that is on the board.&amp;nbsp; I chose to use the default debug probe offered by the IDE when I started the session.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The debugger worked initially, but when I stopped debugging and went back to make some changes things went wrong.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The IDE reported that it couldn't restart debugging because there was an active debug session already, and I could not find any way to halt the debug session.&amp;nbsp; In frustration I replugged the usb to cycle power on the board, and it had no effect.&amp;nbsp; I couldn't find any references to people having similar problems on this module.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I tried to use the MBED system, but the module seems hung up.&amp;nbsp; MBED reports "SWD Error" and is hung.&amp;nbsp; Looking around at the project settings I cannot find anything that will break the deadlock.&amp;nbsp; The one LED that was lit during the stopped debug session is just hung up, and the module is unresponsive.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone advise what I should do at this point?&amp;nbsp; Is this a problem with the IDE?&amp;nbsp; Am I missing a setting somewhere in the IDE that can restart / close the debug session?&amp;nbsp; (I have tried a few settings under the debug configuration and nothing works.&amp;nbsp; For all intent and purposes the board is locked up.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rich&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 13 May 2018 09:32:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-IDE/OM13085-module-debug-locks-module-under-MCUXpressoIDE-10-1-1-606/m-p/748616#M1644</guid>
      <dc:creator>rnk2014</dc:creator>
      <dc:date>2018-05-13T09:32:02Z</dc:date>
    </item>
    <item>
      <title>Re: OM13085 module debug locks module under MCUXpressoIDE_10.1.1_606 on W7 Platform</title>
      <link>https://community.nxp.com/t5/MCUXpresso-IDE/OM13085-module-debug-locks-module-under-MCUXpressoIDE-10-1-1-606/m-p/748617#M1645</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check in Task Manager that none of the debug executables are still running (arm-none-eabi-gdb, crt_emu_cm_redlink, redlinkserv).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then power your board down, and try turning it back on with ISP pulled - as described in :&amp;nbsp;&lt;A href="https://community.nxp.com/thread/389112"&gt;Regaining debug access to target MCU&lt;/A&gt;&amp;nbsp;.&amp;nbsp;Then do a mass erase using the GUI Flash Programmer tool built into the IDE - to overwrite whatever changes you made to the application that is in the flash.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now try debugging one of the standard examples again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note : you may also wish to check&amp;nbsp;that you have the latest CMSIS-DAP firmware installed for the LPC11U35 debug probe circuitry on your board :&amp;nbsp;&lt;A href="https://community.nxp.com/community/lpc/blog/2017/09/11/new-debug-probe-firmware-drivers-for-max-boards"&gt;https://community.nxp.com/community/lpc/blog/2017/09/11/new-debug-probe-firmware-drivers-for-max-boards&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;MCUXpresso IDE Support&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 May 2018 12:42:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-IDE/OM13085-module-debug-locks-module-under-MCUXpressoIDE-10-1-1-606/m-p/748617#M1645</guid>
      <dc:creator>lpcxpresso_supp</dc:creator>
      <dc:date>2018-05-14T12:42:46Z</dc:date>
    </item>
  </channel>
</rss>

