GYRO scanning I2C endpoint is killing CPU cycles

[Circuit-Overtime]

Problem Statement

The title suggests the IMU/gyro I2C scan path is consuming excessive CPU cycles. The specific scope is unclear: it is not stated whether the issue is in firmware, a tool, or an app-level probe.

Tasks

• Scope to be defined once the questions below are answered.

Checklist

• Issue scope confirmed
• Relevant component identified
• Change reviewed
• Verification completed

---

Questions from @elixpoo

• Which component shows the CPU usage increase: oreoWare/imu.py, tools/imu_probe.py, or another IMU-related path?
• Is the problem caused by continuous I2C scanning, or by a broader IMU polling loop?
• What behavior is expected instead of the current CPU usage?
• Is this a regression from a recent change, or a long-standing issue?

[Circuit-Overtime]

Solved by #28