Fix #9562 bmi166 acc readout

[mmosca]

Looks like a typo on bmi160 code.

@DzikuVx this does not seem like a very popular IMU. It was only i in the RADIX target, which lacks a CMakeLists.txt.

The driver itself has been sitting, mostly unchanged for 6-7 years (except a few changes 7 months ago) which introduced this typo.

Reported in issue #9562

[mmosca]

Upon further digging, radix target has been disabled since at least 2.4.0

[synersignart]

Looks like a typo on bmi160 code.

@DzikuVx this does not seem like a very popular IMU. It was only i in the RADIX target, which lacks a CMakeLists.txt.

The driver itself has been sitting, mostly unchanged for 6-7 years (except a few changes 7 months ago) which introduced this typo.

Reported in issue #9562

apparently Our Synerduino boards are using those and we inverted the X and Y axis as the chip set we got seems to have this arrangement

[synersignart]

the INAV 6.1.0 version as this as well

[mmosca]

the INAV 6.1.0 version as this as well

Does it work in inav 6.1.0?

[synersignart]

the INAV 6.1.0 version as this as well

Does it work in inav 6.1.0?

yes after I change the orientation of the X and Y axis as you can see here. as for the code gyroRaw & accRaw it was correct
Commented : the original code
UnCommented : the modify code
this was done could simply be that the later BMI160 chips could have a different orientation between the Gyro and Acc that causes incorrect readings

side note:

Synerduino boards are using the BMI160 as well and active in the Philippine market.