NOTICE: This website will be shut down in the near future. Product content has moved to nxp.com. Forum content and FAQs have been moved to community.nxp.com. We encourage you to create a user account on nxp.com to use the new community forums and access NXP microcontroller content. We greatly appreciate your contributions and look forward to seeing you at our new web location.

 

16: Target error from status-poll: Ee(02). Not connected to emulator

lpcxpresso-support's picture

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 "16: Target error from status-poll: Ee(02). Not connected to emulator" 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.

Some of the things that could cause this error include:

  • MCU going into one of the sleep modes.
  • MCU being reset, for example by a watchdog timer.
  • Faulty USB cable or bad USB port
  • Intermittent power to the target (or bad ground).
  • The MCU crystal or a PLL setting could be out of bounds affecting debug communications through the debug access port.

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.

0
Your rating: None
feedback