Skip to main content
anonymous.8
Senior II
Sep 5, 2019 1:56 PM UTC
Solved

HAL CubeMX I2C START problem.

-----I FOUND THE ANSWER MYSELF. ----------

Technical environment :

-       Master : STM32F767

-       Slave : M24256 EEPROM on custom board. SCL and SDA on PH4 and PH5 with 4.7K pull-ups

-       CubeMX : V5.3.0

-       Normal transaction is : MASTER do a 3 bytes WRITE

HAL_I2C_Master_Transmit calls I2C_TransferConfig. Immediately after CR2 update two flags in ISR are set: STOPF ana NACKF. Write timeouts in I2C_WaitOnTXISFlagUntilTimeout. Logic analyzer does not show any activity. Both signals are high. Any ideas where to search for problem?

This topic has been closed for replies.
anonymous.8
anonymous.8Best answer
Senior II
Sep 9, 2019 7:59 AM UTC

There were two I2Cs. I just mixed the handle.

1 reply

anonymous.8
anonymous.8AuthorBest answer
Senior II
Sep 9, 2019 7:59 AM UTC

There were two I2Cs. I just mixed the handle.