Skip to content

Driver

BNO08x Driver

A C++20 driver for the CEVA BNO080, BNO085 and BNO086 smart sensor hubs. It speaks SHTP and SH-2 over I2C, SPI and UART, and the stand-alone UART-RVC mode, on any MCU, with no heap and no blocking call.

Quickstart API guide Source on GitHub

The driver has no platform code. You give it a small class that moves bytes on your bus and reads a pin or two; it does the rest: the start-up handshake, SHTP framing and its checks, the SH-2 reports and commands, timestamps, calibration, tare and the configuration records.

Smart sensor hub BNO080, BNO085, BNO086 CEVA
Function
Accelerometer, gyroscope and magnetometer fused by the MotionEngine into rotation vectors, motion and activity reports
Interface
I2C (0x4A or 0x4B), SPI mode 3 up to 3 MHz, UART-SHTP at 3 Mbit/s, or UART-RVC at 115200 baud; chosen by two strap pins at reset
Reports
Every sensor report of the SH-2 reference manual, batched and timestamped, from 1 Hz to 1 kHz
Configuration
Calibration, tare, orientation and the flash record store (FRS), read and written by record
Supply
VDD 2.4 V to 3.6 V, VDDIO 1.7 V to 3.6 V

What you get

  • One object, four transports. Bno08x<YourPort> takes a port that names its transport; the I2C, SPI, UART-SHTP and UART-RVC paths share the same API. See Transports.
  • Never blocks. Begin() starts a session and Poll() does all the work in small steps. Operations return an OpId and finish with an event. See Architecture.
  • Every sensor report decoded. One event type with the report's values in its own units, a timestamp and the accuracy. See Sensors.
  • Calibration, tare and FRS. Typed calls for every command of the manual, and generic record read and write. See Calibration.
  • Strict where the documents are, tolerant where they are not. Every place the documents disagree or are silent is a named ambiguity with a configuration knob. See Ambiguities.
  • No heap, no exceptions, no RTTI. Buffers are template parameters. See Contract.
  • Tested without hardware. Host tests run the driver against an independent model of the hub on all four transports, and a fuzzer corrupts what the hub sends. See Testing and CI.

Datasheet

Document Revision Get it
Datasheet: BNO080/BNO085/BNO086 data sheet (CEVA 1000-3927) 1.17, 2023-07-24 PDF · vendor page
Datasheet: BNO080/BNO085 data sheet (earlier revision, history only) (CEVA 1000-3927) 1.8, 2020-02-05 PDF · vendor page
Datasheet: BNO080 data sheet (earliest revision) (CEVA (Hillcrest Labs) 1000-3927) 1.3, 2017-10-01 PDF · vendor page
Datasheet companion, reference manual: SH-2 Reference Manual (CEVA 1000-3625) 1.9, 2021-06-10 PDF · vendor page
Datasheet companion, reference manual: SH-2 Reference Manual (earlier revision, history only) (CEVA (Hillcrest Labs) 1000-3625) 1.2, 2017-05-19 PDF · vendor page
Datasheet companion, protocol: Sensor Hub Transport Protocol (SHTP) (CEVA 1000-3535) 1.10, 2021-06-10 PDF · vendor page
Datasheet companion, protocol: SH-2 SHTP Reference Manual (CEVA 1000-3600) 1.6, 2019-01-01 PDF · vendor page
Datasheet companion, application note: BNO080/BNO085 calibration guide (CEVA 1000-4044) 1.6, 2023-02-01 PDF · vendor page
Datasheet companion, application note: BNO080/BNO085 calibration procedure (earlier revision) (CEVA 1000-4044) 1.3, 2019-07-01 PDF · vendor page
Datasheet companion, application note: BNO085/BNO086 tare usage guide (CEVA 1000-4045) 1.3, 2023-02-01 PDF · vendor page
Datasheet companion, application note: BNO080/BNO085 migration guide (from the BNO070) (CEVA (Hillcrest Labs) none printed) 1.6, 2017-10-01 PDF · vendor page
Datasheet: FSP200 data sheet (same SH-2, read for context only) (CEVA 1000-4121) 1.5, 2022-09-01 PDF · vendor page
Datasheet: BMF055 data sheet (same silicon; electrical limits cross-check only) (Bosch Sensortec BST-BMF055-DS000) 0.4, 2020-11-01 vendor page
Datasheet companion, application note: BNO055 handling, soldering and mounting instructions (mounting cross-check only) (Bosch Sensortec BST-BNO055-HS000) 1.0, 2015-01-01 vendor page

Written against these revisions; the SHA-256 of each file is in docs/datasheets.yml. Where each part of the driver is in the datasheet: Datasheet map.

Where to go next

  • Quickstart


    Wire the chip, write the port, read the rotation vector.

  • Hardware


    Pins, straps, supplies, timing and reference circuits.

  • Transports


    I2C, SPI, UART-SHTP and UART-RVC, framing and checks.

  • API guide


    Start a session, run operations, read events, handle errors.

  • Calibration


    Calibration, tare, orientation and the FRS records.

  • Ambiguities


    Where the documents disagree, and the knob for each.