Sunday, May 20th 2018, 12:03pm UTC+2

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.

shengsu

Beginner

Date of registration: Dec 17th 2015

Posts: 4

1

Thursday, December 17th 2015, 4:28pm

[SOLVED] / [ABANDONED] J-Link V5.10d Internal Error while trying to start debug session

Hello.
I just bought Atmel AT91SAM9X5-EK board and Atmel SAM-ICE debug probe (OEM version of J-Link, sold by Atmel). Using Keil uVision 5 created my first project - tiny LED blinker, compiled it successfully, trying to start debug session. But it doesn't start because of messages about J-Link internal errors: First one is "Could not find breakpoint in internal list", the second one is "Illegal breakpoint handle (0x0001)" and then "Connection to JLink lost. Shutting down debug session."

Command window log:

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
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
Running with Code Size Limit: 32K
ProjectFile = D:\Workspace\embedded\temp\nsam9x\JLinkArm_Target 1.ini
Info: Device "AT91SAM9X25" selected.
Device = SAM9X25
Info: Device "AT91SAM9X25" selected.
VTarget = 3.287V
Info: TotalIRLen = 4, IRPrint = 0x01
Info: CP15.0.0: 0x41069265: ARM, Architecure 5TEJ
Info: CP15.0.1: 0x1D152152: ICache: 16kB (4*128*32), DCache: 16kB (4*128*32)
Info: Cache type: Separate, Write-back, Format C (WT supported)
Info: RTCK reaction time is approx. 126ns
Info: Auto JTAG speed: Adaptive
Info: J-Link: ARM9 CP15 Settings changed: 51078 from 78, MMU Off, ICache On, DCache Off
Info: CP15.0.0: 0x41069265: ARM, Architecure 5TEJ
Info: CP15.0.1: 0x1D152152: ICache: 16kB (4*128*32), DCache: 16kB (4*128*32)
Info: Cache type: Separate, Write-back, Format C (WT supported)
DLL version V5.10d, compiled Dec  9 2015 12:49:14
Firmware: J-Link ARM V8 compiled Aug 26 2015 15:08:21
Hardware: V8.00

Hardware-Breakpoints: 2
Software-Breakpoints: 8192
Watchpoints:      	0

Found 1 JTAG device, Total IRLen = 4:
 Id of device #0: 0x0792603F
ARM9 identified.
Using adaptive clocking instead of fixed JTAG speed.
S/N : (cut off) 
OEM : SAM-ICE 
Feature(s) : RDI, GDB 
ETM support, Trace buffer size: 0KB
VTarget = 3.280V
Info: CP15.0.0: 0x41069265: ARM, Architecure 5TEJ
Info: CP15.0.1: 0x1D152152: ICache: 16kB (4*128*32), DCache: 16kB (4*128*32)
Info: Cache type: Separate, Write-back, Format C (WT supported)
JTAG speed: 1000 kHz
Load "D:\\Workspace\\embedded\\temp\\nsam9x\\Objects\\nsam9x.axf" 

*** Restricted Version with 32768 Byte Code Size Limit
*** Currently used: 728 Bytes (2%)

Info: CP15.0.0: 0x41069265: ARM, Architecure 5TEJ
Info: CP15.0.1: 0x1D152152: ICache: 16kB (4*128*32), DCache: 16kB (4*128*32)
Info: Cache type: Separate, Write-back, Format C (WT supported)
JTAG speed: 1000 kHz
BS \\nsam9x\main.c\10
***JLink Error: Bad JTAG communication: Write to IR: Expected 0x1, got 0x0 (TAP Command : 2) @ Off 0x5.


Any suggestions how to solve this problem?

SEGGER - Niklas

Super Moderator

Date of registration: Oct 6th 2014

Posts: 1,691

2

Thursday, December 17th 2015, 4:46pm

Hi,


thanks for your inquiry.
Please be aware that neither Atmel SAM-ICE nor Keil uVision 5 is a SEGGER product.

Could you provide is with a complete J-Link Logfile of an (attempted) debug session?
Log output can be enabled like as follows:
  • Open a connection to J-Link, e.g start J-Link Commander
  • In J-Link Control Panel: (Click the J-Link symbol located in the notification / tray area in order to open J-Link Control panel)
  • Open the tab "Settings"
  • Next to the field "Log file" check "Override" and click "..." in order to choose a log file path.

