Timeout parameter in HAL_I2C_Master_Receive/HAL_I2C_Mem_Read not used for I2C_WaitOnFlagUntilTimeout function about stm32g0xx_hal_driver

[KRASTM]

Hello @Kedrel,

Thank you for the report.

The Timeout used in I2C_WaitOnFlagUntilTimeout for the 2 functions HAL_I2C_Master_Receive & HAL_I2C_Mem_Read is sufficient to check if the peripheral still busy.

Otherwise, can you share more details about your scenario or project?

With regards.

[Kedrel]

Hello @KRASTM,

The system i'm working on currently uses a tick of 10 ms to run the whole process. The aim is never to have a task that exceends 10ms so we can handle the "real-time" properly.

When i call "HAL_I2C_Mem_Read" using a Timeout parameter at 2 ms, inside of it we have the call of "I2C_WaitOnFlagUntilTimeout" which uses a parameter of I2C_TIMEOUT_BUSY, which is 25ms.

So if an I2C peripheral can't respond, instead of loosing 2ms of wait time like the setting i chose, i'll loose 25ms.

I can't afford to loose 25ms like that (as i have multiple I2C sensors), so i'll change the I2C_TIMEOUT_BUSY value to something acceptable for my application.

With regards.

[KRASTM]

Hello @Kedrel,

In this particular case, it is possible to modify the value of I2C_TIMEOUT_BUSY to suit your application.
Please allow me to close this issue. Thank you for your comprehension.

With regards.