Skip to main content
Visitor II
November 10, 2020
Solved

Where do you log bugs discovered in the `HAL_`?

  • November 10, 2020
  • 2 replies
  • 992 views

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:

0693W000005ArrIQAS.png 

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

    This topic has been closed for replies.
    Best answer by Pavel A.

    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

    2 replies

    Pavel A.Answer
    Super User
    November 10, 2020

    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

    ZakAuthor
    Visitor II
    November 10, 2020