JTAG /SWD Verbindungsproblem zu TM4C129ENCPDT

[Simon (Gast)]

JLinkExe -device TM4C129ENCPDT -if SWD -speed 4000
SEGGER J-Link Commander V5.12c (Compiled Apr 21 2016 16:22:45)
DLL version V5.12c, compiled Apr 21 2016 16:22:40

Connecting to J-Link via USB...O.K.
Firmware: J-Link V9 compiled Mar 29 2016 18:46:37
Hardware version: V9.30
License(s): FlashBP, GDB
OEM: SEGGER-EDU
VTref = 3.280V


Type "connect" to establish a target connection, '?' for help
J-Link>connect
Device "TM4C129ENCPDT" selected.


Found SWD-DP with ID 0x2BA01477
Found Cortex-M4 r0p1, Little endian.
FPUnit: 6 code (BP) slots and 2 literal slots
CoreSight components:
ROMTbl 0 @ E00FF000
ROMTbl 0 [0]: FFF0F000, CID: B105E00D, PID: 000BB00C SCS
ROMTbl 0 [1]: FFF02000, CID: B105E00D, PID: 003BB002 DWT
ROMTbl 0 [2]: FFF03000, CID: B105E00D, PID: 002BB003 FPB
ROMTbl 0 [3]: FFF01000, CID: B105E00D, PID: 003BB001 ITM
ROMTbl 0 [4]: FFF41000, CID: B105900D, PID: 000BB9A1 TPIU
ROMTbl 0 [5]: FFF42000, CID: B105900D, PID: 000BB925 ETM
Cortex-M4 identified.




Es sieht ja so aus als ob die Verbindung klappt, aber dann beim Starten 
des GDB servers:


JLinkGDBServer -device TM4C129ENCPDT -if JTAG -speed 1000
SEGGER J-Link GDB Server V5.12c Command Line Version

JLinkARM.dll V5.12c (DLL compiled Apr 21 2016 16:22:40)

-----GDB Server start settings-----
GDBInit file:                  none
GDB Server Listening port:     2331
SWO raw output listening port: 2332
Terminal I/O port:             2333
Accept remote connection:      yes
Generate logfile:              off
Verify download:               off
Init regs on start:            off
Silent mode:                   off
Single run mode:               off
Target connection timeout:     0 ms
------J-Link related settings------
J-Link Host interface:         USB
J-Link script:                 none
J-Link settings file:          none
------Target related settings------
Target device:                 TM4C129ENCPDT
Target interface:              JTAG
Target interface speed:        1000kHz
Target endian:                 little

Connecting to J-Link...
J-Link is connected.
Firmware: J-Link V9 compiled Mar 29 2016 18:46:37
Hardware: V9.30
OEM: SEGGER-EDU
Feature(s): FlashBP, GDB
Checking target voltage...
Target voltage: 3.28 V
Listening on TCP/IP port 2331
Connecting to target...
J-Link found 1 JTAG device, Total IRLen = 4
JTAG ID: 0x4BA00477 (Cortex-M4)
WARNING: CPU could not be halted
ERROR: Could not connect to target.
Target connection failed. GDBServer will be closed...Restoring target 
state and closing J-Link connection...
Shutting down...
Could not connect to target.
Please check power, connection and settings.







Ich würde das ganze mal aus dem Ti Code Composer heraus Probieren nur da 
scheitert die Installation komplett

[Jim M. (turboj)]

Könntest Du nach dem "connect" ein "halt" oder "reset" ausprobieren?

[Simon (Gast)]

Ja,

Cortex-M4 identified.
J-Link>halt

**************************
WARNING: CPU could not be halted
**************************


J-Link>reset
Unknown command. '?' for help.
J-Link>r
Reset delay: 0 ms
Reset type NORMAL: Resets core & peripherals via SYSRESETREQ & VECTRESET 
bit.
J-Link>

[Simon (Gast)]

Was ich mich auch Frage wie der reset Pin angeschlossen wird.

Laut https://www.segger.com/interface-description.html
habe ich zwei Reset Signale nTRST (J-Link Pin 3) und RESET (J-Link Pin 
15)

Ich habe den RESET (J-Link Pin 15) an den TM4C129ENCPDT  RST (Pin 70) 
über 100R Angeschlossen.
Dazu kommt 100nF zu GND und 10k PullUp

[Simon (Gast)]

Ich hab das ganze nochmal unter Windows probiert.

Selbes Problem. was mir aber auffällt wenn ich erst ein "r" für reset in 
die JLinkExe.exe eingebe dann funktioniert auch ein halt.