2020-11-09 06:50 PM
I believe I have found a bug in `HAL_I2C_Master_Transmit`.
The timeout parameter begins counting from the instant the transaction begins, and it doesn't appear that the watchdog is being reset with each incoming byte. Therefore, when you have a long I2C transaction, it will timeout, even if it is working perfectly.
Here is an example with a 250ms timeout:
I would expect the timeout to related to the amount of time the slave device holds the line low, or time between incoming bytes.
I'm using the STM32L4P5G-DK. I would be happy to log the bug, but I don't know where to put it.
Thanks,
Zak
Solved! Go to Solution.
2020-11-10 11:02 AM
This looks rather like a proposal for improvement than a bug. Wait for comments from people interested in this functionality.
Bugs against the L4 HAL library can be reported on github: https://github.com/STMicroelectronics/stm32l4xx_hal_driver/issues
Regards,
-- pa
2020-11-10 11:02 AM
This looks rather like a proposal for improvement than a bug. Wait for comments from people interested in this functionality.
Bugs against the L4 HAL library can be reported on github: https://github.com/STMicroelectronics/stm32l4xx_hal_driver/issues
Regards,
-- pa
2020-11-10 11:42 AM