|
Post by Frisbone on Sept 4, 2015 11:25:47 GMT -5
While trying to figure out why I couldn't get the MPU9150 interrupts to respond (they certainly are being generated, saw that on the O-scope) I thought I would change the properties and build to the original AM (and swap out the 9150 for the MMA8452). In doing so and rebuilding I found that while an initial signal seems to start coming out - it seems to stop right at the important part (run-time).
Looked at the git repository and it seemed to break right when I added support for multiple AMs. The code was checked in with simulated AM mode so it wasn't obvious that it had been running with a real ISR prior to check in. Need to review all of those changes to see what may have caused the problem.
I'm hoping that by finding out why the ISR stopped working for the MMA8452 it may explain why it doesn't work for the MPU9150.
|
|
|
Post by Frisbone on Sept 14, 2015 5:03:20 GMT -5
Ultimately this seemed to simply be a configuration issue of the MPU9150 but I also found a bug in the version of wiringPi I was using. Turns out it was creating phantom interrupts (a lot of them) - a more recent version of the library existed so I tried it out and that area of the code had been altered significantly and the problem went away. MPU9150 interrupts now work fine - haven't gone back to test MMA8452 but I suspect it will be ok now as well.
|
|