Hello Team,
we have connected L89H GNSS module to the verdin imx8mp board via I2C_1_SDA and I2C_1_SCL (generic i2c-4).
connected i2c to the level shifter and able to see that i2c is draining by 3.3v
Able to connect the module and able to detect it on the i2c bus.
we are facing the issue while running sample code provided by the Quectel.
Raised a query in the Quectel forms and they suggest that the issue is due to i2c connectivity issue
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Hello there!
I understand you’re experiencing some challenges with I2C connectivity on your Verdin iMX8M Plus. Let’s work through this together.
-
Hardware Verification:
- The I2C_1_SDA and I2C_1_SCL pins on the Verdin iMX8M Plus operate at 1.8V. Your setup with a level shifter to 3.3V is appropriate for ensuring compatibility with external devices. You can find more details in the Verdin iMX8M Plus documentation.
-
Software Access:
- If you’re executing the sample code within a container, it’s crucial to ensure that the I2C device access permissions are correctly configured. You might need to:
- Mount the
/devdirectory into the container. - Add the necessary device cgroup rule for I2C access.
- Utilize the standardized symbolic links for I2C devices. More information can be found in this community discussion.
- Mount the
- If you’re executing the sample code within a container, it’s crucial to ensure that the I2C device access permissions are correctly configured. You might need to:
-
Testing Connectivity:
- Before running the Quectel sample code, it’s a good idea to use
i2c-toolsto verify basic I2C communication and ensure the device is detected correctly. This step can help confirm that the hardware connection is functioning as expected.
- Before running the Quectel sample code, it’s a good idea to use
Since you mentioned that the device is detectable on the I2C bus but issues arise with the sample code, it seems the hardware is set up correctly, and the problem might lie in the software configuration.
Could you please provide more details on:
- How you are running the sample code (in a container or directly on the system)?
- Any specific error messages you are encountering?
- The results from basic I2C detection tools?
These details will help us pinpoint whether the issue is related to permissions, configuration, or the communication protocol.
Looking forward to your response!
Best regards,
Toradex AI Assistant.