AnsweredAssumed Answered

STM32Cube - BUG report : DeadTime is missing while configuring advanced TIM8.

Question asked by Stivy on Jul 11, 2014
Latest reply on Jul 28, 2014 by STM32Cube-T

I'm using STM32CubeMX for a STM32F205 MCU.

There is a problem with the use of the TIM8 configuration, regarding BDTR config register.

The DeadTime does not appear in the config of TIM8. And then, its code is not generated either. 
The problem is that in the libraries, sBreakDeadTimeConfig.Deadtime is not initialised ; and then it contains a random value at reset. 

Since the initialisation of the register is made like this : 

  htim->Instance->BDTR = (uint32_t)sBreakDeadTimeConfig->OffStateRunMode  | 
                                   sBreakDeadTimeConfig->OffStateIDLEMode |
                                   sBreakDeadTimeConfig->LockLevel        |
                                   sBreakDeadTimeConfig->DeadTime         |
                                   sBreakDeadTimeConfig->BreakState       |
                                   sBreakDeadTimeConfig->BreakPolarity    |

You can understand that after initialisation, the whole BDTR register is randomly filled.. and the the TIM output can give you very weird behaviours when you are not aware of this problem. 

I don't know if we have the same problem with TIM1, it should be check too.

Can the ST team : 
 - confirm that it is a bug ?
 - let us know when it will be fixed ?
 - let us know when is planned the next update ?