Skip to main content
DM.7
Associate II
February 23, 2023
Solved

F746 Disco - Why does TIM6 trigger and stop application running in init

  • February 23, 2023
  • 4 replies
  • 1763 views

I have used CubeMX to generate an application structure for the STM32F746 DISCO board.

When trying to run the most basic application, during the initialisation, TIM6 is set to be the HAL tick source, when it is enabled, it immediately jumps to its interrupt, and then gets repeated called, stopping any further progress.

This is also happening with the TouchGFX code taken from the example library.

This topic has been closed for replies.
Best answer by KnarfB

Add few lines in main after HAL_Init();

 /* USER CODE BEGIN Init */
 // configure peripherals to pause when a debugger is paused
 // this also mitigates an erratum of the Cortex-M7 r0p1 core: https://developer.arm.com/documentation/ka002944/latest
 (DBGMCU)->APB1FZ = 0xFFFFFFFF;
 (DBGMCU)->APB2FZ = 0xFFFFFFFF;
 /* USER CODE END Init */

this has been discussed here before, so you might search for more detailed explanations.

hth

KnarfB

4 replies

KnarfB
KnarfBBest answer
Super User
February 24, 2023

Add few lines in main after HAL_Init();

 /* USER CODE BEGIN Init */
 // configure peripherals to pause when a debugger is paused
 // this also mitigates an erratum of the Cortex-M7 r0p1 core: https://developer.arm.com/documentation/ka002944/latest
 (DBGMCU)->APB1FZ = 0xFFFFFFFF;
 (DBGMCU)->APB2FZ = 0xFFFFFFFF;
 /* USER CODE END Init */

this has been discussed here before, so you might search for more detailed explanations.

hth

KnarfB

DM.7
DM.7Author
Associate II
February 27, 2023

Thanks. This was the issue

Peter BENSCH
ST Technical Moderator
February 24, 2023

@DM.7​ You can find more information e.g. here.

Good luck!

Regards

/Peter

In order to give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
DM.7
DM.7Author
Associate II
February 27, 2023

Hi. Thanks. Should this information not be included in the chip's errata document?