Sunday, January 21st 2018, 7:47pm UTC+1

You are not logged in.

  • Login
  • Register

gsvftl

Beginner

Date of registration: Jan 12th 2018

Posts: 1

1

Friday, January 12th 2018, 9:54am

CCS/TMS570LS0714: Error: Stat [ JLINKARM_IsHalted() call ] failed!

Hi!

I have a custom board with a TMS570LS0714 that was put together for the first time. I'm trying to upload code to it using the J-Link EDU via Code Composer Studio's J-Link integration, but it seems there's a problem with the connection.

Platform: Arch Linux x86_64
Kernel: 4.14.13-1-ARCH
Code Composer Studio: 7.4.0.00015
Code Composer Studio J-Link Support: 6.20.9.0
Segger product: J-Link EDU
MCU: TMS570LS0714

Output from Code Composer Studio's console (within the IDE)

Source code

1
2
3
CortexR4: Error: Stat [ JLINKARM_IsHalted() call ] failed!
CortexR4: Unable to determine target status after 20 attempts
CortexR4: GEL Output: Memory Map Setup for Flash @ Address 0x0


stdout from ~/ti/ccsv7/eclipse/ccstudio (lots of these)

Source code

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
*** J-Link V6.20i Executing PCode ***
Can not find ICE-Pick (IRLen mismatch). Expected 0x00000006, found: 0x00000280
*** J-Link V6.20i Executing PCode ***



*** J-Link V6.20i Executing PCode ***
Can not find ICE-Pick (IDCODE mismatch). Expected 0xXXXXXX2F, found: 0x00000000
*** J-Link V6.20i Executing PCode ***



*** J-Link V6.20i Executing PCode ***
Can not find ICE-Pick (IRLen mismatch). Expected 0x00000006, found: 0x00000280
*** J-Link V6.20i Executing PCode ***



*** J-Link V6.20i Executing PCode ***
Can not find ICE-Pick (IDCODE mismatch). Expected 0xXXXXXX2F, found: 0x00000000
*** J-Link V6.20i Executing PCode ***


Also tried connecting with the official standalone binaries.

Output from JLinkExe

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
$ ./JLink_Linux_V622e_x86_64/JLinkExe
SEGGER J-Link Commander V6.22a (Compiled Nov 28 2017 17:57:05)
DLL version V6.22a, compiled Nov 28 2017 17:57:00

Connecting to J-Link via USB...O.K.
Firmware: J-Link V9 compiled Dec  1 2017 14:40:21
Hardware version: V9.30
S/N: 269304666
License(s): FlashBP, GDB
OEM: SEGGER-EDU
VTref = 0.000V

...

J-Link>connect
Please specify device / core. <Default>: TMS570LS0714
Type '?' for selection dialog
Device>TMS570LS0714
Device "TMS570LS0714" selected.


Connecting to target via JTAG
Executing InitTarget()
TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
0x00000280
J-Link script: ICEPick found, enabling Cortex-M3 core.
Can not find ICE-Pick (IDCODE mismatch). Expected 0x0000002F, found: 0x00000000
TMS570/RM4x (connect): Can not find Cortex-M3 (IDCODE mismatch)
Executing InitTarget()
TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
0x00000280
J-Link script: ICEPick found, enabling Cortex-M3 core.
Can not find ICE-Pick (IDCODE mismatch). Expected 0x0000002F, found: 0xA0002108
TMS570/RM4x (connect): Can not find Cortex-M3 (IDCODE mismatch)

****** Error: InitTarget(): PCode returned with error code -1

Executing InitTarget()
TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
0x00000280
J-Link script: ICEPick found, enabling Cortex-M3 core.
Can not find ICE-Pick (IDCODE mismatch). Expected 0x0000002F, found: 0xA0002108
TMS570/RM4x (connect): Can not find Cortex-M3 (IDCODE mismatch)
Executing InitTarget()
TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
0x00000280
J-Link script: ICEPick found, enabling Cortex-M3 core.
Can not find ICE-Pick (IDCODE mismatch). Expected 0x0000002F, found: 0xA0002108
TMS570/RM4x (connect): Can not find Cortex-M3 (IDCODE mismatch)

****** Error: InitTarget(): PCode returned with error code -1

Cannot connect to target.


Any tips on what to check?

We've also created a corresponding thread on TI's forum: https://e2e.ti.com/support/development_t…o/f/81/t/619076

Thanks.

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 566

2

Monday, January 15th 2018, 10:42am

Hello,

Thank you for your inquiry.
Such an issue is not known to us.

From the logs it reads: VTref = 0.000V

This indicates that Pin 1 of the J-Link interface is not connected to the target voltage supply correctly.
More information can be found here: https://wiki.segger.com/J-Link_cannot_co…VTref_is_0.000V

Best regards,
Nino