Jeetrohan mpu60xx 1 (BSP-568)

[jeetrohan]

ESP-BSP Pull Request checklist

Note: For new BSPs create a PR with this link.

• Version of modified component bumped
• CI passing

Related

• Feature Request: Support for DMP Mode in MPU6050 Driver (BSP-482) #317

Change description

A new mpu60xx library which uses the new I2C driver for reading raw and floating point values; from accelerometer, gyrometer and temperature sensor.
Added functionality to use inbuilt motion detection on mpu60xx using both, polling and interrupts.

[CLAassistant]

All committers have signed the CLA.

[tore-espressif]

@jeetrohan That's a pretty good job for your first contribution!

[jeetrohan]

I just realized the merge here is different from the fork where sync simply updates the branch. 😅

[jeetrohan]

@espzav , @tore-espressif
If I'm not wrong the pre-commit failed because of incorrect indentation, which it has fixed (or so it indicates in output).
A rerun should do it.

[tore-espressif]

@espzav , @tore-espressif If I'm not wrong the pre-commit failed because of incorrect indentation, which it has fixed (or so it indicates in output). A rerun should do it.

The pre-commit job is always run on latest changes, so there are probably still some formating errors.

If you want to fix them locally, in your esp-bsp folder you can do

pip install pre-commit && pre-commit install

To install pre-commit. Then you can run the pre-commit check on you last 11 commits like this

pre-commit run --from-ref HEAD~11 --to-ref HEAD

[tore-espressif]

@jeetrohan Thanks again for the PR, I'll take over and fix the remaining things when I'm free

[jeetrohan]

@espzav , @tore-espressif If I'm not wrong the pre-commit failed because of incorrect indentation, which it has fixed (or so it indicates in output). A rerun should do it.

The pre-commit job is always run on latest changes, so there are probably still some formating errors.

If you want to fix them locally, in your esp-bsp folder you can do

pip install pre-commit && pre-commit install

To install pre-commit. Then you can run the pre-commit check on you last 11 commits like this

pre-commit run --from-ref HEAD~11 --to-ref HEAD

@tore-espressif
Thank you.
I'll do this at the earliest. I'd have done it since the beginning but as I mentioned it was my first time using the git. So, I think I'll still need to look more into some documentation to do this properly.
I'll follow these for the next update onward too, so that merging process is not hindered by these simple problems which should be resolved at my end itself.

[jeetrohan]

@jeetrohan Thanks again for the PR, I'll take over and fix the remaining things when I'm free

@tore-espressif I totally understand that. I myself had thought to do pre-commit test on branch, but due to some other liabilities and my lack of knowledge (about git itself) I wasn't able to do it ( even though I really want to).
I'll keep you posted, once I'll add more functionality (& this time with pre-commit check. I believe I should've been the one to do it.)
Thanks again.