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.

 

Failed on connect: Ee(37). Priority 0 connection to this core already taken

lpcxpresso-support's picture

If the error "Failed on connect: Ee(37). Priority 0 connection to this core already taken"  is seen when trying to start a debug session, this normally means that the previous debug session has not been terminated.

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.

If the debug view shows only a terminated debug session, then it is possible you have a defunct arm-none-eabi-gdb or crt_emu_cm_redlink process in your task list. Please check, and kill the arm-none-eabi-gdb process (it terminates the other) if you see it.

In addition, you may also have a default redlinkserv process in your task list - terminate this too.

If terminating these processes still does not resolve the problem, try disconnecting and reconnecting the debug probe and restarting your debug session.

0
Your rating: None
feedback