Now I try to use ST-link V2 to debug in AC3 System Workbench, but can't debug.
You can try to upgrade the STLink firmware first, you have JTAG v17 which is an old version.
You can do this with stlink upgrade tool available on st web site.
Then, for the debug, it is better to connect the Reset line comming from STlink to target mcu.
If you can't, use the "software reset system" in SW4STM32 debug configuration (debugger tab and click "show generator options").
Add more information, just DIO, CLK, GND connectioned between ST-link V2 and STM32F103 board.
From the latest error, seems that just reset and halt issue, but I enable & disable Rest and Halt setting, the error is same.
Need NRST connected for Reset connection options to function.
Not really, the choice "software system reset" is indeed not using the reset line.
But it is preferable to connect Reset line to avoid being blocked if using SWD pins as GPIOs or low power modes in your appli...
Or even if you want to use the Reset button on your Ide.
Is there a robustness issue with OpenOCD, GDB and ST-LINK that ST could put some engineering resources behind? Seems to be more fragile than the IAR and Keil implementations.
The application of current drivers and firmware seems to be something that could get addressed directly in the installation of SW4STM32. Tightening up things in this regard could substantially reduce the support burden, especially when dealing with simple/repetitive issues.
Do you means that update STJlink firmware using the below SW?
You can use this way if the Stlink utility software is not too old.
I was refering to the appli stlink fw upgrade available here :
Retrieving data ...