Sunday, May 20th 2018, 11:59am 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.

smishra

Beginner

Date of registration: May 4th 2017

Posts: 11

1

Friday, May 5th 2017, 12:35pm

[SOLVED/OR] Jlink Pro connects to target wtih 5.00C but not with 6.14d

I have a Cortex A9 SOC that I am working with. I am able to connect and work J-Link 5.00C but not with 6.14d.


I want to use the Ozone debugger and that seems to require the later DLLs to work.

Log with v6.14d

-------------------------------------------------------------------------------------------------

SEGGER J-Link Commander V6.14d (Compiled Apr 19 2017 18:26:24)
DLL version V6.14d, compiled Apr 19 2017 18:25:54


Connecting to J-Link via USB...O.K.
Firmware: J-Link Pro V4 compiled Apr 7 2017 09:04:32
Hardware version: V4.00
S/N: 174403061
License(s): RDI, FlashBP, FlashDL, JFlash, GDB
IP-Addr: 192.168.8.85
VTref = 1.864V




Type "connect" to establish a target connection, '?' for help
J-Link>connect
Please specify device / core. : CORTEX-A9
Type '?' for selection dialog
Device>
Please specify target interface:
J) JTAG (Default)
S) SWD
TIF>
Device position in JTAG chain (IRPre,DRPre) : -1,-1 => Auto-detect
JTAGConf>
Specify target interface speed [kHz]. : 4000 kHz
Speed>
Device "CORTEX-A9" selected.




TotalIRLen = 37, IRPrint = 0x002200000D
TotalIRLen = 37, IRPrint = 0x002200000D


****** Error: CPU-TAP not found in JTAG chain


TotalIRLen = 37, IRPrint = 0x002200000D
TotalIRLen = 37, IRPrint = 0x002200000D


****** Error: CPU-TAP not found in JTAG chain


Cannot connect to target.
J-Link>


---------------------------------------------------------------------------------------------------------------------------------------------
Log with 5.00C



SEGGER J-Link Commander V5.00c ('?' for help)
Compiled Jun 11 2015 11:40:57
DLL version V5.00c, compiled Jun 11 2015 11:40:27
Firmware: J-Link Pro V4 compiled Apr 7 2017 09:04:32
Hardware: V4.00
S/N: 174403061
Feature(s): RDI, FlashBP, FlashDL, JFlash, GDB
IP-Addr.: 192.168.8.85 (user assigned)
VTarget = 1.864V
Info: TotalIRLen = 37, IRPrint = 0x002200000D
Info: ARM AP[0]: 0x44770001, AHB-AP
Info: ARM AP[1]: 0x24770002, APB-AP
Info: ROMTbl 0 [0]: 00001003, CID: B105900D, PID:04-003BB907 ETB
Info: ROMTbl 0 [1]: 00002003, CID: B105900D, PID:04-003BB906 ECT / CTI
Info: ROMTbl 0 [2]: 00003003, CID: B105900D, PID:04-004BB912 TPIU
Info: ROMTbl 0 [3]: 00004003, CID: B105900D, PID:04-001BB908 CSTF
Info: ROMTbl 0 [4]: 00005003, CID: B105900D, PID:04-002BB913
Info: ROMTbl 0 [5]: 00100003, CID: B105100D, PID:04-000BB4A9 ROM Table
Info: ROMTbl 1 [0]: 00010003, CID: B105900D, PID:04-000BBC09 Cortex-A9
Info: Found Cortex-A9 r4p1
Info: 6 code breakpoints, 4 data breakpoints
Info: Debug architecture ARMv7.0
Info: Data endian: little
Info: Main ID register: 0x414FC091
Info: I-Cache L1: 32 KB, 256 Sets, 32 Bytes/Line, 4-Way
Info: D-Cache L1: 32 KB, 256 Sets, 32 Bytes/Line, 4-Way
Info: System control register:
Info: Instruction endian: little
Info: Level-1 instruction cache enabled
Info: Level-1 data cache enabled
Info: MMU enabled
Info: Branch prediction enabled
Found 3 JTAG devices, Total IRLen = 37:
#0 Id: 0x0420C065
#1 Id: 0x4BA00477, IRLen: 04, IRPrint: 0x1, CoreSight JTAG-DP (ARM)
#2 Id: 0x0420C065
Cortex-A9 identified.
Target interface speed: 100 kHz
J-Link>

SEGGER - Niklas

Super Moderator

Date of registration: Oct 6th 2014

Posts: 1,691

2

Friday, May 5th 2017, 2:25pm

Hi,

with 5.00c, the JTAG speed defaults to 100 kHz.

C/C++ Source code

1
Target interface speed: 100 kHz


With version 6.14d, you specified 4000 kHz as interface speed.

C/C++ Source code

1
2
Specify target interface speed [kHz]. : 4000 kHz
Speed>


Could you please give it a try using 100 kHz as interface speed?

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

