topic 16: Target error from status-poll: Ee(02). Not connected to emulator in LPCXpresso IDE FAQs https://community.nxp.com/t5/LPCXpresso-IDE-FAQs/16-Target-error-from-status-poll-Ee-02-Not-connected-to-emulator/m-p/467709#M8 <HTML><HEAD></HEAD><BODY><P>During a debug session, whilst your target is executing , the debug tools will poll the target to determine whether it has halted on a breakpoint or event. A "<STRONG>16: Target error from status-poll: Ee(02). Not connected to emulator</STRONG>" error is returned whenever the debug tools cannot get the present target state. In this case, the debug connection to your MCU is considered offline.</P><P></P><P>Some of the things that could cause this error include:</P><UL><LI>MCU going into one of the sleep modes.</LI><LI>MCU being reset, for example by a watchdog timer.</LI><LI>Faulty USB cable or bad USB port</LI><LI>Intermittent power to the target (or bad ground).</LI><LI>The MCU crystal or a PLL setting could be out of bounds affecting debug communications through the debug access port.</LI></UL><P></P><P>If you are connecting to the target using a Red Probe+ (but NOT using an LPC-Link), then in the Project Debug Configuration, you can specify a reduced wire speed (i.e. "Maximum wire speed). The default is typically 3 MHz, or 3000 KHz. Setting this value to a lower number, such as 1000 KHz (1 MHz), can sometimes improve matters - though this depends on the actual cause of the status-poll error.</P></BODY></HTML> Thu, 31 Mar 2016 15:28:29 GMT lpcware-support 2016-03-31T15:28:29Z 16: Target error from status-poll: Ee(02). Not connected to emulator https://community.nxp.com/t5/LPCXpresso-IDE-FAQs/16-Target-error-from-status-poll-Ee-02-Not-connected-to-emulator/m-p/467709#M8 <HTML><HEAD></HEAD><BODY><P>During a debug session, whilst your target is executing , the debug tools will poll the target to determine whether it has halted on a breakpoint or event. A "<STRONG>16: Target error from status-poll: Ee(02). Not connected to emulator</STRONG>" error is returned whenever the debug tools cannot get the present target state. In this case, the debug connection to your MCU is considered offline.</P><P></P><P>Some of the things that could cause this error include:</P><UL><LI>MCU going into one of the sleep modes.</LI><LI>MCU being reset, for example by a watchdog timer.</LI><LI>Faulty USB cable or bad USB port</LI><LI>Intermittent power to the target (or bad ground).</LI><LI>The MCU crystal or a PLL setting could be out of bounds affecting debug communications through the debug access port.</LI></UL><P></P><P>If you are connecting to the target using a Red Probe+ (but NOT using an LPC-Link), then in the Project Debug Configuration, you can specify a reduced wire speed (i.e. "Maximum wire speed). The default is typically 3 MHz, or 3000 KHz. Setting this value to a lower number, such as 1000 KHz (1 MHz), can sometimes improve matters - though this depends on the actual cause of the status-poll error.</P></BODY></HTML> Thu, 31 Mar 2016 15:28:29 GMT https://community.nxp.com/t5/LPCXpresso-IDE-FAQs/16-Target-error-from-status-poll-Ee-02-Not-connected-to-emulator/m-p/467709#M8 lpcware-support 2016-03-31T15:28:29Z