Getting Data from I2C via Interrupt With MPU-6050

RE: Getting Data from I2C via Interrupt With MPU-6050

Toastus — Sat, 13 Sep 2025 23:37:48 GMT

Vidar Berg is correct. See the Zephyr page link below (latest api) for details on open-drain vs. OPEN_SOURCE and high/low signals. In essence, INT_OPEN, which corresponds to the latest nRF SDK GPIO_OPEN_DRAIN will essentially ground the pin (forcing it inactive in your setup), while open-source (GPIO_OPEN_SOURCE on nRF chips) will allow the pin to go high or low, acting as a signal source.

docs.zephyrproject.org/.../group__gpio__interface__nrf.html

RE: Getting Data from I2C via Interrupt With MPU-6050

Vidar Berg — Mon, 06 Jan 2025 14:25:53 GMT

I haven't worked with this accelerometer, but I expect it won't drive the signal HIGH with the open-drain configuration.

RE: Getting Data from I2C via Interrupt With MPU-6050

pieseekingmissile — Mon, 06 Jan 2025 14:00:44 GMT

I see. I will try that.

Could you give me more detail on why INT_OPEN (open-drain) is not compatible with active HIGH?

RE: Getting Data from I2C via Interrupt With MPU-6050

Vidar Berg — Mon, 06 Jan 2025 13:00:29 GMT

Hello,

Since the pin interrupt is triggered when the input is connected to VDD, I assume the issue is that the sensor not raising the interrupt signal. If possible, I recommend probing this output signal with an scope or logic analyzer to confirm there is no signal.

Also, in enable_interrupts(), it appears you are configuring the interrupt output pin as INT_OPEN (open-drain), but your interrupt input pin on the nRF is configured as active HIGH.

Best regards,

Vidar