wasserwiesel
Junior Member

Thank you very much mjs513 for your testing! Good to see, that it's working on your side. My confidence in the Teesy is increasing thanks to you and I will continoue to use spi Mode. I remember in past I came across...

With my own lib (not the borderflight) I have similar issues. I get only the gyro X and Acc X values. But with the delay it is working. So it is rather a problem with teensy 4.x, it is just to fast as KurtE already...

No problem, thank you for your help! Yes I saw that pull request, thats how I came to the nanodelay solution. I see, so the teensy is too fast - doesn't sound so bad ;) I updated arduino and teensyduino to the latest...

Yes, I had the same behavior, sometimes even different whoAmI values without changing anything. But I am amazed why such errors occur with so few people. However, an idea just occurred to me. The SPI traces on my PCB...

150 MHZ CPU Speed

At 600MHZ CPU Speed and nanoseconddelay(120) its works only randomly, therefore I will wait 500ns for safety reasons. But what does this mean? - Is the digitalWrite too slow?

It works with nanosecondsDelay(200) after a digitalWrite^^

https://forum.pjrc.com/threads/58688-Teensy-4-0-Clock-speed-influences-delay-and-SPI Seems like a known issue... I will now try to add some nanoseconds delay after the chip selection, but I don't like this solution...

It doesn't work like I said. Only with 150MHZ. Nevertheless thanks for your reply.

https://github.com/bolderflight/MPU9250