When using mculink, debugging can find the probe, but there is an exception when selected

[Yu_]

When I completed the steps outlined in the MCU-LINK installation guide and proceeded to use MCU-LINK in conjunction with MCUXpresso IDE, I encountered an issue.

After connecting the computer to MCU-LINK, I can debug and the probe is recognized. However, after I select it, it keeps reconnecting and pops up this exception. What could be the reason for this? Could you please help me understand? Thank you!

[Yu_]

What is circled in red is that it would be on after normal burning, and the blue part would be on after pressing. Now D8, D9, D10 and D11 are not on, and they can't be burned in.

[Yu_]

The following figure is the error that pops up after clicking Debug.

[Yu_]

The picture shows my connection status

 

[carlos_o]

Hi @Yu_ 

Thanks for your question

Are you using a custom board or the MIMXRT685-EVK?

Are you using an external power supply for the board? or are you using the MCU-Link?

Another thing to mention is the Additional information included at the MCU-Link User Manual

[MCU-Link Base standalone Debug Probe, Page 7]

[Yu_]

I carefully checked my board again, and the chip on it is RT685SFFOB
I use 1.8V power supply for it

[Yu_]

Hello @carlos_o
After reading your reply
Yes, I am using the MIMXRT685-EVK.
I provide independent power supply for the board, and connect the MCU-LINK to the computer via USB. Then, I connect my board using the target debug connector.
For the SWD target connection header, I only use SWDIO, SWO, and SWCLK.
After that, the situation shown in the above figure will occu.

[carlos_o]

Hi @Yu_

Please could you try to connect directly the MCU-LINK connector to the SWD 10 pin connector on the RT685EVK board.

Let me know if this solves your issue.

[Yu_]

Hello@carlos_o
I 'm sorry. I regret to reply you that I do not have an RT685EVK board.
The chip I use on my board is only the RT685SFFOB. Following your instructions, I connected the RST pin to PIN10 of the MCU-Link on my board, but the issue remains the same.
I'd like to briefly describe the current situation. I just used the RT685SFFOB chip on my board. Now I need to carry out a chip test on it to verify whether its function is normal. If it is normal, I'll carry out my own two development.
The problem is that when I connect the muc-link to the computer, and then connect my board to the mcu-link, the above problems will occur in Debug.
I want to know what causes the above problems and how to solve them.
I'm looking forward to your answers.

[carlos_o]

Hi @Yu_ 

Apologies for the late reply

Thank you for clarifying your setup

It seems that the issue is that the RT685 Board you are using are not being recognized by the MCU Link. Could you confirm that both boards are sharing a common ground reference? 

Those error you are facing appear when you start debugging or during running the debug? 

[Yu_]

Hello@carlos_o
I'm glad to see your reply.
I didn't connect MCU-LINK to the GND of the board before. After reading your reply, I connected SWDIO, SWCLK and SWO and then connected their GND.
But it's a pity that the result is still the same as before.
This error is after I click Debug, I see the probe, and it appears after I select the MCU probe, and it will Retrying once.

[carlos_o]

Hi @Yu_ 

Please try to connect all the 10 connectors of the MCU-LINK to the corresponding signal on your RT600 board 

VREF is needed to the proper work of the level shifters at the MCU-LINK

IF_DETECT is needed to go to gnd of your board to detect the board. 

Please try to connect all the 10 pins if possible 

[Yu_]

Hi@carlos_o
I'm sorry it took so long to get back to you.
Before, I tried to connect the interface on my board, but the error was still displayed.
Recently I got the development board of RT685. At the beginning, I used the data cable to connect J5 to the computer, and then successfully burned the program of HelloWorld. D8 and D11 on the board are in constant state, and D2 flickers.
Later, I went to check my board. The above interface is type-C, and the pins are DM and DP, and A5, B8 and VBUS, GND. I don't know why the computer is connected through the type-C port. The computer can't find any external devices, and it doesn't show the access of unknown devices.
Today, when testing the development board, I also encountered a very strange problem.
Originally, the development board was intact, and I burned the case code to enable normal burning. But when I first failed to burn my board, I changed the data line and then burned the development board, and the development board also had the initial problem of this post.
Moreover, after connecting the J5 port, only the D2 light is flashing, and D8 and D11 are not on.
Now it can't be burned in, and it always shows "unable to connect wire for probe index 1. Error: Wire Ack Fault - target connected?"
What's the reason for that? Is the board broken?

[carlos_o]

Hi @Yu_ 

The D2 flashing means that the on-board debugger is running. 

The D11 is a power on indicator that you could see at the schematic of the board.

The D8 is blue led that is controlled by P0_26

Did you modify the board in any way? or did you move any of the mini jumper default position?

[Yu_]

Hi@carlos_o
I didn't modify the development board, and the jumper position has also been restored to the default position, but the D11 of the development board is still not on.
After connecting the computer through LINK USB, the Device manager displays the new USB "Composite device", but the development board still can't burn the example code, and it still displays "Unable to connect wire for probe index 1."

[carlos_o]

Hi @Yu_ 

If the D11 is not on, there is a power distribution problem at the board. The debugger is still working that is why you detect the board when connected the USB.