This is also described in UM8001 Chapter 5 "Working with J-Link and J-Trace", Section 5.7 "J-Link control panel" .

Best regards,
Niklas
Would you like to be added to the J-Link software update notification list, so you get informed automatically when a new version becomes available?
Just write me a PM or in case you want to subscribe to it yourself, please use this link: Link
Notification for J-Link, J-Link Debugger, SystemView & J-Scope: Link
Notification for Embedded Studio: Link

shengsu

Beginner

Date of registration: Dec 17th 2015

Posts: 4

3

Thursday, December 17th 2015, 5:04pm

Hi,

Here is the log:

Source code

1
2
3
4
5
6
7
8
9
10
T07C8 004:066 SEGGER J-Link V5.10d Log File (0018ms, 3509ms total)
T07C8 004:066 DLL Compiled: Dec  9 2015 12:49:14 (0018ms, 3509ms total)
T07C8 004:066 Logging started @ 2015-12-17 19:03 (0018ms, 3509ms total)
T07C8 004:066 JLINK_ClrBPEx(BPHandle = 0x00000001) >0x2F8 JTAG>TotalIRLen = 4, IRPrint = 0x01 >0x30 JTAG> >0x210 JTAG> >0x58 JTAG> >0x58 JTAG> >0x18 JTAG> >0x88 JTAG> >0x48 JTAG> >0x1A0 JTAG> >0x48 JTAG> >0x910 JTAG> >0x70 JTAG> >0x90 JTAG>CP15.0.0: 0x41069265: ARM, Architecure 5TEJ >0x90 JTAG>CP15.0.1: 0x1D152152: ICache: 16kB (4*128*32), DCache: 16kB (4*128*32)Cache type: Separate, Write-back, Format C (WT supported) -- Detecting speed: - RTCK reaction time is approx. 126ns
RTCK reaction time is approx. 126ns - 2380kHz: >0x78 JTAG> O.K. -- Auto JTAG speed: AdaptiveAuto JTAG speed: Adaptive >0x08 JTAG> >0x3F0 JTAG> >0x10 JTAG> >0x48 JTAG> -- CPU is running
  ***** Internal Error: Could not find breakpoint in internal list. >0x48 JTAG> >0x1A0 JTAG> >0x48 JTAG> >0x910 JTAG> >0x80 JTAG> >0x10 JTAG>
  ***** Error: Illegal breakpoint handle (0x0001) >0x3F0 JTAG>  returns 0x01 (2548ms, 6039ms total)
T07C8 008:651 JLINK_Close() >0x08 JTAG> (0005ms, 6044ms total)
T07C8 008:651  (0005ms, 6044ms total)
T07C8 008:651 Closed (0005ms, 6044ms total)

SEGGER - Niklas

Super Moderator

Date of registration: Oct 6th 2014

Posts: 1,691

4

Friday, December 18th 2015, 9:06am

Hi,


is this the complete Logfile?
If yes, this looks to me like an IDE error.
Clearing a breakpoint which has not been set in the first place and then calling JLINK_Close()
without ever calling open() or any other initialization before JLINK_ClrBPEx() seems plain wrong to me.


Best regards,
Niklas
Would you like to be added to the J-Link software update notification list, so you get informed automatically when a new version becomes available?
Just write me a PM or in case you want to subscribe to it yourself, please use this link: Link
Notification for J-Link, J-Link Debugger, SystemView & J-Scope: Link
Notification for Embedded Studio: Link

shengsu

Beginner

Date of registration: Dec 17th 2015

Posts: 4

5

Friday, December 18th 2015, 12:34pm

Hi,

