Has anyone ported the umpl code to compile as an ATMega 328p target? Would you be willing to share your project file?
There seem to be a number of pitfalls with this activity.
Thank you!
- Log in to post comments
phpbb Topic ID
14016
Re: Re: MotionApps 2.0 AVR Studio 5.0 - ATMega 328p Target
For anyone interested in the outcome of this effort... Motion apps does not appear to work on an ATMega328. Unless someone has any suggestions for compiler settings.
Device: atmega328p
Program: 128578 bytes (392.4% Full)
(.text + .data + .bootloader)
Data: 11516 bytes (562.3% Full)
(.data + .bss + .noinit)
This result was obtained using the following compiler settings:
avr-gcc.exe -funsigned-char -funsigned-bitfields -Os -ffunction-sections -fpack-struct -Wall -c -std=gnu99 -mmcu=atmega328p -MD
Linker settings:
avr-gcc.exe" -Wl,-nostartfiles -mmcu=atmega328p -Wl,-lm -Wl,-lc
Re: Re: MotionApps 2.0 AVR Studio 5.0 - ATMega 328p Target
@lgreenlee wrote:
MotionApps is pretty bloated, as capable as it is. What about this approach instead, which is admittedly less feature-complete (not to mention still in progress), but maybe more like what you can use?
http://www.i2cdevlib.com/devices/mpu6050
- I2Cdev class .cpp/.h foundation files (basic I2C abstraction)
- MPU6050 class .cpp/.h device files (with straightforward methods for working with each register)
- Working Arduino sketch example
That's all there is to it. The code is WAY smaller than MotionApps, full of Doxygen comments, and much more portable. The DMP functionality isn't there yet, but I'm working on it.
Re: Re: MotionApps 2.0 AVR Studio 5.0 - ATMega 328p Target
J, your whole project is a great piece of work (*bows before you*).