X-NUCLEO-IKS01A3 sensor driver transplantation based on NUCLEO-L011K4

sylar^z

X-NUCLEO-IKS01A3 sensor driver transplantation based on NUCLEO-L011K4 [Copy link]

 

This porting of the X-NUCLEO-IKS01A3 sensor driver is based on the NUCLEO-L011K4 development board, using the official en.x-cube-mems1.zip resource package. Since the NUCLEO-L011K4 has only 16K ROM, the sensor functions can only be enabled one by one through the compilation options, and the enable flag is located in the iks01a3_conf.h file. In order to facilitate viewing of data, an OLED display is connected to display the collected sensor data.

During the debugging process, I found that X-NUCLEO-IKS01A3 sometimes did not respond after vibration (I2C communication did not return), and it still did not respond after restarting L011K4, until IKS01A3 was powered on again, it became normal. I wonder if other netizens have encountered such a situation.

NUCLEO-L011K4 Development Board

Configure pin functions and initialize them through CubeMX.

Drive HTS221 and collect data.

Drive LPS22HH and collect data.

Drive STTS751 and collect data.

Drive LSM6DSO and collect data.

Drive LIS2DW12 and collect data.

Drive LIS2MDL and collect data.

Source code: NUCLEO-L011K4_FOR_X-NUCLEO_IKS01A3_WITH_DRIVER-(fin).rar (11.91 MB, downloads: 60)

2019-7-24 18:15 上传

点击文件名下载附件

dcexpert

I2C not responding is sometimes because the I2C bus has an error and needs to be reinitialized.

sylar^z

dcexpert published on 2019-7-25 11:12 I2C does not respond sometimes because the I2C bus has an error and needs to be reinitialized.

It should not be an I2C error. I reset NUCLEO-L011K4 and re-downloaded the program, but still could not read the sensor data. It returned to normal after the whole power was turned off.