AnsweredAssumed Answered

Debugging issues with STM32CubeMX for STM32F100RCT MCU generated project in Atollic

Question asked by Anani Popov on Jun 6, 2017
Latest reply on Jun 22, 2017 by Anani Popov

I am having issues when debugging STM32CubeMX for STM32F100RCT MCU generated project in Atollic. The ST-Link debugger jumps to unknown code location and generated HW fault exception. It happens with Cube generated peripheral INI HAL like TIM16, TIM17 and SPI1 as well. Usually in TIMx cases it happens when tmpcr1=TIMx->CR1; line in HAL {void TIM_Base_SetConfig(TIM_TypeDef *TIMx, TIM_Base_InitTypeDef *Structure)} function is executed. In the SPI1 failure case it happens when __HAL_AFIO_REMAP_SPI1_ENABLE() macro is called. I am using Cube App V4.21, FW V.1.4 and Atollic 7.1.2 Lite. Any idea? Please help.

Outcomes