AnsweredAssumed Answered

STM32Cube_FW_F4_V1.8.0 I2C hardcoded timeout, why?

Question asked by krasutski.denis on Oct 20, 2015
Latest reply on Oct 29, 2015 by krasutski.denis
Hello,
I updated ST library and got huge delay during I2C transfers when I have some errors. previously I manage timeouts in my firmware now some timeout hardcoded for example:

#define I2C_TIMEOUT_FLAG          ((uint32_t)35)     /* 35 ms */
#define I2C_TIMEOUT_ADDR_SLAVE    ((uint32_t)10000)  /* 10 s  */
#define I2C_TIMEOUT_BUSY_FLAG     ((uint32_t)10000)  /* 10 s  */
 
Can you explain, why ST added it?
Previous library version used function argument.

Do you have plans remove this? Because if I use this function whith RTOS in HI priority task when happaned error will block all system on 10sec. it is not permissible.

BR,
Denis Krasutski

Outcomes