i2c.master: this port has not been initialized, please initialize it first

[OzerOzdemir]

Hello all. Didn't want to create an issue, as I'm not sure if this error is due to me doing something wrong. I'm getting

E (1244) i2c.master: this port has not been initialized, please initialize it first
I (1264) i2c_bus: i2c0 bus inited
I (1264) i2c_bus: I2C Bus V2 Config Succeed, Version: 1.4.0

error when I call i2c_bus_create(I2C_NUM_0, &conf); Nothing fancy to reproduce. Just the sample code in the main readme is giving me this error message.

Wanted to check here if this message can be ignored, or if I am doing something wrong? It seems like this is coming from the i2c_master code, but I assume the issue is coming from i2c_bus.

I did search for issues, discussions, etc. however did not find anyone else mentioning this error. Should I file an issue to get this fixed?

[YanKE01]

Hi, @OzerOzdemir . You can ignore this error. This design is intended to handle the scenario where the I2C bus is first initialized by the application, and then sensors using the I2C_BUS component attempt to initialize the bus again. If the I2C_BUS component detects that the I2C bus has already been initialized, it will only initialize the resources required by the I2C_BUS component, rather than reinitializing the I2C bus. Devices created by the I2C_BUS component afterward will be attached to the already-initialized bus.

[OzerOzdemir]

Thanks @YanKE01 for the explanation. I'd suggest that this error message be avoided in future versions. Maybe the I2C driver could make the i2c_bus_occupied function public so that the I2c_bus could check before calling i2c_master_get_bus_handle or something similar. This is the only error line we are seeing in a pretty big project on boot up, and it does raise eyebrows.

[YanKE01]

Hi, @OzerOzdemir . This feature was introduced in i2c_bus version 1.3.0. If there are no bus conflicts between i2c_bus and other components in your project, you can revert to version 1.2.0 of i2c_bus to avoid the error messages in the logs. We're currently working on resolving this issue.