Monday, December 11th 2017, 4:59am UTC+1

You are not logged in.

  • Login
  • Register

hrb

Beginner

Date of registration: Sep 3rd 2015

Posts: 13

1

Wednesday, November 29th 2017, 2:32pm

[SOLVED] J-Link Ver6.22a not working with LPC4370 anylonger

HI there,

i started to have problem connecting to a LPC4370 with the newest firmware on my J-Link plus. J-Link commander and J-Flash both said that they cannot connect to the target. I downgraded the firmware on my J-Link plus to the one from J-Link 6.20i.
Now i can work fine again with my LPC4370. However, J-Flash freezes for 5sek before it starts programming the QSPI flash. This is why i updated today. But then nothing worked anymore.

Does anyone else have a similar problem ?

Best,
Hans

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 430

2

Wednesday, November 29th 2017, 4:27pm

Hello Hans,

Thank you for your inquiry.
Such an issue is not known to us.
Are you using an eval board or custom hardware?
Could you try connecting with the J-Link Commander and post a screenshot of the output for the working case and not working case?
How is explained in the following article.
https://wiki.segger.com/J-Link_cannot_connect_to_the_CPU

Best regards,
Nino

hrb

Beginner

Date of registration: Sep 3rd 2015

Posts: 13

3

Thursday, November 30th 2017, 2:13pm

Hi there,

in version 6.22a it just says: "could not connect to target" I attached the output of j-link commander in both cases. I use a custome hardware. But i have this for quite a while and i didn't had issues with my segger over quite some versions.
In 6.20i it happens sometimes that the connection via usb times out the first time. I don't know what this is and its not always the case. But still i can connect and do everything :)

Best,
Hans
hrb has attached the following files:
  • 6.20i.txt (1.95 kB - 15 times downloaded - Last download: Yesterday, 12:06am)
  • 6.22a.txt (1.04 kB - 13 times downloaded - Last download: Yesterday, 12:14am)

This post has been edited 1 times, last edit by "hrb" (Nov 30th 2017, 2:14pm)


SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 430

4

Thursday, November 30th 2017, 2:24pm

Hello Hans,

How are you powering your target device?
Are you using J-Link for that?
Because from the log files with the 6.20i you get 3.2V and with 6.22a 0.2 V.
If so please check if "power on" is enabled when using V6.22a.

Best regards,
Nino

hrb

Beginner

Date of registration: Sep 3rd 2015

Posts: 13

5

Monday, December 4th 2017, 9:51am

Hi Nino,

i always power the board via usb or an external power supply. I never used the J-Link to power the Target.
I can check if this makes a difference.

Best,
Hans

hrb

Beginner

Date of registration: Sep 3rd 2015

Posts: 13

6

Monday, December 4th 2017, 10:08am

Hi again,

i quickly tested it. In 6.22a the jlink control panel shows, that my device has not enough power. Just 0.2V. But the device is correctly powered. Even if i turn on the powering from jlink it still shows 0.2V. But this basically shouldn't have an effect ?

Best,
Hans

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 430

7

Monday, December 4th 2017, 10:22am

Hello Hans,

If you power the device externally then "power on" will make no difference.
Can you measure the VTref Pin (Pin 1) with a multimeter and check what voltage you read there?
Is it the same voltage J-Link is reading?

Best regards,
Nino

hrb

Beginner

Date of registration: Sep 3rd 2015

Posts: 13

8

Monday, December 4th 2017, 11:32am

Hello Nino,

the VTref pin is always 3.25V when i measure it with a multimeter with both J-Link versions. But version 6.22a shows 0.2V in the readings. Seems like a small bug to me :)

Best,
Hans

This post has been edited 1 times, last edit by "hrb" (Dec 4th 2017, 11:34am)


SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 430

9

Monday, December 4th 2017, 11:53am

Hello Hans,

Unfortunately not reproducible here so I doubt it is a software bug.
Just tested it with a J-Link Plus V10 and J-Link Software V6.22a on Windows 7 and the commander always showed the correct voltage that gets applied to pin one (tried several values between 0-5 V and the 3.25 V like in your example).

What OS are you using J-Link on? Is it directly connected to the PC or over a USB hub?
Could you try another PC and see if the issue persists?
Could you please provide a screenshot of the commander output with the 0.2V displayed?

Best regards,
Nino

hrb

Beginner

Date of registration: Sep 3rd 2015

Posts: 13

10

Monday, December 4th 2017, 5:26pm

Hi Nino,

strange behaviour. I use Win10 1709. I connect my j-link plus v10 via an usb hub but this was never a problem. I also tested both hub/pc with 6.22a and it didn't worked. With 6.20i it works.
I can try to use another pc tomorrow and make a screenshot of the commander.

Best,
Hans

hrb

Beginner

Date of registration: Sep 3rd 2015

Posts: 13

11

Wednesday, December 6th 2017, 11:01am

Hi Nino,

im sorry that it took me so long but i'm very busy at the moment. I didn't checked on another PC so far but i made some screenshots of my jlink with the different firmwares on the jlink plus. I also connected my jlink directly to my laptop this time.
As you can see, whenever i have the 22a firmware installed on my jlink the voltage is not correctly measured.

Best,
Hans
hrb has attached the following images:
  • jlink20i_firmware20i.png
  • jlink20i_firmware22a.png
  • jlink22a_firmware20i.png
  • jlink22a_firmware22a.png

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 430

12

Wednesday, December 6th 2017, 12:08pm

Hello Hans,

Thank you for providing the screenshots.
I tried to reproduce the issue on a Windows 10 machine but without success.

Could you test if the issue persists with V6.22? You can get the version hereif you click on older versions.
We found another issue with the V6.22a that might be related to the one you are seeing so we want to make sure they are actually related.

Best regards,
Nino

hrb

Beginner

Date of registration: Sep 3rd 2015

Posts: 13

13

Thursday, December 7th 2017, 10:01am

Hi Nino,

6.22 works straight away. I attached the Screenshot.

Best,
Hans
hrb has attached the following image:
  • jlink22_firmware22.png

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 430

14

Thursday, December 7th 2017, 10:16am

Hi Hans,

Ok great. This is a good indicator that it might be fixed with the latest version as well.
When running your tests when it did not work, did you have multiple connections open to J-Link? For example multiple Commander instances or Commander + J-Flash etc.?
Could you try out the newest version V6.22b which we released yesterday that hopefully should solve the issue?

Best regards,
Nino

hrb

Beginner

Date of registration: Sep 3rd 2015

Posts: 13

15

Thursday, December 7th 2017, 3:44pm

Hi Nino,

i most of the time use one j-flash and debugging via the gdb server from gnu arm eclipse plugins. During the test i do i only use one jlink commander instance.

I also tested 6.22b and i still get the error. Screenshot attached.

Best,
Hans
hrb has attached the following image:
  • jlink22b_firmware22b.png

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 430

16

Thursday, December 7th 2017, 4:07pm

Hi Hans,

Quoted

I also tested 6.22b and i still get the error. Screenshot attached.


Oh bother, so it seems to be something else.
The problem is that we can't reproduce the behaviour in house whatsoever so it is tough to debug this issue without a debug setup on our side.

What makes me wonder is how did you give your J-Link Plus an IP address over DHCP?
Did you actively change some configuration or how did that happen?
If this is not your doing I suspect that the config area on the J-Link might be corrupted somehow.

Could you try to reset it by writing "resetconf" in the J-Link commander (without the quotation marks) when connected to your J-Link?
After that power the J-Link off and on again.
Does that change the behaviour?

Best regards,
Nino

hrb

Beginner

Date of registration: Sep 3rd 2015

Posts: 13

17

Friday, December 8th 2017, 2:55pm

Hi Nino,

you are right i also wonderd for some time why my jlink has an ip adress because it just has usb connection. But since everything worked i didn't really paid attention to that.
Anyway "resetconf" fixed the problem :D

Attached is the screenshot where you can see that it is working with 6.22b right now.

Thanks so much for your help. Your support is really good at SEGGER.

Best,
Hans
hrb has attached the following image:
  • jlink22b_firmware22b.png

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 430

18

Friday, December 8th 2017, 3:05pm

Hi Hans,

Great to hear that you are up and running again.

Quoted

Thanks so much for your help. Your support is really good at SEGGER.

Thank you for the flowers ;)

So does that also solve your initial issue with connecting to the LPC?
If so i would close the case.

Best regards,
Nino

hrb

Beginner

Date of registration: Sep 3rd 2015

Posts: 13

19

Friday, December 8th 2017, 5:09pm

Hi Nino,

my problem that i could not connect to my LPC4370 is also solved. Everything works fine right now.

Best,
Hans

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 430

20

Friday, December 8th 2017, 5:10pm

Hi Hans,

Thank you for coming back to us.
We will consider this case as solved now.

Best regards,
Nino