[ABANDONED] J-Link v10.x only works in SWD mode, older J-Links also work with JTAG mode

mwb1100 · May 4, 2021 at 5:20 PM

I've run into something curious with v10.x J-Links. I have a project using the STM32F103ZG microcontroller and I'm currently using IAR EWARM 9.1.

Flashing and debugging with older J-Links (v8, v9.1 and Ultra v4.3) work just fine in either JTAG or SWD mode - JTAG has been the default since the beginning. However, when some people started using v10.0 or v10.1 J-Link, flash and debug would only work in SWD mode.

As an example, here's the Debug log from when I try to "Debug without download" using a v10.1 J-Link with JTAG configured instead of SWD. The J-Link's LED quickly flashes red/yellow (or red/green?) and I get a message "Failed to get CPU status after 4 retries".

Code

Tue May 04, 2021 07:58:28: IAR Embedded Workbench 9.10.1 (C:\Program Files\IAR Systems\Embedded Workbench 9.0\arm\bin\armPROC.dll) 
Tue May 04, 2021 07:58:28: Loaded macro file: C:\Program Files\IAR Systems\Embedded Workbench 9.0\arm\config\debugger\ST\STM32F1xx.dmac 
Tue May 04, 2021 07:58:28: JLINK command: ProjectFile = C:\devtrees\obfuscated\settings\obfuscated_Debug.jlink, return = 0 
Tue May 04, 2021 07:58:28: Device "STM32F103ZG" selected. 
Tue May 04, 2021 07:58:28: DLL version: V6.94d, compiled Feb 12 2021 15:56:38 
Tue May 04, 2021 07:58:28: Firmware: J-Link V10 compiled Apr 27 2021 16:35:48 
Tue May 04, 2021 07:58:28: JTAG speed is initially set to: 32 kHz 
Tue May 04, 2021 07:58:28: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:28: STM32 (connect): Can not attach to CPU. Trying connect under reset. 
Tue May 04, 2021 07:58:28: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:28: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:28: STM32 (connect): Can not attach to CPU. Trying connect under reset. 
Tue May 04, 2021 07:58:28: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:28: Warning: STM32: Connecting to CPU via connect under reset failed. 
Tue May 04, 2021 07:58:28: Hardware reset with strategy 0 was performed 
Tue May 04, 2021 07:58:28: Initial reset was performed 
Tue May 04, 2021 07:58:28: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:28: STM32 (connect): Can not attach to CPU. Trying connect under reset. 
Tue May 04, 2021 07:58:28: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:28: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:28: STM32 (connect): Can not attach to CPU. Trying connect under reset. 
Tue May 04, 2021 07:58:28: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:29: Warning: STM32: Connecting to CPU via connect under reset failed. 
Tue May 04, 2021 07:58:29: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:29: STM32 (connect): Can not attach to CPU. Trying connect under reset. 
Tue May 04, 2021 07:58:29: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:29: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:29: STM32 (connect): Can not attach to CPU. Trying connect under reset. 
Tue May 04, 2021 07:58:29: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:29: Warning: STM32: Connecting to CPU via connect under reset failed. 
Tue May 04, 2021 07:58:29: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:29: STM32 (connect): Can not attach to CPU. Trying connect under reset. 
Tue May 04, 2021 07:58:29: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:29: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:29: STM32 (connect): Can not attach to CPU. Trying connect under reset. 
Tue May 04, 2021 07:58:29: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:29: Warning: STM32: Connecting to CPU via connect under reset failed. 
Tue May 04, 2021 07:58:29: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:29: STM32 (connect): Can not attach to CPU. Trying connect under reset. 
Tue May 04, 2021 07:58:29: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:30: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:30: STM32 (connect): Can not attach to CPU. Trying connect under reset. 
Tue May 04, 2021 07:58:30: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:30: Warning: STM32: Connecting to CPU via connect under reset failed. 
Tue May 04, 2021 07:58:30: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:30: STM32 (connect): Can not attach to CPU. Trying connect under reset. 
Tue May 04, 2021 07:58:30: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:30: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:30: STM32 (connect): Can not attach to CPU. Trying connect under reset. 
Tue May 04, 2021 07:58:30: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:30: Warning: STM32: Connecting to CPU via connect under reset failed. 
Tue May 04, 2021 07:58:30: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:30: STM32 (connect): Can not attach to CPU. Trying connect under reset. 
Tue May 04, 2021 07:58:30: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:30: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:30: STM32 (connect): Can not attach to CPU. Trying connect under reset. 
Tue May 04, 2021 07:58:30: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:30: Warning: STM32: Connecting to CPU via connect under reset failed. 
Tue May 04, 2021 07:58:30: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:30: STM32 (connect): Can not attach to CPU. Trying connect under reset. 
Tue May 04, 2021 07:58:31: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:31: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:31: STM32 (connect): Can not attach to CPU. Trying connect under reset. 
Tue May 04, 2021 07:58:31: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:31: Warning: STM32: Connecting to CPU via connect under reset failed. 
Tue May 04, 2021 07:58:31: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:31: STM32 (connect): Can not attach to CPU. Trying connect under reset. 
Tue May 04, 2021 07:58:31: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:31: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:31: STM32 (connect): Can not attach to CPU. Trying connect under reset. 
Tue May 04, 2021 07:58:31: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:31: Warning: STM32: Connecting to CPU via connect under reset failed. 
Tue May 04, 2021 07:58:31: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:31: STM32 (connect): Can not attach to CPU. Trying connect under reset. 
Tue May 04, 2021 07:58:31: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:31: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:31: STM32 (connect): Can not attach to CPU. Trying connect under reset. 
Tue May 04, 2021 07:58:32: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:32: Warning: STM32: Connecting to CPU via connect under reset failed. 
Tue May 04, 2021 07:58:32: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:32: STM32 (connect): Can not attach to CPU. Trying connect under reset. 
Tue May 04, 2021 07:58:32: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:32: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:32: STM32 (connect): Can not attach to CPU. Trying connect under reset. 
Tue May 04, 2021 07:58:32: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:32: Warning: STM32: Connecting to CPU via connect under reset failed. 
Tue May 04, 2021 07:58:32: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:32: STM32 (connect): Can not attach to CPU. Trying connect under reset. 
Tue May 04, 2021 07:58:32: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:32: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:32: STM32 (connect): Can not attach to CPU. Trying connect under reset. 
Tue May 04, 2021 07:58:32: TotalIRLen = 9, IRPrint = 0x0011 
Tue May 04, 2021 07:58:32: Warning: STM32: Connecting to CPU via connect under reset failed. 
Tue May 04, 2021 08:00:47: Unloaded macro file: C:\Program Files\IAR Systems\Embedded Workbench 9.0\arm\config\debugger\ST\STM32F1xx.dmac 
Tue May 04, 2021 08:00:47: IAR Embedded Workbench 9.10.1 (C:\Program Files\IAR Systems\Embedded Workbench 9.0\arm\bin\armPROC.dll) 
Tue May 04, 2021 08:00:47: Loading the jlink driver

