Posted by fcgehrke on 2015-07-31 03:45

To make the debug work you can Erase the chip on the STM32 STLINK Software, it should work.

I had this problem. There was a configuration problem, I looked to the assert functions and it was to pointing to ‘0’ which I believe that resets the microcontroller. Then, I activated the FULL_ASSERT and then I could see what was wrong. In my case it was a GPIO configuration problem. I forgot to put the pulls (I thought that it was not necessary, it’s outputs) on the GPIO_InitTypeDef structure. After I did that, the debug was working.

You can try this solution, but don’t forget to Erase the chip before.

Posted by elgarbe on 2016-08-14 01:27

I have de same problem
I could connect with st link utility but now with system workbench to debug my application

this is the code

1. include “stm32f0xx.h”

volatile uint32_t counter = 0;
int main( void ) {

HAL_Init();

GPIO_InitTypeDef GPIO_InitStruct;

/* GPIO Ports Clock Enable */
__GPIOA_CLK_ENABLE();

/*Configure GPIO pins : PAPin PAPin */
GPIO_InitStruct.Pin = GPIO_PIN_4;
GPIO_InitStruct.Mode = GPIO_MODE_OUTPUT_PP;
GPIO_InitStruct.Pull = GPIO_NOPULL;
HAL_GPIO_Init(GPIOA, &GPIO_InitStruct);

while(1)
{
HAL_GPIO_TogglePin(GPIOA, GPIO_PIN_4);
for(counter=0; counter