Forum Rule: Always post complete source code & details to reproduce any issue!
Not the way it's currently written. That's why you can select other SPI buses and alternate sets of pins. But you can't mix and match currently. In other words, with the current library, you can select the alternate SPI0 bus of:
Originally Posted by ninja2
MOSI: pin 7
MISO: pin 8
SCK: pin 14
But you can't mix and match pins from the SPI0 bus, like:
MOSI: pin 11
MISO: pin 12
SCK: pin 14
I can look at whether I can re-arrange the code to allow it.
you didnt need to add an external led, you could of just told the mcu to assign SCK to an alternate pin and keep D13 as the led.. see SPI.setSCK(newPin); and reference newPin with the alternate SCK0 pin listed on your teensy card
It's not a big deal, maybe consider it when in next major update. The advantage of 11/12/14 is it frees up the LED_BUILTIN on pin 13.
Originally Posted by brtaylor
Last edited by ninja2; 02-07-2017 at 08:58 PM.
Has anyone tried implementing the wake-on-interrupt feature?
http://www.invensense.com/wp-content...0A-01-v1.1.pdf page 30/31
This would allow very low power applications, eg. deep sleeping the processor and waking by movement.
6.1 Wake-on-Motion Interrupt
The MPU-9250 provides motion detection capability. A qualifying motion sample is one where the high passed sample from any axis has an absolute value exceeding a user-programmable threshold. The following flowchart explains how to configure the Wake-on-Motion Interrupt. For further details on individual registers, please refer to the MPU-9250 Registers Map and Registers Description document.
In order to properly enable motion interrupts, the INT pin should be connected to a GPIO on the system processor that is capable of waking up the system processor.
Nice clear language in this topic.
Hi Fyod, I haven't had a need to implement the wake on interrupt yet. If there's a need for it, I may be able to roll it into the next library update.
Originally Posted by Fyod