Add support for new variants of BMI160. #277

New Issue

MrUnknownDE · 2026-04-05T17:52:24+02:00

MrUnknownDE commented

2026-04-05 17:52:24 +02:00

Originally created by @alice-king on 5/16/2023

When testing my AIO tracker, I found that the whole batch of BMI160 all have 0xD3 as CHIP_ID instead of 0xD1, with all functionalities checked out ok after skipping the CHIP_ID check in testConnection().

I found this header containing three different CHIP_IDs:
0xD0 for 'BMI' (probably for engineering samples)
0xD1 for 'BMI_C2' (Matches the value listed in the datasheet)
0xD3 for 'BMI_C3' (probably for newer revisions of the chip).

https://github.com/BST-Github-Admin/drivers/blob/master/drivers/iio/imu/bmi160/bmi160_core.h

Considering 'BMI_C3' may get more usage if it's really a newer revision of the chip, add support for CHIP_ID value 0xD3 in case anyone gets their hands on some new chips as I do.

*Originally created by @alice-king on 5/16/2023* When testing my AIO tracker, I found that the whole batch of BMI160 all have 0xD3 as CHIP_ID instead of 0xD1, with all functionalities checked out ok after skipping the CHIP_ID check in testConnection(). I found this header containing three different CHIP_IDs: 0xD0 for 'BMI' (probably for engineering samples) 0xD1 for 'BMI_C2' (Matches the value listed in the datasheet) 0xD3 for 'BMI_C3' (probably for newer revisions of the chip). https://github.com/BST-Github-Admin/drivers/blob/master/drivers/iio/imu/bmi160/bmi160_core.h Considering 'BMI_C3' may get more usage if it's really a newer revision of the chip, add support for CHIP_ID value 0xD3 in case anyone gets their hands on some new chips as I do.

MrUnknownDE closed this issue

2026-04-05 17:52:24 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/SlimeVR-Tracker-ESP#277