Display More

This isn't a problem in the sense that simply changing to SWD works. But it was unexpected and there are some worries that maybe the JTAG isn't correct on the schematic/PCB layout (I'm not an EE so I can't begin to guess what's going on there - if anything). This happens with both a v10.0 and v10.1 J-Link. All older J-Links I've tried work fine in JTAG mode (and SWD mode).

For comparison, I have also attached a debug log of a J-Link Ultra+ v4.3 successfully using JTAG mode.

I'm wondering if this is something we should be concerned about, and if so do you have any suggestions for where we should look?

SEGGER - Fabian · May 7, 2021 at 3:04 PM

Hi,
Thank you for your inquiry.
We are not aware of any issues related to the STM32F1 series and JTAG.

I just gave this a quick try and it seems to be working without any issues on an STM32F10X-128K-EVAL board (STM32F103V8):

Do you experience the same issue on an evaluation board?
Could you please send us a J-Link log file? How to enable:
https://wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File

Best regards,
Fabian

mwb1100 · May 20, 2021 at 12:54 AM

Sorry for my delayed response (I didn't get or I missed an email notification).

I will try your suggestions, but it might be a while as I'm up against a deadline right now. The J-Link v10 does work on these boards in SWD mode, so the problem is just an annoyance so far.

I did do a J-Link session to connect and the v10.1 J-Link worked as well as you session did. Some time in the next week or so, I'll try updating the DLL that is used in IAR to the 7.2 version and see if that makes a difference.

My jlink.exe session that connects successfully:

Code

C:\Program Files (x86)\SEGGER\JLink_V720>jlink
SEGGER J-Link Commander V7.20 (Compiled Apr 28 2021 17:35:36)
DLL version V7.20, compiled Apr 28 2021 17:34:08


Connecting to J-Link via USB...O.K.
Firmware: J-Link V10 compiled Apr 27 2021 16:35:48
Hardware version: V10.10
S/N: 50100825
License(s): GDB
VTref=0.000V




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




Connecting to target via JTAG
InitTarget() start
InitTarget() end
TotalIRLen = 9, IRPrint = 0x0011
JTAG chain detection found 2 devices:
 #0 Id: 0x3BA00477, IRLen: 04, CoreSight JTAG-DP
 #1 Id: 0x06430041, IRLen: 05, STM32 Boundary Scan
DPv0 detected
Scanning AP map to find all available APs
AP[1]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x14770011)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x411FC231. Implementer code: 0x41 (ARM)
Found Cortex-M3 r1p1, Little endian.
FPUnit: 6 code (BP) slots and 2 literal slots
CoreSight components:
ROMTbl[0] @ E00FF000
ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 001BB000 SCS
ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 001BB002 DWT
ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 000BB003 FPB
ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 001BB001 ITM
ROMTbl[0][4]: E0040000, CID: B105900D, PID: 001BB923 TPIU-Lite
ROMTbl[0][5]: E0041000, CID: B105900D, PID: 101BB924 ETM-M3
Cortex-M3 identified.
J-Link>

Display More

My log looks pretty much identical to yours except for the DLL version used and this line near the end that is in my log but not yours:

ROMTbl[0][5]: E0041000, CID: B105900D, PID: 101BB924 ETM-M3

I have no idea what it indicates or if it's at all significant.

[ABANDONED] J-Link v10.x only works in SWD mode, older J-Links also work with JTAG mode

Participate now!

Users Viewing This Thread