LIS25BA configuration on STM32F4

说人不说见

LIS25BA configuration on STM32F4 [Copy link]

 

I recently soldered a LIS25BA module. When connected to the STM32, the IIC was configured according to the normal address and did not work. I'd like to ask what's going on. By the way, can I directly set up DMA to transfer data to wm8978?

dcexpert

Is it a voltage level problem? 1.8V is required.

说人不说见

dcexpert posted on 2019-8-15 21:25 Is it a voltage level issue? 1.8V is required

I asked someone and they said 3.3V is also OK. I connected the A0 line directly to the ground. Is this the problem?

说人不说见

Attach two pictures

dcexpert

Published on 2019-8-16 09:04 I asked someone and they said 3.3V is also OK. I connected the A0 line directly to the ground. Is this the problem?

3V is not acceptable, as stated in the data sheet. 3V can be connected to the X-NUCLEO-IKS01A3, which has a level conversion chip on it

一个小白

You can use 3.3v, there may be problems with the accuracy, but it can work normally. There may be something wrong with your iic program.

Data can be transferred to wm8978 via DMA, but it needs to be processed by stm32. There is no interface in the F4 peripherals that can directly receive LIS25BA data.

说人不说见

A Xiaobai posted on 2019-8-16 14:05 You can use 3.3v, there may be problems with the accuracy, but it can work normally. Your iic program may have problems. You can transfer data to wm89 through DMA ...

I changed the device address directly in IIC. Someone said I should use simulated IIC. Can't I just pass it through IIS?

一个小白

Published on 2019-8-16 14:19 I changed the device address directly in IIC. Others said that I should use simulated IIC. Can't I just pass it through IIS?

The hardware iic has defects, but it is not completely unusable. It depends on the specific situation. No, there is no matching method

littleshrimp

It is recommended to operate according to the voltage in the manual.

Read who am i to see if it is correct

If it is not correct, try using F4 to drive other devices to eliminate the F4 i2c problem.

If that doesn't work, use an oscilloscope to capture the waveform and analyze where the problem is.