smishra

Beginner

Date of registration: May 4th 2017

Posts: 11

3

Friday, May 5th 2017, 3:35pm

Same result with connection speed of 100kHz. Since the JLink software seems to be able to read the IR and DR registers, it may be a difference in how processing flows in the software for different register values in v5.00C vs 6.14D


J-Link>ip 192.168.8.85
Connecting to 192.168.8.85
Connecting to J-Link via IP...O.K.
Firmware: J-Link Pro V4 compiled Apr 7 2017 09:04:32
Hardware version: V4.00
S/N: 174403061
License(s): RDI, FlashBP, FlashDL, JFlash, GDB
IP-Addr: 192.168.8.85
VTref = 1.862V
J-Link>connect
Please specify device / core. : CORTEX-A9
Type '?' for selection dialog
Device>
Please specify target interface:
J) JTAG (Default)
S) SWD
TIF>
Device position in JTAG chain (IRPre,DRPre) : -1,-1 => Auto-detect
JTAGConf>
Specify target interface speed [kHz]. : 4000 kHz
Speed>100
Device "CORTEX-A9" selected.


TotalIRLen = 37, IRPrint = 0x002200000D
TotalIRLen = 37, IRPrint = 0x002200000D

****** Error: CPU-TAP not found in JTAG chain
P/IP (192.168.8.85, port 19020)
TotalIRLen = 37, IRPrint = 0x002200000D
TotalIRLen = 37, IRPrint = 0x002200000D

****** Error: CPU-TAP not found in JTAG chain
P/IP (192.168.8.85, port 19020)
Cannot connect to target.

SEGGER - Niklas

Super Moderator

Date of registration: Oct 6th 2014

Posts: 1,691

4

Friday, May 5th 2017, 4:26pm

Hi,


so the autodetection for the chain in V614d seems not be as effective as in 5.00c.

Does it work if you pass the corrrect parameters for the position in the chain?

C/C++ Source code

1
2
Device position in JTAG chain (IRPre,DRPre) : -1,-1 => Auto-detect
JTAGConf>


Quoted

I have a Cortex A9 SOC

Whats the name of the device / SOC? Or is it a FPGA?

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

smishra

Beginner

Date of registration: May 4th 2017

Posts: 11

5

Friday, May 5th 2017, 4:58pm

Can I determine the correct position and other parameters using the working 5.00C and pass them to 6.14D? What would the commands to do so be? Can you tell from the following working 5.00C log

Thanks
Sanjay

Here is the working 5.00C log


EGGER J-Link Commander V5.00c ('?' for help)
Compiled Jun 11 2015 11:40:57
DLL version V5.00c, compiled Jun 11 2015 11:40:27
Firmware: J-Link Pro V4 compiled Apr 7 2017 09:04:32
Hardware: V4.00
S/N: 174403061
Feature(s): RDI, FlashBP, FlashDL, JFlash, GDB
IP-Addr.: 192.168.8.85 (user assigned)
VTarget = 1.864V
Info: TotalIRLen = 37, IRPrint = 0x002200000D
Info: ARM AP[0]: 0x44770001, AHB-AP
Info: ARM AP[1]: 0x24770002, APB-AP
Info: ROMTbl 0 [0]: 00001003, CID: B105900D, PID:04-003BB907 ETB
Info: ROMTbl 0 [1]: 00002003, CID: B105900D, PID:04-003BB906 ECT / CTI
Info: ROMTbl 0 [2]: 00003003, CID: B105900D, PID:04-004BB912 TPIU
Info: ROMTbl 0 [3]: 00004003, CID: B105900D, PID:04-001BB908 CSTF
Info: ROMTbl 0 [4]: 00005003, CID: B105900D, PID:04-002BB913
Info: ROMTbl 0 [5]: 00100003, CID: B105100D, PID:04-000BB4A9 ROM Table
Info: ROMTbl 1 [0]: 00010003, CID: B105900D, PID:04-000BBC09 Cortex-A9
Info: Found Cortex-A9 r4p1
Info: 6 code breakpoints, 4 data breakpoints
Info: Debug architecture ARMv7.0
Info: Data endian: little
Info: Main ID register: 0x414FC091
Info: I-Cache L1: 32 KB, 256 Sets, 32 Bytes/Line, 4-Way
Info: D-Cache L1: 32 KB, 256 Sets, 32 Bytes/Line, 4-Way
Info: System control register:
Info: Instruction endian: little
Info: Level-1 instruction cache enabled
Info: Level-1 data cache enabled
Info: MMU enabled
Info: Branch prediction enabled
Found 3 JTAG devices, Total IRLen = 37:
#0 Id: 0x0420C065
#1 Id: 0x4BA00477, IRLen: 04, IRPrint: 0x1, CoreSight JTAG-DP (ARM)
#2 Id: 0x0420C065
Cortex-A9 identified.

