0
\$\begingroup\$

I am fairly new to pcb design and I just created a mpu6050 chip that will work with an Arduino microprocessor. I want to make sure the hookup is all correct before I start work on the other parts, as this is the most complicated. It will be using standard i2c communication with scl and sda with the default (low) address being selected. The datasheet can be found here: https://datasheet.lcsc.com/szlcsc/TDK-InvenSense-MPU-6050_C24112.pdf

-Thanks!

enter image description here

\$\endgroup\$
3
\$\begingroup\$

What you have looks pretty good to me.

However, when I'm making the first version of a circuit, I like to add in some flexibility in case the design needs tweaks, or something external changes.

I would suggest (if you have some extra PCB space):

  • Connect all unused pins to separate through-hole test points. This allows you to connect a wire later-on if you decide that you need to use them for something.
  • Add an unpopulated resistor from INT (Pin12) to an unconnected through-hole pad. This will allow you to configure the INT as open-drain if you decide totem-pole (push-pull) isn't working for you. You could then apply the voltage of your choice to the unconnected pad (as log as it's less than Vdd), and add a conveniently-sized pull-up resistor.
  • Add a zero-ohm resistor (jumper) from FSYNC to GND (in case you would like to use its functionality in the future).
  • Keep traces for CPOUT and REGOUT short, and ground the caps using short fat traces . Keep the 'loop area' of these nets as small as possible to reduced possible generated emi. Do not share these ground traces with other parts of the circuit (connect the ground connections of these caps directly to your main ground plane, as close to the chip's ground pins as possible).
  • Their reference design shows a 10nF cap on the VLOGIC pin. You will have separate connections for VDD and VLOGIC, so you might as well (you should) have dedicated caps near each power pin for supply bypassing.

Keep an eye on the diagram for power-on sequencing in section 7.4. This shows that Vlogic must always be <= Vdd (it can't come 'on' first). Be sure this doesn't happen as your design evolves. Shorting Vdd to Vlogic, as you have it shown, should be fine (as the datasheet says that the time difference for power-up can be =0).

Show the PCB when your ready, for some more arm-chair review...

Good luck!

\$\endgroup\$
  • \$\begingroup\$ Thank you! Smart Idea with the INT resistor - will do. I don't plan on using the fsync function for what I am doing, but to be safe ill add one. Also ill add the 10nf cap and have the two separate. I also was planning on adding test points for some of the main lines, so that works. I will def show the pcb design, with it connected to the mega2560 chip. \$\endgroup\$ – Braydon Burkhardt May 16 at 19:23

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.