Hello, looking at bmi08a_get_synchronized_data code, I noticed that synchronous accelerometer data fetch is split into two different transactions, the first for x and y coordinates, the second for z. I then tried to group the two transactions into a single read covering all required addresses, including the range between BMI08X_REG_ACCEL_GP_0 and BMI08X_REG_ACCEL_GP_4. Longer payload, but an SPI transfer saved. Doing this I still get correct values for x and y, but z fixed to zero. Should I then assume as mandatory to have a dedicated read starting at BMI08X_REG_ACCEL_GP_4 (z address), or it can be included in a longer transaction without side effects? Many thanks Andrea
... View more