Saturday, November 25th 2017, 10:35am UTC+1

You are not logged in.

  • Login
  • Register

Dear visitor, welcome to SEGGER Forum. If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

MatthewKyeo

Beginner

Date of registration: Jul 19th 2017

Posts: 37

1

Friday, July 21st 2017, 2:26am

[SOLVED] 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: 352

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: 37

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: 37

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?

MatthewKyeo

Beginner

Date of registration: Jul 19th 2017

Posts: 37

5

Monday, August 21st 2017, 2:40am

Uploaded JLink Log

Hi, Nino. This is the log result.

Source code

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
T277C 000:000 SEGGER J-Link V6.18 Log File (0000ms, 0000ms total)
T277C 000:000 DLL Compiled: Aug 3 2017 16:21:33 (0000ms, 0000ms total)
T277C 000:000 Logging started @ 2017-08-21 09:40 (0000ms, 0000ms total)
T277C 000:000 JLINK_EMU_SelectByUSBSN(SerialNo = 0) returns 0xFFFFFFFF (0000ms, 0000ms total)
T277C 000:000 JLINK_ExecCommand("EnableAutoUpdateFW", ...). returns 0x00 (0000ms, 0000ms total)
T277C 000:000 JLINK_OpenEx(...)
Firmware: J-Link V10 compiled Jul 28 2017 08:59:01
Hardware: V10.10
S/N: 6XXXXXXXX
Feature(s): RDI, FlashBP, FlashDL, JFlash, GDB

TELNET listener socket opened on port 19021WEBSRV 
Webserver running on local port 19080 returns O.K. (0011ms, 0011ms total)
T277C 000:011 JLINK_GetEmuCaps() returns 0xB9FF7BBF (0000ms, 0011ms total)
T277C 000:011 JLINK_GetFirmwareString(...) (0000ms, 0011ms total)
T277C 000:011 JLINK_GetDLLVersion() returns 61800 (0000ms, 0011ms total)
T277C 000:011 JLINK_GetHardwareVersion() returns 0x18A88 (0000ms, 0011ms total)
T277C 000:011 JLINK_GetHWStatus(...) returns 0x00 (0001ms, 0012ms total)
T277C 000:012 JLINK_ExecCommand("ProjectFile = "C:/Users/USERNAME/Documents/SEGGER Embedded Studio Projects/Hello/Hello_Debug.jlink"", ...). returns 0x00 (0153ms, 0165ms total)
T277C 000:165 JLINK_DEVICE_GetIndex(sDeviceName = Cortex-M3) returns 13 (0000ms, 0165ms total)
T277C 000:165 JLINK_ExecCommand("device = Cortex-M3", ...). Device "CORTEX-M3" selected. returns 0x00 (0002ms, 0167ms total)
T277C 000:167 JLINK_DEVICE_GetIndex(sDeviceName = Cortex-M3) returns 13 (0000ms, 0167ms total)
T277C 000:167 JLINK_DEVICE_G





This part; JLINK_EMU_SelectByUSBSN(SerialNo = 0) returns 0xFFFFFFFF (0000ms, 0001ms total)


I think this has a relationship with the "no idcode" error.


Can you help me with this?

-Best Regards

This post has been edited 3 times, last edit by "MatthewKyeo" (Aug 21st 2017, 2:45am)


SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 352

6

Monday, August 21st 2017, 3:39pm

Hi Matthew,

Sorry for the delay in response, it is currently vacation time and many new projects have come in making it quite a busy summer.

Thank you for providing me with additional setup information, especially the J-Link Commander output is crucial here.
It reads "VTref = 0.000 V" which indicates that the target is not powered and/or the debug probe gets no information about the target power and thus does not know with what voltage the
debug pins should be driven. This is a safety measure to make sure our debug probes do not ever damage the target hardware.
To be able to connect to the target make sure that on PIN 1 (VTref) of the debug interface is connected to the target devices supply voltage.

More information about a proper interface connection can be found here: https://www.segger.com/products/debug-pr…ce-description/

Best regards,
Nino

MatthewKyeo

Beginner

Date of registration: Jul 19th 2017

Posts: 37

7

Tuesday, August 22nd 2017, 2:59am

Sorry for the delay in response, it is currently vacation time and many new projects have come in making it quite a busy summer.

Thank you for providing me with additional setup information, especially the J-Link Commander output is crucial here.
It reads "VTref = 0.000 V" which indicates that the target is not powered and/or the debug probe gets no information about the target power and thus does not know with what voltage the
debug pins should be driven.
Hi, Nino. I apologize for pushing.

Thanks for solving this. As you have mentioned, after powering my board, the SES shows "CortexMx on J-link" at the bottom of the screen.



Good luck on your summer projects!

-Best Regards, Matthew

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 352

8

Tuesday, August 22nd 2017, 9:52am

Hi Matthew,

You are welcome.
I will consider this thread as closed then.

Best regards,
Nino