This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

I2C clock stretching on nrf52840

Hello !

I would like to know if the nrf52840 is affected by the errata https://infocenter.nordicsemi.com/topic/errata_nRF52832_Rev2/ERR/nRF52832/Rev2/latest/anomaly_832_149.html#anomaly_832_149 or something similar ?
(I did not find it in the 52840 errata)

I am struggling to communicate with a 100KHz i2c device which require clock stretching to work. The communication often hang forever.
It sometimes work, the difference seems to be the lenght of the first clock after a stretch.

A non working screenshot :

A working screenshot:


If this is the same issue as the 832 errata, is there a known workarround ?

Thank you for your help.

Parents
  • Hi,

    It was worth a test, but then it looks like this timing is indeed in hardware on both the legacy and Easydma, and can't be changed no. I assume you have two options, either use a bit bang software I2C implementation and/or look into whether a different serial interface may be used (and/or switch direction of the interface in some way).

    Sorry for this, but it is the first I have heard that this have caused an third party device to actually fail.

    Best regards,
    Kenneth

Reply
  • Hi,

    It was worth a test, but then it looks like this timing is indeed in hardware on both the legacy and Easydma, and can't be changed no. I assume you have two options, either use a bit bang software I2C implementation and/or look into whether a different serial interface may be used (and/or switch direction of the interface in some way).

    Sorry for this, but it is the first I have heard that this have caused an third party device to actually fail.

    Best regards,
    Kenneth

Children
No Data
Related