New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Eagle Schematic Question #229
Comments
The VDDIO supplies power to the digital sector, mostly I2C, but it is a
different domain and best practice is to bypass the analog (VDD) and
digital (VDDIO) domains separately. Standard practice it to connect the
caps directly to the MPU9250 pins and use a via on the other side of the
cap to provide the connection to power. I would also tie ADO to GND or VDD,
one or the other depending on which device address you want. If 0x68 is
OK tie ADO to GND. nCS must be pulled HIGH to VDD, no bypass is
required, for I2C. I would recommend you connect the interrupt to the MCU.
The Pro Mini is one of my favorite MCUs but at best you will be able to get
~100 Hz sensor fusion rate out of it, not really adequate if your intention is
absolute orientation estimation. My recommendation is to use 4K7 pullups if
the number of I2C devices on the bus is six or fewer. If you have as many
as 10 devices then 2K2 would be appropriate.
I think the RESV pin is pin 20, right? Yes, I would GND this pin. here is one of my designs for reference:
https://www.oshpark.com/shared_projects/WnZaoIHh
BTW, the Sparkfun design is crap.
…On Wed, Jan 17, 2018 at 6:56 PM, ElectroStef ***@***.***> wrote:
Hi Kris,
I'm developing a black box of sorts for a high altitude glider and I'm
using the MPU9250. My biggest question is whether or not I have the VDDIO
pin connected correctly. I noticed in your design you have a capacitor
going to ground, but I'm thinking if I just tie it in with VDD I should be
fine. I also have a few other sensor running on my I2C lines so the pull up
resistors aren't in this portion of the schematic (my pull ups are 2.7k
which is recommended for 3.3V) I am using an ATmega328P with 3.3V. I think
this will work, but I would like a second opinion as I am still confused on
what the VDDIO pin is used for. I have read the data sheet but I still seem
a little confused. If you could help that would be great, thank you!
-stef
[image: mpu9250]
<https://user-images.githubusercontent.com/31677212/35078545-54ca7324-fbc8-11e7-94a7-778a681cfa55.PNG>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#229>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGY1qnpwn1v3iYlHTf0elV_awTRQsH5xks5tLrLigaJpZM4RiT-m>
.
|
Thanks for the clarification! Ya the Sparkfun design wasn't all that great. -Stef |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi Kris,
I'm developing a black box of sorts for a high altitude glider and I'm using the MPU9250. My biggest question is whether or not I have the VDDIO pin connected correctly. I noticed in your design you have a capacitor going to ground, but I'm thinking if I just tie it in with VDD I should be fine. I also have a few other sensor running on my I2C lines so the pull up resistors aren't in this portion of the schematic (my pull ups are 2.7k which is recommended for 3.3V) I am using an ATmega328P with 3.3V. I think this will work, but I would like a second opinion as I am still confused on what the VDDIO pin is used for.
Also I saw that you have the RESV pin connected but Sparkfun didn't seem to use this at all, I used the sparkfun library for my MPU component and it doesn't have that pin shown.
I have read the data sheet but I still seem a little confused. If you could help that would be great, thank you!
-stef
The text was updated successfully, but these errors were encountered: