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

You are not logged in.

  • Login
  • Register

jiri

Beginner

Date of registration: May 4th 2016

Posts: 6

Location: Prague

1

Monday, December 4th 2017, 3:51pm

J-Link and Windows 10 issues

Hello,
we have been using J-Link to debug MCIMX6G1 since it's support was introduced without any issues. We have been running Win 7, but unfortunately, we're forced to move to Win 10. We have already found two issues.

The first issue is with fw upgrade. When firmware upgrade attempt occurs, it fails almost immediately (see attached image ). Luckily unplugging and plugging J-link again solves the issue, as the fw upgrade from "recovery mode" works.

Second issue is that new versions (6.21d, 6.22, 6.22a) couldn't attach to cpu any more. Log follows. The result is same for any fw version we tried.

C/C++ 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
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
C:\Program Files (x86)\SEGGER\JLink_V622a>jlink
SEGGER J-Link Commander V6.22a (Compiled Nov 28 2017 17:56:48)
DLL version V6.22a, compiled Nov 28 2017 17:56:10

Connecting to J-Link via USB...O.K.
Firmware: J-Link Pro V4 compiled Nov 28 2017 11:47:28
Hardware version: V4.00
S/N: 174xxxxxx
License(s): RDI, FlashBP, FlashDL, JFlash, GDB
IP-Addr: DHCP (no addr. received yet)
VTref = 1.089V


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


Connecting to target via JTAG
TotalIRLen = 13, IRPrint = 0x0101

**************************
WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)

**************************

JTAG chain detection found 3 devices:
 #0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP
 #1 Id: 0x00000001, IRLen: 05, Unknown device
 #2 Id: 0x1891D01D, IRLen: 04, JTAG-DP
Scanning AP map to find all available APs
AP[2]: Stopped AP scan as end of AP map seems to be reached
AP[0]: AHB-AP (IDR: 0x74770001)
AP[1]: APB-AP (IDR: 0x44770002)
Iterating through AP map to find AHB-AP to use
AP[0]: Skipped. Not an APB-AP
AP[1]: APB-AP found
Invalid ROM table component ID 0x2F0F0F02 @ 0x20001EF0 (expected 0xB105100D). Trying again at alternative offset.
Invalid ROM table component ID 0x2F0F0F02 @ 0x60000FF0 (expected 0xB105100D). Trying again at alternative offset.
TotalIRLen = 13, IRPrint = 0x0101

**************************
WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)

**************************

JTAG chain detection found 3 devices:
 #0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP
 #1 Id: 0x00000001, IRLen: 05, Unknown device
 #2 Id: 0x1891D01D, IRLen: 04, JTAG-DP

****** Error: Cortex-A/R-JTAG (connect): Could not determine address of core debug registers. Incorrect CoreSight ROM table in device?
TotalIRLen = 13, IRPrint = 0x0101

**************************
WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)

**************************

JTAG chain detection found 3 devices:
 #0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP
 #1 Id: 0x00000001, IRLen: 05, Unknown device
 #2 Id: 0x1891D01D, IRLen: 04, JTAG-DP
TotalIRLen = 13, IRPrint = 0x0101

**************************
WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)

**************************

JTAG chain detection found 3 devices:
 #0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP
 #1 Id: 0x00000001, IRLen: 05, Unknown device
 #2 Id: 0x1891D01D, IRLen: 04, JTAG-DP
Cannot connect to target.


But, if we use older J-Link version (6.15f), it works as expected even with newest firmware:

C/C++ 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
49
50
J-Link>connect
Please specify device / core. <Default>: MCIMX6G1
Type '?' for selection dialog
Device>
Please specify target interface:
J) JTAG (Default)
S) SWD
TIF>
Device position in JTAG chain (IRPre,DRPre) <Default>: -1,-1 => Auto-detect
JTAGConf>
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "MCIMX6G1" selected.


TotalIRLen = 13, IRPrint = 0x0101

**************************
WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)

**************************

JTAG chain detection found 3 devices:
#0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP
#1 Id: 0x00000001, IRLen: ?, Unknown device
#2 Id: 0x1891D01D, IRLen: ?, Unknown device
ARM AP[0]: 0x74770001, AHB-AP
ARM AP[1]: 0x44770002, APB-AP
ROMTbl[0][0]: CompAddr: 80001000 CID: B105900D, PID:04-001BB961 TMC
ROMTbl[0][1]: CompAddr: 80002000 CID: B105900D, PID:04-004BB906 ECT / CTI
ROMTbl[0][2]: CompAddr: 80003000 CID: B105900D, PID:04-004BB912 TPIU
ROMTbl[0][3]: CompAddr: 80004000 CID: B105F00D, PID:04-001BB101
ROMTbl[0][4]: CompAddr: 80020000 CID: B105100D, PID:04-000BB4A7 ROM Table
ROMTbl[1][0]: CompAddr: 80030000 CID: B105900D, PID:04-005BBC07 Cortex-A7
Found Cortex-A7 r0p5
6 code breakpoints, 4 data breakpoints
Debug architecture ARMv7.1
Data endian: little
Main ID register: 0x410FC075
I-Cache L1: 32 KB, 512 Sets, 32 Bytes/Line, 2-Way
D-Cache L1: 32 KB, 128 Sets, 64 Bytes/Line, 4-Way
Unified-Cache L2: 128 KB, 256 Sets, 64 Bytes/Line, 8-Way
System control register:
Instruction endian: little
Level-1 instruction cache enabled
Level-1 data cache enabled
MMU enabled
Branch prediction enabled
Cortex-A7 identified.
J-Link>


Although we eventualy got working configuration, it doesn't somehow feel good, to ignore these issues.

This post has been edited 1 times, last edit by "jiri" (Dec 4th 2017, 3:53pm)


SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 430

2

Monday, December 4th 2017, 3:56pm

Hello,

Thank you for your inquiry.
Such an issue is not known to us.
We will try to reproduce the issue and come back to you.

What VTref value do you get with V6.15f?
In V6.22a it is at about ~1 V. Is that voltage expected at your target?

Best regards,
Nino

jiri

Beginner

Date of registration: May 4th 2016

Posts: 6

Location: Prague

3

Monday, December 4th 2017, 4:07pm

Hello,
thank you for a prompt response. VTref is 3.349 in both cases. So it's probably what is expected.

Sincerely
Jiri

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 430

4

Tuesday, December 5th 2017, 9:34am

Hello,

To clarify, VTref shows ~3.3 V for J-Link version V6.15f and 6.22a?
Because in the logs you posted earlier for V6.22a it shows: VTref = 1.089V

Did that change?
Could you post a screenshot of the J-Link commander output in both cases?

Best regards,
Nino

jiri

Beginner

Date of registration: May 4th 2016

Posts: 6

Location: Prague

5

Tuesday, December 5th 2017, 10:30am

Hello,
I rerun connect for both versions.

Before running JLink.exe, the board is connected to power, then the boot is stoped at u-boot prompt.

6.22a

C/C++ 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
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
C:\Program Files (x86)\SEGGER\JLink_V622a>jlink
SEGGER J-Link Commander V6.22a (Compiled Nov 28 2017 17:56:48)
DLL version V6.22a, compiled Nov 28 2017 17:56:10

Connecting to J-Link via USB...O.K.
Firmware: J-Link Pro V4 compiled Nov 28 2017 11:47:28
Hardware version: V4.00
S/N: 174xxxxxx
License(s): RDI, FlashBP, FlashDL, JFlash, GDB
IP-Addr: DHCP (no addr. received yet)
VTref = 3.349V


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


Connecting to target via JTAG
TotalIRLen = 13, IRPrint = 0x0101

**************************
WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)

**************************

JTAG chain detection found 3 devices:
#0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP
#1 Id: 0x00000001, IRLen: 05, Unknown device
#2 Id: 0x1891D01D, IRLen: 04, JTAG-DP
Scanning AP map to find all available APs
AP[2]: Stopped AP scan as end of AP map seems to be reached
AP[0]: AHB-AP (IDR: 0x74770001)
AP[1]: APB-AP (IDR: 0x44770002)
Iterating through AP map to find AHB-AP to use
AP[0]: Skipped. Not an APB-AP
AP[1]: APB-AP found
Invalid ROM table component ID 0x2F0F0F02 @ 0x20001EF0 (expected 0xB105100D). Trying again at alternative offset.
Invalid ROM table component ID 0x2F0F0F02 @ 0x60000FF0 (expected 0xB105100D). Trying again at alternative offset.
TotalIRLen = 13, IRPrint = 0x0101

**************************
WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)

**************************

JTAG chain detection found 3 devices:
#0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP
#1 Id: 0x00000001, IRLen: 05, Unknown device
#2 Id: 0x1891D01D, IRLen: 04, JTAG-DP

****** Error: Cortex-A/R-JTAG (connect): Could not determine address of core debug registers. Incorrect CoreSight ROM table in device?
TotalIRLen = 13, IRPrint = 0x0101

**************************
WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)

**************************

JTAG chain detection found 3 devices:
#0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP
#1 Id: 0x00000001, IRLen: 05, Unknown device
#2 Id: 0x1891D01D, IRLen: 04, JTAG-DP
TotalIRLen = 13, IRPrint = 0x0101

**************************
WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)

**************************

JTAG chain detection found 3 devices:
#0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP
#1 Id: 0x00000001, IRLen: 05, Unknown device
#2 Id: 0x1891D01D, IRLen: 04, JTAG-DP
Cannot connect to target.


6.15f

C/C++ 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
49
50
51
52
53
54
55
56
57
58
59
60
61
62
SEGGER J-Link Commander V6.15f (Compiled May 22 2017 18:57:01)
DLL version V6.15f, compiled May 22 2017 18:56:28

Connecting to J-Link via USB...O.K.
Firmware: J-Link Pro V4 compiled Nov 28 2017 11:47:28
Hardware version: V4.00
S/N: 174xxxxxx
License(s): RDI, FlashBP, FlashDL, JFlash, GDB
IP-Addr: DHCP (no addr. received yet)
VTref = 3.349V


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


TotalIRLen = 13, IRPrint = 0x0101

**************************
WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)

**************************

JTAG chain detection found 3 devices:
#0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP
#1 Id: 0x00000001, IRLen: ?, Unknown device
#2 Id: 0x1891D01D, IRLen: ?, Unknown device
ARM AP[0]: 0x74770001, AHB-AP
ARM AP[1]: 0x44770002, APB-AP
ROMTbl[0][0]: CompAddr: 80001000 CID: B105900D, PID:04-001BB961 TMC
ROMTbl[0][1]: CompAddr: 80002000 CID: B105900D, PID:04-004BB906 ECT / CTI
ROMTbl[0][2]: CompAddr: 80003000 CID: B105900D, PID:04-004BB912 TPIU
ROMTbl[0][3]: CompAddr: 80004000 CID: B105F00D, PID:04-001BB101
ROMTbl[0][4]: CompAddr: 80020000 CID: B105100D, PID:04-000BB4A7 ROM Table
ROMTbl[1][0]: CompAddr: 80030000 CID: B105900D, PID:04-005BBC07 Cortex-A7
Found Cortex-A7 r0p5
6 code breakpoints, 4 data breakpoints
Debug architecture ARMv7.1
Data endian: little
Main ID register: 0x410FC075
I-Cache L1: 32 KB, 512 Sets, 32 Bytes/Line, 2-Way
D-Cache L1: 32 KB, 128 Sets, 64 Bytes/Line, 4-Way
Unified-Cache L2: 128 KB, 256 Sets, 64 Bytes/Line, 8-Way
System control register:
Instruction endian: little
Level-1 instruction cache enabled
Level-1 data cache enabled
MMU enabled
Branch prediction enabled
Cortex-A7 identified.

jiri

Beginner

Date of registration: May 4th 2016

Posts: 6

Location: Prague

6

Tuesday, December 5th 2017, 11:00am

I also tried v6.22a on Windows 7, with same results. It seems the problem is not related to Win 10 at all. Latest working version, which I could try is v6.20a.

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 430

7

Wednesday, December 6th 2017, 12:10pm

Hello,

Thank you for providing additional information.
We found another issue in V6.22a that might be related to this case.
Could you try out V6.22 in comparison?
You can get it herewhen you click on older versions.

Does that version work for you?

Best regards,
Nino

jiri

Beginner

Date of registration: May 4th 2016

Posts: 6

Location: Prague

8

Wednesday, December 6th 2017, 4:15pm

I got same result with v6.22 as with v6.22a.

Last working version is 6.20i.

This post has been edited 1 times, last edit by "jiri" (Dec 6th 2017, 4:19pm)


SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 430

9

Thursday, December 7th 2017, 11:27am

Hi,

We were able to reproduce the issue and are currently working for a fix.
For now stay with V6.20i for a working setup.

Sorry for any inconveniences caused.

Best regards,
Nino