MPU-6050 replacement: obsolete 6-axis IMU cross-reference (2026)
Engineers replacing the obsolete MPU-6050 reach first for the crosses that autocomplete alongside it, the BNO055, the BMI160, the ADXL345 and the MPU-9250, and every one of those four has a catch. The ADXL345 has no gyroscope. The BMI160 is at Bosch end-of-life. The MPU-9250 is end-of-life at TDK. The BNO055 is not recommended for new designs. A 6-axis IMU is defined by carrying both a 3-axis gyroscope and a 3-axis accelerometer on a specific register map, not by the “IMU” tag a distributor filter returns, so a cross that shares the label can still lack the gyro or be obsolete itself. This page screens the searched crosses, mpu6050 vs bno055, mpu6050 vs bmi160, mpu6050 vs adxl345, mpu6050 vs mpu9250, against TDK's own named alternate, the ICM-42670-P. Suggested candidates to validate in your own design, not drop-in equivalents.
Status // The part in question
Lifecycle status
On TDK's own Product Center page, the MPU-6050 shows an “Obsolete” Product Status, and that same page names the ICM-42670-P as its Recommended Alternate under the qualifier “Interchangeability is not guaranteed.” The live page rejects automated fetches, so the status word and the alternate line here are cited from the archived 2025-09-15 capture; DigiKey flags the part obsolete and the trade press reports it discontinued at TDK, with no cross-source conflict.
A maker-set Obsolete status makes this a migration, not a planned design-out. What separates the MPU-6050 from a quiet industrial end-of-life is its install base: it sits in an enormous body of hobby and clone hardware, and sourcing threads report counterfeit MPU-6050 units in circulation, so any last-time-buy or broker stock should come from authorized channels only. Runway does not remove the requalification, because every active cross on this page changes the register map, the interface, or the sensor content, sometimes all three.
Live stock, broker availability and pricing shift week to week; those point-in-time numbers belong in the email, not on this evergreen page.
Candidates // Why these
The candidate set
One vendor-named alternate, and four crosses that carry their own fit-catch. The MPU-6050 core, for reference: a 6-axis MEMS device combining a 3-axis gyroscope and a 3-axis accelerometer with an on-chip Digital Motion Processor, I2C only at addresses 0x68 or 0x69, in a 24-pin QFN measuring 4×4×0.9mm, on the RM-MPU-6000A register map shared with the MPU-6000.
Catch: TDK's own qualifier is “interchangeability is not guaranteed.” This is the part the MPU-6050 status field points to, and the only candidate here that is both a true 6-axis IMU and in production. Its register architecture and identity value differ from RM-MPU-6000A, so an MPU-6050 driver will not enumerate or configure it without a rewrite, and the package changes from QFN-24 to LGA-14.
Catch: fused output, not a register-level match. The part mpu6050 vs bno055 searches, cross-shopped because it also reports orientation. It is a 9-axis System in Package running on-board fusion firmware, outputting absolute orientation (quaternion or Euler) over its own register set on I2C or UART. The host either consumes fused output or drives it in a different mode, either is a firmware rework. Bosch also lists it not recommended for new designs.
Catch: obsolescence relocated, not solved. The part mpu6050 vs bmi160 searches. It is a genuine 6-axis IMU on a Bosch register map, but it is at Bosch end-of-life and not available for new designs (a trade source dates the final buy 2025-04-14), and Bosch names the BMI270 and BMI323 as the forward path. Ruling it out early avoids qualifying a part already being retired.
Catch: no gyroscope. The part mpu6050 vs adxl345 searches. It is a 3-axis accelerometer only, so it cannot replace the MPU-6050 in any design that reads the gyro. It is the accelerometer half of a 6-axis solution, part of a replacement, not a replacement. It earns a row here only to close off that cross.
Catch: the same-family upgrade is also end-of-life. The part mpu6050 vs mpu9250 searches, cross-shopped as a family step that adds a magnetometer. It is end-of-life at TDK, and its register map is documented separately from the MPU-6000/6050 map, so it is neither a durable path nor a register-level match.
Also named, not built into the comparison: ST's LSM6DS3 is a common cross-vendor migration target, and the 9-axis ICM-20948 is sometimes suggested as a same-vendor step but is itself end-of-life at TDK. Each is a different part with its own register map and driver. None of the parts compared is a drop-in.
Screening // Two questions, five candidates
The two questions that end most crosses
Before any parametric comparison, two facts disqualify a candidate outright, and neither is a filterable column in a distributor cross-reference: does the part carry a gyroscope at all, and is the part itself still in production? Filter loosely on “motion sensor” and the tool returns the ADXL345, which has no gyro. Filter on “6-axis IMU” and it returns the BMI160 and MPU-9250, both discontinued.
Screening pass · run before parametrics, not after
The screen comes before the parametric search. A cross-reference will hand back all five; the gyro question and the candidate's own status are what remove four of them, suggested candidates to validate in your own design, not drop-in equivalents.
Parametrics // Side by side
Comparison table
Sensor content and lifecycle are settled in section 03 and are deliberately not repeated here. What remains is the fit and firmware detail, bus, footprint, register identity, and the confidence behind each status, for the parts that reach this stage.
| MPU-6050 (subject) | ICM-42670-P | BNO055 | BMI160 | ADXL345 | MPU-9250 | |
|---|---|---|---|---|---|---|
| Vendor | TDK InvenSense | TDK InvenSense | Bosch Sensortec | Bosch Sensortec | Analog Devices | TDK InvenSense |
| Host interface | I2C only (0x68 / 0x69) | I2C 1MHz + SPI 24MHz + I3C 12.5MHz | I2C + UART | I2C + SPI | I2C + SPI | I2C + SPI |
| Package | QFN-24, 4×4×0.9mm | LGA-14, 2.5×3.0×0.76mm | LGA-28, 3.8×5.2×1.13mm | LGA-14, 2.5×3.0×0.83mm | LGA-14, 3×5×1mm | QFN-24, 3×3×1mm |
| Register map / driver identity | RM-MPU-6000A, WHO_AM_I 0x68 | Own architecture, different WHO_AM_I; new driver | Fusion register set + operating modes; new driver | Bosch map; new driver | Accelerometer registers only; no gyro registers | Own map, documented separately from RM-MPU-6000A |
| On-chip processing | DMP (Digital Motion Processor) | APEX motion features | On-board fusion firmware | Step / motion features | Activity & tap detection | DMP + magnetometer |
| Status confidence | Confirmed (TDK field, archived 2025-09-15) | Confirmed | Confirmed (Bosch NRND) | Dated (EOL date via trade source) | Confirmed | Confirmed |
The load-bearing rows here are package, host interface and register map / driver identity: no candidate keeps the RM-MPU-6000A map, and none shares the MPU-6050 footprint, so a per-pin map is not meaningful across the set. Package, interface and register data is vendor-reported, not independently audited.
Next // The decision
What to do next
One candidate survived the screen, and one cross-vendor option is worth pricing beside it.
Path A · the vendor's own answer
The part TDK's status field points MPU-6050 users to, with the vendor's qualifier that interchangeability is not guaranteed.
- Re-layout the sensor site for LGA-14, 2.5×3.0mm
- Port the driver off RM-MPU-6000A to its own architecture
- Decide whether to keep I2C or take the SPI / I3C option
Path B · the cross-vendor comparison
ST's 6-axis IMU is a common migration target off the MPU-6050. Named here as a path to price and qualify, not a screened candidate.
- Confirm current lifecycle status at ST before designing in
- Budget a second-vendor driver, not a port of Path A's
- Weigh dual-source value against a second qualification
Both paths
No active candidate keeps the RM-MPU-6000A register map.
The driver rewrite is the gating validation on either path, the target has to enumerate and stream in your firmware before the board is committed. Authorized channels matter here, because counterfeit MPU-6050 parts are reported in circulation.
Ruled out in section 03, do not re-open
- ADXL345no gyroscope
- BMI160EOL at Bosch
- MPU-9250EOL at TDK
- BNO055NRND, fused output
What this doesn't say: every lifecycle call above is only what the cited source showed on the verification date. Statuses move, so treat the source list below as the live record and re-check each one before you commit a design. No end use, program or system is named or implied.
FAQ // Frequently asked
Frequently asked questions
Is the MPU-6050 obsolete or still in production?
The MPU-6050 is obsolete, not in production. TDK's Product Center lists Product Status as “Obsolete” and names the ICM-42670-P as its recommended alternate, read from the archived capture because the live page blocks automated fetches, and DigiKey lists it as obsolete. Broker and last-time-buy stock still appears, but the maker status is end-of-life, so the reader-useful move is a planned migration rather than a stock hunt.
What is the recommended replacement for the MPU-6050?
TDK's named recommended alternate is the ICM-42670-P, and TDK adds “Interchangeability is not guaranteed.” It is a current 6-axis IMU, but its register architecture, WHO_AM_I identity and package differ from the MPU-6050, so it enters the design as a new part to qualify, not a like-for-like swap.
Can I replace the MPU-6050 with an ADXL345?
No, the ADXL345 is a 3-axis accelerometer with no gyroscope. It can supply the accelerometer half of a 6-axis solution, but any MPU-6050 design that reads gyro data needs a separate gyroscope or a true 6-axis part. The ADXL345 is part of a replacement, not a replacement.
Is the MPU-9250 still available as an MPU-6050 alternative?
No, the MPU-9250 is not a durable alternative, because it is itself end-of-life at TDK. It is a 9-axis part often cross-shopped as a same-family upgrade, but crossing to it moves the design onto another discontinued TDK part and onto a register map documented separately from the MPU-6000/6050 map.
Is the BMI160 a safe cross for the MPU-6050?
No, the BMI160 is at Bosch end-of-life and not available for new designs (a trade source dates the final buy 2025-04-14). It is a real 6-axis IMU on a Bosch register map, but it is being retired and Bosch names the BMI270 and BMI323 as the forward path, so crossing to it would qualify a part that is already discontinued.
How is the BNO055 different from the MPU-6050?
The BNO055 is a 9-axis sensor-fusion System in Package that outputs absolute orientation, while the MPU-6050 is a 6-axis raw-data IMU. It runs on-board fusion firmware and exposes fused orientation over I2C or UART on its own register set, so it is not a raw-register replacement: the host either consumes fused output or drives it in a different mode, and either is a rework.
Does the register map or interface change when moving off the MPU-6050?
Yes, both change on every active cross. The MPU-6050 is I2C-only on the RM-MPU-6000A map, and no active candidate keeps that map: the ICM-42670-P uses its own architecture and adds SPI and I3C, the BNO055 uses a fusion register set and adds UART, and the ADXL345 exposes accelerometer registers with no gyro registers at all. The register-map port and driver rewrite are the core of the migration.
Sources // Public, primary
Sources
- TDK Product Center MPU-6050 status (Obsolete; alternate ICM-42670-P, “interchangeability is not guaranteed”), archived 2025-09-15
- MPU-6050 product status (DigiKey, Obsolete)
- MPU-6000 and MPU-6050 Product Specification (TDK, PS-MPU-6000A, PDF)
- MPU-6000 and MPU-6050 Register Map and Descriptions (RM-MPU-6000A, PDF)
- ICM-42670-P product page (TDK InvenSense; I2C / SPI / I3C host interface)
- Bosch BNO055 product page (9-axis absolute orientation sensor)
- Bosch BMI160 product page (6-axis IMU)
- BMI160 status: not available for new designs; Bosch names BMI270 / BMI323 (trade source, final buy 2025-04-14)
- Analog Devices ADXL345 product page (3-axis accelerometer)
- MPU-9250 product page (TDK InvenSense, 9-axis)
- MPU-9250 product status (DigiKey)
- ICM-20948 product page (TDK InvenSense, 9-axis, itself EOL)
- ST LSM6DS3 product page (6-axis IMU, migration path)
- Rapid Electronics: “MPU6050 alternatives, equivalents” (EOL context)
- Arduino Forum: “Successor to the MPU6050?”
- SparkFun Community: “MPU6050 obsolete?”
Part of // Featured in
Related reading
Editorially independent and from public sources only; lifecycle, package, electrical and interface data is vendor-reported, not independently audited. Alternates are candidates to validate in your own design, confirm every detail with the manufacturer before committing.
About the author
Editorially independent and from public sources only; lifecycle, pin and rating data is vendor-reported, not independently audited. Alternates are candidates to validate in your own design. Confirm every detail with the manufacturer before committing.