topic Re: Debug works only one time in MCUXpresso General

Debug works only one time

berndsirozynski — Wed, 10 Apr 2019 09:54:36 GMT

i used the MCUXpresso IDE 3.1 and the LPC-Link Board for the LPC1768

I can only Debug a Program one time.

If i change my Source and want to debug again,

i get errors. cant connect.....

To solve the problem:

a) i must close the complete IDE and Start again.

b) i must disconnect the USB from the LPC Link.

So, i have deinstalled the complete IDE and reinstalled

The same problem again.

Now, i have istalled the previous version 3.0

and all works fine.

Siro

Re: Debug works only one time

berndsirozynski — Thu, 11 Apr 2019 07:14:27 GMT

Hello again,

now i have tried to install the IDE the 3rd time. to inform you about the error mesages

if i stop my debug session
next debugging doesnt work and shows 3 error Windows:

----------------
Windows 1: Error reported by target
02: Failed on connect
Could not connect to core.
31: No connection to chips's debug port
Debugging contexte: project1 LinkServer Debug
----------------

Window2: LinkServer

17^error,msg?"Remote communication error. Target disconnected,: Success."

Reason:
Failed to execute MI command:
-target-select extended-remote | crt_emu_cm_redlink -msg-port=49873 -g -mi -2
-pLPC1768 -vendor=NXP --reset=VECTRESET -ProbeHandle=1 -CorIndex=0
--flash-driver LPC175x_6x_512.cfx --telnet 3330
Error message from debugger back end_
Remote communication error. Target disconnetcted.: Success.

----------------
Window 3: Problem Occured
'Launching project1 LinkServer Debug' has encountered a
problem

Error in final launch sequence
Failed to execute MI command:

----------------
Consolen output:
MCUXpresso IDE RedlinkMulti Driver v10.3 (Feb 7 2019 22:50:02 - crt_emu_cm_redlink build 760)
Found part description in XML file nxp_lpc17xx.xme
( 5) Remote configuration complete
Reconnected to existing link server
Connecting to probe 1 core 0 (using server started externally) gave 'Ee(42). Could not connect to core.'
Connecting to probe 1 core 0 (using server started externally) gave 'Ee(42). Could not connect to core.'
Connecting to probe 1 core 0 (using server started externally) gave 'Ee(42). Could not connect to core.'
Server OK but no connection to probe 1 core 0 (after 3 attempts) - Ee(42). Could not connect to core.
Failed on connect: Ee(42). Could not connect to core.
No connection to chip's debug port
------------------

The Button "Clean Up Debug" dont change the behavior.

a next test with another project has the same results.

i cant locate the problem

Debugging all projects with the MCUXPresso IDE Version 3.0 has no problems

Siro

Re: Debug works only one time

berndsirozynski — Thu, 11 Apr 2019 16:47:35 GMT

never give up,

so i have a complete other Windows PC and installed followed versions:
also i have a new LPC-Link and also i have a minimum Hardware only the LPC1768xx on my Board
connected with SWD

MCUXPresso V10.2.1 all work fine
MCUXpresso V10.3.1 has identical problems with debugging

so, it is better to work with an older version.

Siro

Re: Debug works only one time

berndsirozynski — Mon, 15 Apr 2019 12:20:48 GMT

Hello, i have found the problem:

The Version MCUXpresso Version V10.3.1 has only Problems with the

LPC-Link (Breakout Board from LPCXpresso Board LPC1769)

with the a New LPC-LINK 2 board, there is no problem.

Very Happy

Re: Debug works only one time

Alice_Yang — Thu, 18 Apr 2019 09:38:40 GMT

Hello Bernd,

Thanks for your sharing.

I will report it to development team.

Have a great day,
TIC

Re: Debug works only one time

kk7xo — Thu, 22 Aug 2019 18:56:47 GMT

I am having this same problem with MCUXpresso IDE 11.0 and LPC845Max board. Trying to run Multi-Timer Blinky example. If I run it under the LinkServer debugger the first time after powering up the board, it runs fine. If I terminate the debug, then restart it again, it fails the 2nd time with the same errors described above. If I unplug the board from USB and then reconnect, the debugger works again.

Re: Debug works only one time

joelmiao — Wed, 27 Nov 2019 09:03:12 GMT

Finally found that I am not the only one who is being bothered by this problem. I have three LPCXpresso boards on hand:

* LPCXpresso LPC812 REV B

* LPCXpresso LPC1200 REV B

* LPCXpresso LPC812-MAX

And I am using the lastest MCUXpresso IDE verion - v11.0.1, the debug session can only run for one time on both LPC812 and LPC1200. I have to disconnect the USB calbe and connect it again if I want to start a new debug session.

But on LPC812-MAX (with a built-in CMSIS-DAP), I didn't find this problem.

So I installed LCPXpresso IDE v8.2.2, found that debugging with LPC1200 and LPC812 works well. Seems MCUXpresso IDE has some issue or different configuration.

Re: Debug works only one time

wangwenyu — Tue, 21 Feb 2023 07:54:56 GMT

I have the same problem as yours. My MCUXpresso version is 11.6.1. feel frustrated.

Re: Debug works only one time

ErichStyger — Tue, 21 Feb 2023 08:48:12 GMT

HI @wangwenyu ,

could you share what board you are using, just in case?

Erich

Re: Debug works only one time

wangwenyu — Tue, 21 Feb 2023 14:30:48 GMT

I use MCUXpresso to connect my target board through a MCU-Link pro. The target board is a simple system on which a LPC11U68 connects a NTAG plus chip through IIC. The ROM driver is used.

It works properly at the first time when I debug this board. But, after I repower the target board, the MCUXpresso never connects with the target board again. This problem continuously occured on my 5 boards. The first time always works. Then the MCUXpresso never connects the target again.

It is highly appreciated if some body help me.

I have struggled for 4 days. No clue is found.

Re: Debug works only one time

wangwenyu — Tue, 21 Feb 2023 14:31:53 GMT

The below is my information. If you can help me, please. Thanks.

https://community.nxp.com/t5/MCUXpresso-IDE/MCUXpresso-can-t-access-the-lpc11u68-after-the-first-time-of/m-p/1602627#M8770

Re: Debug works only one time

Bariel76 — Wed, 17 Jan 2024 13:54:41 GMT

I have this problem with v11.8.1 on my Thinkpad laptop, but my desktop is fine with the same version!