Sunday, August 20th 2017, 6:08am UTC+2

You are not logged in.

  • Login
  • Register

MatthewKyeo

Beginner

Date of registration: Jul 19th 2017

Posts: 5

1

Friday, July 21st 2017, 2:26am

Target, Connect J-Link - Error: Check connection and target interface type

Hi, I'm Matthew. I used Keil MDK-ARM 5 recently and I was trying to change to SEGGER Embedded Studio so I can create a firmware with my MacBook.

Before testing it with the MacBook, I'm using
- 64-bit Windows 10 desktop
- 64-bit SEGGER Embedded Studio V3.24 (SES, Non-Commercial License)
- J-Link Edu and J-Link Plus
- Nordic's nRF-52 PCA10040
- STM32L4 Discovery board



I receive an error message; "Failed to connect to target. No idcode detected. Please check connection and Target Interface Type"
This appears when I click Target - Connect J-Link with SES.

To begin with, while installing SES, I noticed something peculiar.
I have checked the "Install J-Link driver 6.16g" but J-Link tools (J-Flash, J-Link RTT Logger, and more) were not installed on my Windows desktop.



I thought that was the reason for the error message. So I have installed J-Link 6.16h manually.
After this manual installation, J-Link tools were installed normally and other tools were able to detect my J-Link.



However, SES still throws the error message.
What should I do to solve this to debug PCA10040 and STM32L4 Discovery board?

-Best Regards

This post has been edited 1 times, last edit by "MatthewKyeo" (Jul 21st 2017, 2:32am)


SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 67

2

Monday, July 24th 2017, 5:30pm

Hello Matthew,

Thank you for your inquiry.
Sorry for the delay in response.

Quoted

To begin with, while installing SES, I noticed something peculiar.
I have checked the "Install J-Link driver 6.16g" but J-Link tools (J-Flash, J-Link RTT Logger, and more) were not installed on my Windows desktop.

This is expected behaviour as Embedded studio gets shipped with only the JLink.DLL and USB drivers so you can start debugging out of the box without ever needing to install the complete J-Link software package.
If you want to have all other J-Link software package applications as well you have to install them manually.

Quoted

I receive an error message; "Failed to connect to target. No idcode detected. Please check connection and Target Interface Type"
This appears when I click Target - Connect J-Link with SES.


This issue is most likely related to either a bad debug interface connection or bad power supply to the target device.
What does the J-Link Commander output if you try to connect with it?
You can follow the following guide: https://wiki.segger.com/J-Link_cannot_connect_to_the_CPU
Could you post a screenshot of your full J-Link Commander output?

Best regards,
Nino

MatthewKyeo

Beginner

Date of registration: Jul 19th 2017

Posts: 5

3

Monday, August 7th 2017, 10:43am

You can follow the following guide: https://wiki.segger.com/J-Link_cannot_connect_to_the_CPU
Could you post a screenshot of your full J-Link Commander output?
Hello, sorry for the delay. I haven't received any notification after your reply.

I have observed the "USB connection O.K" message from the J-Link Commander.





For details, I have taken a video.

Other programs, such as Nordic's nRFgo studio is reading my J-Link Plus with no problem. SES is the only program that cannot connect.

The commander is reading the input. Whereas, the SES cannot connect the J-Link Plus.


What seems to be the problem?

MatthewKyeo

Beginner

Date of registration: Jul 19th 2017

Posts: 5

4

Friday, August 11th 2017, 10:46am

Hi, Nino. I have re-uploaded a demo video which uses J-Link Plus and J-Link commander.

Now, the SES says that "No Idcode detected".

Can you help me with this?