how to use st-LINK v2 in Ac6 System Workbench for STM32 environment?

[kent gu]

Posted on November 29, 2017 at 10:00

Hi?

 Now I try to use ST-link V2 to debug in AC3 System Workbench, but can't  debug.  

Best Regards,

Kent

#system-workbench-ide #debug-stm32-using-st-link/v2

[kent gu]

Posted on November 30, 2017 at 05:58

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.

Best Regards,

Kent

[LaurentL · Accepted solution]

Posted on November 30, 2017 at 10:33

Hi,

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').

Rgds,

Laurent

[kent gu]

Posted on November 30, 2017 at 13:39

Laurent,

Do you means that update STJlink firmware using the below SW?

Best Regards,

Kent

[LaurentL]

Posted on November 30, 2017 at 14:15

Hi,

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 :

http://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/stsw-link007.html

Rgds,

Laurent

[Tesla DeLorean]

Posted on November 30, 2017 at 14:33

Need NRST connected for Reset connection options to function.

[LaurentL]

Posted on November 30, 2017 at 14:43

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.

Rgds,

Laurent

[Tesla DeLorean]

Posted on November 30, 2017 at 16:41

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.

[dan239955_st]

I have the same problem on a STM32F746BGT6. I updated the F/W on ST-Link/V2. And still can not debug my board. FRUSTRATING!