Hello,

I meet the same problem with this thread.
forum.segger.com/index.php/Thr…cannot-connect-to-target/

I'm trying to debug FRDM-K64F host msd command bm project from NXP SDK with a JLink EDU and a U-disk.
There are two USB ports, SDA USB and K64F USB.
Generally, I connect the U-disk with K64F USB port and power cable with SDA USB. It works when I debug with LinkServer option in the MCUXpresso IDE.

However, it's different when debug with JLink EDU.

If the power cable linked to the SDA USB and U-disk linked to K64F USB, the MCUXpresso will show an error that couldn't connect to the target when debugging with JLink EDU as the picture shown.
[img]https://community.nxp.com/servlet/JiveServlet/downloadImage/2-1353774-327858/pastedImage_1.png[/img]

If power cable linked to the K64F USB and U-disk linked to SDA USB, JLink Edu works and could debug the project. However, the demo project couldn't detect the U-disk and no attached eventBit flag is set.

Could you please help to explain this and how could I debug the USB demo project with JLink Edu?
Besides, I know the other debug option LinkServer works. But I have to use JLink for future development.


Thanks.

Conclusion
Changing to segger openSDA firmware will works.

How
After testing and searching, I guess it should be the problem of openSDA firmware. I get this idea from the link Cannot debug FDRM-K64F via J-link.



It shows I need to power the board with K64F USB port when using external JLink EDU if using mbed/CMSIS-DAP which is come as default configuration of the board.

So I think I need another openSDA firmware which supports to power the board with SDA USB port. I know that segger provides another openSDA firmware as the link segger.com/products/debug-prob…r-j-links/opensda-sda-v2/ . As the description, I think it should support it.

And I follow another tutorial on how to download the segger openSDA as the link Install OpenSDAv2 Firmware on FRDM-K64F Board- MATLAB & Simulink . Please pay attention to the second step that you need to press the reset button firstly before connect to PC.

Finally, it works! The power cable is connected to SDA USB port and U-disk to K64F USB port.

Still confused
I still do not know the details about these two openSDA firmware and why it acts like this. If anyone knows and be likely to share it. Really appreciate it.