Timeline for LSM6DS3 SPI-communication problem with STM32F4
Current License: CC BY-SA 4.0
Post Revisions
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 28, 2024 at 8:28 | comment | added | 0andriy | You can always to look into the implementation of the driver for Linux kernel to get some ideas from. The code there is most likely was tested (okay, to some extent). | |
| May 27, 2024 at 7:48 | comment | added | Andrey Turkin | Can't see anything obviously wrong, so here are some ideas you could try to debug this. 1: Set the entirety of SPI CR1, just to be sure of the flags. 2: Try lower speed (also would make analyzer output less jittery). 3: Try disconnecting MISO from the MCU and checking with scope if behaviour changes at all. 4: Try bidirectional 2 byte transmit&receive - maybe the device doesn't like big clock gaps for some reason? | |
| May 26, 2024 at 12:57 | comment | added | hcheung | Can you show what SPI_Receive() does? After sending the address byte, you need to transmit one byte dummy in order to get the received data back. | |
| May 26, 2024 at 8:29 | history | edited | hcheung | CC BY-SA 4.0 |
added 42 characters in body
|
| S May 26, 2024 at 7:49 | review | First questions | |||
| May 30, 2024 at 12:47 | |||||
| S May 26, 2024 at 7:49 | history | asked | Дмитро Мачковський | CC BY-SA 4.0 | created from wizard |