-
We have a custom board based on the STM32U5A5 MCU. The board also has a LSM6DSV IMU. Looking at the zephyr driver support for this family of IMUs, there is existing support for LSM6DSV16X. Apart from the machine learning core on the 16X, are there any fundamental differences between the two variants that would prevent the use of the existing driver for LSM6DSV? Any insights on the reusability (if even possible) of the existing driver for the LSM6DSV would be appreciated. Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
@avisconti Perhaps you can shed some light on this? Thanks. |
Beta Was this translation helpful? Give feedback.
-
The LSM6DSV and LSM6DSV16X belong to the same family of devices and are quite similar. There are few differences though. The two biggest differences are that LSM6DSV DOES NOT have MLC and QVAR, which are not currently used in zephyr. So, I would say that you may use LSM6DSv16X driver keeping in mind what I have just said. I would like to add a clear support of lsm6dsv (and lsm6dsv32x, also part of the family) in the same way we did for lps2xdf (which supports lps22df AND lps28dfw). |
Beta Was this translation helpful? Give feedback.
-
Sorry, can you provide links to the documentation of LSM6DSV16X support? |
Beta Was this translation helpful? Give feedback.
The LSM6DSV and LSM6DSV16X belong to the same family of devices and are quite similar. There are few differences though. The two biggest differences are that LSM6DSV DOES NOT have MLC and QVAR, which are not currently used in zephyr. So, I would say that you may use LSM6DSv16X driver keeping in mind what I have just said. I would like to add a clear support of lsm6dsv (and lsm6dsv32x, also part of the family) in the same way we did for lps2xdf (which supports lps22df AND lps28dfw).