2026-04-08 5:17 AM
Connected STEVAL_$MKI243AA board to a nucleo-g491re board using 4 wire spi interface. The spi bus is setup to run @ 146 Kbits/sec. Reading back bad data.
WHO_AM_I is 0x48
PIN_CTRL is 0x3E
Not sure but seem like the device is power
2026-04-27 4:16 AM
Hello Andrew,
Why do you say that MISO is bad? At the start of the SPI cycle, the IMU will not drive this signal, and so the MISO line would be floating (which is what is being observed). in the second part of the SPI cycle, read data is clearly being driven back by the IMU i.e. 0x48 (which is the problem. It should be 0x6B).
Thx.
Rgds.
2026-04-27 4:47 AM
@arifkhan wrote:Why do you say that MISO is bad? .
Just look at it:
It's supposed to be a digital signal; ie, it should have just 2 clearly distinct levels - low and high.
Yours seems to have about five different levels !
@arifkhan wrote:At the start of the SPI cycle, the IMU will not drive this signal, and so the MISO line would be floating
Even so, it shouldn't be fluctuating like that - something looks very wrong!
Again, you still haven't shared schematics or code.
2026-04-28 5:35 PM - last edited on 2026-04-29 2:09 AM by Andrew Neil
2026-05-01 10:46 AM
Hey Andrew,
Do you see anything in the code?
Rgds.
2026-05-05 2:57 AM
I composed this reply some time last week, but it doesn't seem to have got published.
Fortunately, the forum kept a draft:
A good, clear photo of your actual setup would help.
Check connections very carefully - particularly Vdd & GND.
@arifkhan wrote:The two evals boards are jumpered as shown with 8" jumper wires.
These are quite prone to poor connections.
As noted above, your MISO behaviour very much suggests poor connections.
I would strongly recommend one of the X-Nucleo-IKS adaptor boards ("shields") - which accommodate the 24-pin DIL pinout; eg,
X-NUCLEO-IKS5A1 - X-NUCLEO-IKS02A1 - X-NUCLEO-IKS4A1
These models are Obsolete, but still usable if you happen to have one:
X-NUCLEO-IKS01A3 - X-NUCLEO-IKS01A1
2026-05-05 2:59 AM
@arifkhan wrote:Do you see anything in the code?
Looks more like a hardware problem to me.
See my "delayed" post ...