You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using I2C on the STM32U585 with Zephyr RTOS, the I2C communication fails with a TIMEOUT error during a write operation. The Logic Analyzer shows no activity on the clock line (SCL) and only a single pulse on the data line (SDA). The observed output is as follows:
Channel 0 (SCL): No activity.
Channel 1 (SDA): Single pulse.
To Reproduce
1.Configure the I2C1 peripheral in the device tree as follows:
2.Ensure that PB6 (SCL) and PB7 (SDA) are properly routed and configured with pull-up resistors on board.
3.Execute a basic i2c_write operation in the application:
uint8_t data[] = {0x01, 0x42};
int ret = i2c_write(i2c_dev, data, sizeof(data), 0x48);
4.Observe the system logs and the Logic Analyzer output.
Expected behavior
The I2C master should generate a complete sequence, including:
A Start Condition on SDA.
Clock pulses on SCL.
The slave address followed by data bytes.
Describe the bug
When using I2C on the STM32U585 with Zephyr RTOS, the I2C communication fails with a TIMEOUT error during a write operation. The Logic Analyzer shows no activity on the clock line (SCL) and only a single pulse on the data line (SDA). The observed output is as follows:
Channel 0 (SCL): No activity.
Channel 1 (SDA): Single pulse.
To Reproduce
1.Configure the I2C1 peripheral in the device tree as follows:
config:
device tree:
2.Ensure that PB6 (SCL) and PB7 (SDA) are properly routed and configured with pull-up resistors on board.
3.Execute a basic i2c_write operation in the application:
4.Observe the system logs and the Logic Analyzer output.
Expected behavior
The I2C master should generate a complete sequence, including:
A Start Condition on SDA.
Clock pulses on SCL.
The slave address followed by data bytes.
Logs and console output
Environment:
MCU: STM32U585
Zephyr Version: 3.6.99
The text was updated successfully, but these errors were encountered: