I am trying to use the motion_driver_6.12 with a teensy 3.1.
Now as soon as inv_execute_on_data with INV_PRIORITY_QUATERNION_GYRO_ACCEL as parameter is called my program get stuck and nothing happens any more.
To be more precise the last call I could track was "result = inv_data_builder.process[kk].func(&sensors);" which I assume calls a function in the compiled
libmpllib.
Calling inv_enable_fast_nomot does lead to "no response" as well but I am not sure yet if this is due to the same problem.
Those features are enabled:
hal.dmp_features = DMP_FEATURE_6X_LP_QUAT | DMP_FEATURE_TAP |
DMP_FEATURE_ANDROID_ORIENT | DMP_FEATURE_SEND_RAW_ACCEL | DMP_FEATURE_SEND_CAL_GYRO |
DMP_FEATURE_GYRO_CAL;
Did anyone see something similar or has a clue what could cause this?
Can someone confirme that "run_self_test" is not compatible with MPU9250? I get a gyro fail on all axis.