Moin Leute,
wir haben das Problem, dass wir ein Custom Board nicht mit originalen
J-Link/J-Trace per SWD ansprechen koennen, aber sehr wohl mit onboard
J-Links von anderen Dev-Boards.
Was geht:
- onboard J-Link (umgeflasht) von einem STM32 Discovery
- onboard J-Link von einem Dialog DA1469x Dev-Kit
https://www.dialog-semiconductor.com/products/bluetooth-low-energy/da14695-development-kit-usb
Was nicht geht:
- SEGGER J-Trace PRO
- SEGGER J-Link EDU
J-Trace PRO
1 | SEGGER J-Link GDB Server V7.00 Command Line Version
|
2 | JLinkARM.dll V7.00 (DLL compiled Apr 8 2021 14:33:43)
|
3 |
|
4 | Command line: -if swd -port 50000 -swoport 50001 -telnetport 50002 -device cortex-m33 -rtos GDBServer/RTOSPlugin_FreeRTOS
|
5 | -----GDB Server start settings-----
|
6 | GDBInit file: none
|
7 | GDB Server Listening port: 50000
|
8 | SWO raw output listening port: 50001
|
9 | Terminal I/O port: 50002
|
10 | Accept remote connection: yes
|
11 | Generate logfile: off
|
12 | Verify download: off
|
13 | Init regs on start: off
|
14 | Silent mode: off
|
15 | Single run mode: off
|
16 | Target connection timeout: 0 ms
|
17 | ------J-Link related settings------
|
18 | J-Link Host interface: USB
|
19 | J-Link script: none
|
20 | J-Link settings file: none
|
21 | ------Target related settings------
|
22 | Target device: cortex-m33
|
23 | Target interface: SWD
|
24 | Target interface speed: 4000kHz
|
25 | Target endian: little
|
26 | Connecting to J-Link...
|
27 | J-Link is connected.
|
28 | Firmware: J-Trace PRO V2 Cortex-M compiled Feb 5 2021 14:50:19
|
29 | Hardware: V2.00
|
30 | S/N: xxxxxxxxx
|
31 | Feature(s): RDI, FlashBP, FlashDL, JFlash, GDB
|
32 | Checking target voltage...
|
33 | Target voltage: 3.61 V
|
34 | Listening on TCP/IP port 50000
|
35 | Connecting to target...
|
36 | ERROR: Could not connect to target.
|
umgeflashter J-Link vom STM32Discovery:
1 | SEGGER J-Link GDB Server V7.00 Command Line Version
|
2 | JLinkARM.dll V7.00 (DLL compiled Apr 8 2021 14:33:43)
|
3 |
|
4 | Command line: -if swd -port 50000 -swoport 50001 -telnetport 50002 -device cortex-m33 -rtos GDBServer/RTOSPlugin_FreeRTOS
|
5 | -----GDB Server start settings-----
|
6 | GDBInit file: none
|
7 | GDB Server Listening port: 50000
|
8 | SWO raw output listening port: 50001
|
9 | Terminal I/O port: 50002
|
10 | Accept remote connection: yes
|
11 | Generate logfile: off
|
12 | Verify download: off
|
13 | Init regs on start: off
|
14 | Silent mode: off
|
15 | Single run mode: off
|
16 | Target connection timeout: 0 ms
|
17 | ------J-Link related settings------
|
18 | J-Link Host interface: USB
|
19 | J-Link script: none
|
20 | J-Link settings file: none
|
21 | ------Target related settings------
|
22 | Target device: cortex-m33
|
23 | Target interface: SWD
|
24 | Target interface speed: 4000kHz
|
25 | Target endian: little
|
26 | Connecting to J-Link...
|
27 | J-Link is connected.
|
28 | Firmware: J-Link STLink V21 compiled Aug 12 2019 10:29:20
|
29 | Hardware: V1.00
|
30 | S/N: 771848496
|
31 | Checking target voltage...
|
32 | Target voltage: 3.30 V
|
33 | Listening on TCP/IP port 50000
|
34 | Connecting to target...
|
35 | Connected to target
|
36 | Waiting for GDB connection...Connected to 127.0.0.1
|
37 | Reading all registers
|
Wir haben es auch schon mit Widerstaenden (150 + 330) in den SWD
Leitungen versucht: kein Erfolg. Die SWD Belegung des J-Trace (Pin 1, 2,
4 und ein GND) habe ich von hier entnommen:
https://www.segger.com/products/debug-probes/j-trace/models/j-trace/#gallery-1
Habt ihr vielleicht eine Idee, was hier das Problem sein koennte? :-/
Beste Gruesse und einen schoenen Sonntagabend.