BMI160 Obsolete: Best Replacement Sensors BMI270, BMI323, LSM6DSOTR

Bosch has officially marked the bosch bmi160 as obsolete, with support ending on April 14, 2025. Engineers now face a critical need to select new sensors for ongoing projects. Top recommended replacements include the bosch bmi270, BMI323, BHI360, and LSM6DSOTR. Many developers also consider sensors like MPU-6500, MPU-6050, MPU-9250, LSM6DSM, and LSM6DS3 for their low power use and high accuracy.

Developers must act quickly, as bosch will discontinue support and supply for these sensors.

bosch bmi160 Obsolescence  

End-of-Life Timeline

Bosch announced the official end-of-life for the bosch bmi160 sensor in early 2024. The company set April 14, 2025, as the final date for support and supply. After this date, engineers will not receive firmware updates, technical support, or new shipments. Many distributors have already started to reduce their inventory. Some have placed strict limits on order quantities.

⚠️ Note: Teams relying on the bmi160 should check their current stock and plan for last-time buys before the deadline.

A typical end-of-life process for sensors like the bosch bmi160 includes several stages:

• Initial Notification: Bosch informs customers about the upcoming discontinuation.

• Last-Time Buy Period: Customers can place final orders for the bmi160.

• End of Support: Bosch stops providing technical help and software updates.

• Obsolescence: The sensor becomes unavailable for new designs.

Impact on Projects

The obsolescence of the bosch bmi160 affects many industries. Wearable devices, robotics, and IoT products often use this sensor for motion tracking. When the bmi160 becomes unavailable, teams must redesign hardware and update firmware. Some projects may face delays or increased costs.

Project managers should review all designs that use the bmi160. They need to identify risks and create a migration plan. Early action helps avoid production stoppages and supply chain issues. Teams should also test new sensors to ensure performance matches the original bosch bmi160.

Comparison Table     

bmi160 vs bmi270

Engineers often look to the bmi270 as a direct replacement for the bosch bmi160. Both sensors share similar pinouts and package sizes, making hardware swaps straightforward. However, software support and integration differ. The bmi270 requires a configuration file upload at every power-up, which increases firmware complexity and memory use. Devices with limited memory may need extra storage to handle this file. The bmi270 also offers advanced features, but these come with added setup steps.

Note: Users report that using bmi270 with bmi160 component software can cause communication failures. The bmi270 needs its own drivers and setup.

The chart above shows that the bmi270 SensorAPI has more community activity and recent updates than the bmi160 API. This means engineers can expect better ongoing support for the bmi270.

Other Alternatives

When the bmi270 does not fit project needs, teams can consider other sensors. The following part comparison table summarizes key specs, compatibility, and software support for leading options:

• Only the bmi270 matches the bmi160 component pinout, but software changes are always required.

• BMI323, BHI360, and LSM6DSOTR need hardware redesigns and new drivers.

• All sensors offer active software support, but each uses different APIs.

Tip: Always review memory and firmware needs before switching sensors. Some alternatives, like the bmi270, add extra steps for configuration and startup.

bmi270 and Other Replacements

BMI270 Overview

The bmi270 stands out as the most direct successor to the BMI160. Bosch designed this sensor to match the original’s pinout and package, which allows for easy hardware swaps. Many engineers choose the bmi270 because it offers improved motion detection and lower noise levels. This sensor supports advanced features like step counting and activity recognition, which benefit wearable and fitness devices.

Pros:

• Hardware compatibility with BMI160 simplifies board redesign.

• Active software support and frequent updates from Bosch.

• Enhanced motion detection and lower noise improve accuracy.

Cons:

• The bmi270 requires a configuration file upload at every power-up. This step increases firmware complexity and uses more memory.

• Developers must update drivers and cannot reuse BMI160 software directly.

Tip: Teams should allocate extra memory for the configuration file and test the new driver integration early in the migration process.

BMI323 and BHI360

Bosch offers the BMI323 and BHI360 as strong alternative options for projects needing lower power or more advanced features. The BMI323 uses less power than the BMI160 and fits into the same 14-pin LGA package. The BHI360 provides a 36-pin LGA package and adds a programmable sensor hub for on-chip data processing.

BMI323 Pros:

• Lower power consumption extends battery life in portable devices.

• Maintains a compact package for space-limited designs.

BHI360 Pros:

• Integrated sensor hub offloads processing from the main CPU.

• Advanced features support gesture recognition and context awareness.

Cons:

• Both sensors require hardware redesign due to different pinouts.

• Developers must adapt software and drivers for new APIs.

Migration Tips for BMI323 and BHI360:

1. Write wrapper functions for low-level I2C or SPI communication using STM32 HAL libraries, instead of Bosch’s COINES protocol.

2. Modify interface files in the Bosch sensor API to replace COINES calls with STM32 HAL-based read/write functions.

3. Use examples from other Bosch sensor APIs, such as the BMP388, to guide the adaptation process.

4. Define device addresses, manage buffers, and handle register operations within the STM32 HAL framework.

5. Test communication thoroughly to ensure reliable sensor data transfer.

Note: This migration approach helps teams move from BMI160 to BMI323 or BHI360, even though Bosch does not provide explicit step-by-step instructions.

LSM6DSOTR

The LSM6DSOTR from STMicroelectronics serves as a popular alternative option to Bosch’s sensors. This device combines a 3-axis accelerometer and a 3-axis gyroscope in a single 14-lead LGA package. It delivers high accuracy and supports selectable full-scale ranges for precise motion tracking. The sensor’s low power consumption makes it ideal for battery-powered products.

Key Features:

• High-resolution motion tracking with selectable ranges.

• Embedded functions such as a programmable finite state machine, event detection, and a FIFO buffer.

• Integrated temperature sensor for thermal drift compensation.

• Flexible communication interfaces, supporting both I2C and SPI.

• Compact package fits space-constrained designs.

Pros:

• Advanced embedded features reduce CPU load and improve efficiency.

• Low power operation extends device battery life.

• Suitable for a wide range of applications, including wearables, industrial automation, and healthcare.

Cons:

• Requires new drivers and software adaptation.

• Hardware redesign needed due to differences in pinout and electrical characteristics.

Engineers should review the LSM6DSOTR’s documentation and reference designs before starting migration. Testing all embedded features ensures the sensor meets project requirements.

Migration Tips

Firmware Changes

Firmware migration requires careful planning. Developers often face new requirements when moving from the bmi160 to other sensors. For example, the BMI270 needs a configuration file upload at every power-up. This step increases memory use and makes firmware more complex. Many sensors, including the bmi160 and its alternatives, do not have enough internal processing power for all built-in features. Enabling too many features can cause the sensor to behave unpredictably or even lock up. Some built-in functions are buggy or poorly documented. Many teams choose to disable these features and process raw sensor data with their own code. When using the bosch sensor api, developers should update interface files and test all changes.

Common firmware migration pitfalls include:

• Sensors like the BMI270 require firmware uploads at each startup, increasing resource use.

• Limited internal processing power can cause lockups if too many features are enabled.

• Built-in features may be buggy or hard to use, leading teams to rely on raw data.

• Interfacing protocols (I2C or SPI) may have conflicting recommendations, making integration harder.

• MEMS sensors often have short product lifecycles, forcing frequent firmware updates.

Tip: Start with basic sensor functions and add advanced features one at a time. This approach helps catch problems early.

Hardware Adjustments

Hardware changes depend on the chosen replacement. The bmi270 matches the bmi160 pinout, so hardware changes are minimal. Other sensors, like the BMI323, BHI360, or LSM6DSOTR, require new PCB layouts. Pin layouts and sensor packaging can complicate board design and soldering. Teams should review datasheets and reference designs before making changes. Careful planning reduces the risk of errors during assembly.

Testing Steps

Testing ensures the new sensor works as expected. Teams should validate communication using both I2C and SPI interfaces. They should check for reliable data transfer and correct sensor readings. Testing should include all power modes and feature settings. Teams must also verify that the sensor does not lock up when multiple features are enabled. Using automated tests helps catch issues early and speeds up development.

Note: Always test with real hardware and in the final product environment. This step ensures the sensor performs well in actual use.

Bosch BMI160 users face a strict deadline. Teams must replace this sensor before April 2025 to avoid supply chain risks. The BMI270, BMI323, BHI360, and LSM6DSOTR offer strong alternatives. These sensors deliver high accuracy, low power use, and flexible interfaces. Their compact size and robust design fit modern wearables and IoT devices.

Early migration planning ensures smooth transitions and keeps projects on track.

FAQ

What happens if a team keeps using the Bosch BMI160 after April 2025?

Bosch will stop support and shipments. Teams may face supply shortages and no technical help. Projects could stall if the sensor fails or stock runs out.

Is the Bosch BMI270 a true drop-in replacement for the BMI160?

The BMI270 matches the BMI160’s pinout and size. However, it needs a configuration file upload at startup. Teams must update firmware and drivers for full compatibility.

Which sensor offers the lowest power consumption among the alternatives?

• BMI323 uses the least power, around 700 μA.

• LSM6DSOTR also provides low power operation.

• Lower power helps extend battery life in portable devices.

Do teams need to redesign hardware for every replacement sensor?

Not every sensor needs a new board. The BMI270 fits the same footprint as the BMI160. BMI323, BHI360, and LSM6DSOTR require hardware changes due to different pinouts or package sizes.