2023-07-02 08:18 AM
I recently update my STM32L4 HAL library from 1.9 to 1.13. After that, using the
Solved! Go to Solution.
2023-07-05 03:15 AM
Hello @onderdelen ,
Thank you for reporting this issue.
It will be fixed soon.
Foued
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.
2023-07-02 08:45 AM
I applied a fix to the driver by setting the XferSize member variable to 0. Doing this made the ISR routine perform without any errors, and my application runs again without problems.:
I reckon this fix, if valid, should also be applied to the the HAL_I2C_Mem_Read_IT function.
Perhaps someone from ST can comment on this?
With best regards,
Ewout Boks
2023-07-05 03:15 AM
Hello @onderdelen ,
Thank you for reporting this issue.
It will be fixed soon.
Foued
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.
2023-07-05 07:09 AM
Hi,
Thanks for your reply. My take on it is that the XferSize variable holds a value after an I2C transfer. Then, when doing the next transfer the old value would be in the way and interfere with the new setup in the HAL function, which splits the transfer in a few parts using the RELOAD feature of the I2C hardware. The reset of XferSize to 0 is required.