Yes, that was compete log file. I tried to install old version of Keil, and it leaded to the same result. Also I tried different reset strategies, when "No Reset" strategy is chosen, debug session is started, but I can not define any breakpoint in c-code area, only in assembler area. Almost useless.
Don't know what to think, if it is a problem of Keil IDE. Don't believe nobody got the same problem earlier. :(

I also have a way to get IAR J-Link with evaluation version of IAR, so I will try it that way.

SEGGER - Niklas

Super Moderator

Date of registration: Oct 6th 2014

Posts: 1,691

6

Friday, December 18th 2015, 4:49pm

Hi,


feel free to provide us with your Keil project, so we can take a look at it.

Basically, the following happens:
  • IDE -> J-Link: Clear Breakpoint 0x01
  • J-Link -> IDE: A BP with the handle 0x01 does not exist
  • IDE quits the session
Why the IDE quits at this point I cannot tell you, it is not necessary.

Best regards,
Niklas
Would you like to be added to the J-Link software update notification list, so you get informed automatically when a new version becomes available?
Just write me a PM or in case you want to subscribe to it yourself, please use this link: Link
Notification for J-Link, J-Link Debugger, SystemView & J-Scope: Link
Notification for Embedded Studio: Link

shengsu

Beginner

Date of registration: Dec 17th 2015

Posts: 4

7

Monday, December 21st 2015, 9:58am

Hi,

I have tried IAR and it works good without any problem with the same probe and the same code. So I think I will stay with it for the time being. Nevertheless, I attached the Keil project, so if you got some time, I would like to know if is it buggy software or some my fault in project settings. Thank you for your help!

newsam9x.zip

questioner

Beginner

Date of registration: Feb 22nd 2016

Posts: 1

8

Monday, February 22nd 2016, 3:47pm

Hello,
i nearly have the same problem which is described here. In the past I used µVision 4 and the Segger J-Link EDU with no problems. After I updated to µVision 5 and the automatic firmware update of the J-Link I have that issue. I tried to install the newest J-Link software pack for Windows V5.10n with no success. The only difference is that now the message "Could not find breakpoint in internal list" isn’t displayed. After start “run” it ends with "Connection to JLink lost. Shutting down debug session." Even now under µVision 4 there happened strange things. I only can use single steps and after some steps it crash with the same message.


Maybe you can test the program from shengsu above and give me an advice how to solve that problem.


Thanks,
Regards

This post has been edited 1 times, last edit by "questioner" (Feb 22nd 2016, 3:49pm)


SEGGER - Niklas

Super Moderator

Date of registration: Oct 6th 2014

Posts: 1,691

9

Tuesday, February 23rd 2016, 11:09am

Hi,

what target are you using? Could provide us with a reproduction project?
Shengsu is using a AT91SAM9X25 device which has not internal flash, and his project does not work for me at all...

Best regards,
Niklas
Would you like to be added to the J-Link software update notification list, so you get informed automatically when a new version becomes available?
Just write me a PM or in case you want to subscribe to it yourself, please use this link: Link
Notification for J-Link, J-Link Debugger, SystemView & J-Scope: Link
Notification for Embedded Studio: Link

Eitum

Beginner

Date of registration: Mar 1st 2016

Posts: 3

10

Tuesday, March 1st 2016, 9:31am

Hi,

I have a similar problem with an AduC7060 from AnalogDevice.

I can definitly say, the problem ist Segger related, as the same hardware is working with the same debugger on another PC. the only difference is that I have the latest driver installed.

While starting the debug I receive the Following Error:

***JLink Error: Bad JTAG communication: Write to IR: Expected 0x1, got 0x2 (TAP Command : 12) @ Off 0x13.

Deactivating the Option "Run to main()" allowed me to enter debugging. But Running always caused the previous error.

Debugging the Assembler showed he is jumping to 0x00000000 after this:

IMPORT __main
LDR R0, =__main
BX R0

As I said previously the code is working on another PC. It's also strange that i can set Breakpoints in assembler but the debugger is not holding there.

I'm running out of ideas so I would love to hear any suggestions what I might have set up wrong.

In Addition: I tried some example projects from Keil with the same result as with my code.... so I doubt it code related.

Edit:
Some further information. I can step throught the disassembly step by step, even throught the user code till (and including) the infinite loop. But I cannot autorun or use debug points. It seems He cannot stop the controller one i let it go.

This post has been edited 2 times, last edit by "Eitum" (Mar 1st 2016, 10:14am)


SEGGER - Niklas

Super Moderator

Date of registration: Oct 6th 2014

Posts: 1,691

11

Tuesday, March 1st 2016, 10:38am

Hi,

thanks for your inquiry.

Quoted

the only difference is that I have the latest driver installed.

Are you referring to the J-Link software & documentation pack?
If so, could you tell us which version is working for you (other PC) and which is not (current PC)?

Quoted

I tried some example projects from Keil with the same result as with my code.... so I doubt it code related.

Can you point me to an example which can be used to reproduce the issue with an AduC70xx device?

Best regards,
Niklas
Would you like to be added to the J-Link software update notification list, so you get informed automatically when a new version becomes available?
Just write me a PM or in case you want to subscribe to it yourself, please use this link: Link
Notification for J-Link, J-Link Debugger, SystemView & J-Scope: Link
Notification for Embedded Studio: Link

Eitum

Beginner

Date of registration: Mar 1st 2016

Posts: 3

12

Tuesday, March 1st 2016, 11:29am

I attached my project as well as my Keil information.

I eliminated the driver as cause by managing to get the same as on the other pc installed and all other removed.

The project is currently quiet simple and is used with the eval board EVAL-ADuC7060 Rev A1.

As we're now talking about the standard installation of keil together with an eval board I believe the problem might be in the integration in keil.
I enver expected such problems with Segger hardware before.

The J-Link is a branded one from Analog Devices: mIDAS-Link.
Eitum has attached the following image:
  • Keil.PNG
Eitum has attached the following file:

SEGGER - Niklas

Super Moderator

Date of registration: Oct 6th 2014

Posts: 1,691

13

Tuesday, March 1st 2016, 5:00pm

Hi,

I am sorry, but I cannot reproduce the issue here.
I can step, run to breakpoints etc... without any problem.

Quoted

I can definitly say, the problem ist Segger related, as the same hardware is working with the same debugger on another PC. the only difference is that I have the latest driver installed.

Quoted

I eliminated the driver as cause by managing to get the same as on the other pc installed and all other removed.

Do I understand you correctly, that your setup is working on another PC with the same Debugger and same target?

Best regards,
Niklas
Would you like to be added to the J-Link software update notification list, so you get informed automatically when a new version becomes available?
Just write me a PM or in case you want to subscribe to it yourself, please use this link: Link
Notification for J-Link, J-Link Debugger, SystemView & J-Scope: Link
Notification for Embedded Studio: Link

Eitum

Beginner

Date of registration: Mar 1st 2016

Posts: 3

14

Wednesday, March 2nd 2016, 4:10pm

yes you are right, the same setup is working on another PC without problems.

Using another kind of debugger (competitor) it worked straight out of the box. It seems to be a driver issue, or at least a setting in keil caused by the latest driver.

jmag999

Beginner

Date of registration: Aug 13th 2014

Posts: 16

15

Friday, March 4th 2016, 8:29pm

We are having the same problem. Other debuggers work fine. This just started happening a few days ago with IAR. 2 Developers have the problem. 1 other developers JLink is working fine.

SEGGER - Niklas

Super Moderator

Date of registration: Oct 6th 2014

Posts: 1,691

16

Monday, March 7th 2016, 6:25pm

Hi,

@Eitum
It looks like the J-Link is o.k, but the communication between J-Link and Target is faulty. (e.g faulty cable, insufficient voltage level driver of the JTAG pins,.......)
Could you please post a screenshot of a debug session with J-Link Commander?
Example Steps:
  • Start J-Link Commander (jlink.exe)
  • Type "connect" in order to start a debug session
  • Type in the Device name if asked (ADuC7060)
  • Choose the correct target interface (JTAG)
  • Speed should be <= 200 for this session
  • JTAG conf can be auto
  • You should now be successfully connected.
  • It should now be possible to use the following commands:
  • "s" (Single Step)
  • "r" (Reset)
  • "h" (Halt)
  • "g" (Go)
@jmag99
What kind of problems are you experiencing ?
Do the 2 J-Link still work at all?

Best regards,
Niklas
Would you like to be added to the J-Link software update notification list, so you get informed automatically when a new version becomes available?
Just write me a PM or in case you want to subscribe to it yourself, please use this link: Link
Notification for J-Link, J-Link Debugger, SystemView & J-Scope: Link
Notification for Embedded Studio: Link