Thanks
Sanjay

SEGGER - Niklas

Super Moderator

Date of registration: Oct 6th 2014

Posts: 1,691

6

Friday, May 5th 2017, 5:39pm

Hi Sanjay,

Quoted

What would the commands to do so be?

as far as I can see, there are no command available for this in J-Link Commander.
Apart from using the J-Link SDK (Part No 8.08.06 on the price list),
you could use J-Flash (part of the J-Link software & documentation pack, can be used free of charge with J-Link PRO), which has a auto detect feature in the Target Interface tab of the project settings, which can be opened with ALT+F7.


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

smishra

Beginner

Date of registration: May 4th 2017

Posts: 11

7

Saturday, May 6th 2017, 5:36am

The hardware works because it works with 5.00C.


Does JLink have a detailed log feature where its decisions are logged? If so we could turn on logging with 5.00C and see what is happening and compare with 6.14D


If there is a tech support number I can call in Germany or in US and resolve this in real time let me know. I emailed tech support email that came with the product but I have not received a response yet.

Thanks
Sanjay

This post has been edited 1 times, last edit by "smishra" (May 6th 2017, 5:38am)


SEGGER - Niklas

Super Moderator

Date of registration: Oct 6th 2014

Posts: 1,691

8

Monday, May 8th 2017, 9:39am

Hi Sanjay,

Quoted

The hardware works because it works with 5.00C.

I agree with this statement, however, since most new devices require special handling and got confused from the auto-detect routines of the J-Link software, the routines were partly removed or re-written in versions 5.10 and later of the J-Link software. Without having a similar hardware to reproduce the issue (I understand that there are reasons for this), I cannot test how we get the auto-dection for this SoC working again without breaking anything.

Therefore, I suggested to use J-Flash to find out more about the JTAG-chain, also regarding to your question:

Quoted

Can I determine the correct position and other parameters using the working 5.00C and pass them to 6.14D? What would the commands to do so be? Can you tell from the following working 5.00C log

The J-Link Commander 5.00c log unfortunately does not show the IRLen of the two 0x0420C065 devices.

Quoted

[...]you could use J-Flash (part of the J-Link software & documentation pack, can be used free of charge with J-Link PRO), which has a auto detect feature in the Target Interface tab of the project settings, which can be opened with ALT+F7.


In the interface tab, just select JTAG and 100 kHz Interface speed, then choose Detailed configuration and click Detect.
The result will show up in the area marked green.



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

smishra

Beginner

Date of registration: May 4th 2017

Posts: 11

9

Monday, May 8th 2017, 2:29pm

Thanks a lot for your help! Here is what I get with JFlash v5

Device Number - Device Name - ID - IRLen
0 - Unknown JTAG Device - 0420C065 - 25
1 - CoreSight JTAG-DP - 4BA00477 - 4
2 - Unknown JTAG Device - 0420C065 - 8




I have also attached a screenshot.

How do I use these parameters in v6 JLink to connect?





-----------------------------------------------------------------------------------

Just as a test I took the configuration detected above using JFLash 5 and manually added them in Project Settings for v6.14 JFlash

I then did a verify in Project Settings of JFlash 6 and got a

ERROR: CPU-TAP not found in JTAG chain

message in JFlash 6 log window.

See attached image for details
-------------------------------------------------------------------------------------------

When I open the same JFlash project file in JFlash5, go to project settings, and hit verify, the configuration is verified successfully.


Thanks again
smishra has attached the following image:
  • JFlash6.png

This post has been edited 5 times, last edit by "smishra" (May 8th 2017, 2:47pm)


SEGGER - Niklas

Super Moderator

Date of registration: Oct 6th 2014

Posts: 1,691

10

Tuesday, May 9th 2017, 9:39am

Hi Sanjay,


thanks for the tests.
I forwarded this issue to my colleagues, they will respond either here in the forum or via mail.


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

smishra

Beginner

Date of registration: May 4th 2017

Posts: 11

11

Thursday, May 11th 2017, 4:49am

I got an email from support that resolved the issue.

Segger support is great.

Thank you!

SEGGER - Niklas

Super Moderator

Date of registration: Oct 6th 2014

Posts: 1,691

12

Thursday, May 11th 2017, 8:42am

Hi Sanjay,


thanks for the feedback! Good to hear that you are up and running again with the new version!


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

SEGGER - Niklas

Super Moderator

Date of registration: Oct 6th 2014

Posts: 1,691

13

Thursday, May 11th 2017, 8:46am

Hi Forum,


the fix is not officially available yet, as it requires some internal testing in order to make sure that the improvement does not break existing setups.
It will therefore be available in the next version of the J-Link software & documentation pack (beta), V6.15f .
In order to receive an E-Mail notification when the fix is available in a release version, please subscribe to the release notes mailing list: https://www.segger.com/notification/subs…php?prodid=7,94 .

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