Society of Robots - Robot Forum
Software => Software => Topic started by: GWER57 on February 26, 2010, 10:40:30 AM
-
Hi, I was looking for a makefile to use on an ATMega 64A, I downloaded the axon(original) makefile and was wondiring if i could just change:
MCU = atmega640
to:
MCU = atmega64A
Also, is there anything else i should change? I noticed that the makefile was almost identical to the makefile for the iRobot Create, with a few setting changes, so i assume that i can't mess much up by changing a few things (not the fuses though). But until i hear for sure i'll put everything on hold.
And lastly, what would i have to mod to be able to apply the SoR uart / i2c / any comm protocol to be able to use it on the 64A?
Thank you very much in advance!
-
I just realized that there is a default makefile that pretty much everything is derived from.
So my only remaining question is if it will harm anything by playing with the various optimization level?
-
I just realized that there is a default makefile that pretty much everything is derived from.
So my only remaining question is if it will harm anything by playing with the various optimization level?
Short answer: no.
Long answer: optimization should not modify the semantic (~ behavior) of your program. Except some cases
like delays implemented with busy loops. In these cases there are solutions to prevent the optimizer from
removing the empty loop.
Why do you want to play with optimization?
Chelmi.
-
I was just curious if changing some of the parameters of the makefile would brick my mcu or not.
-
If the makefile modifies fuses, you might brick it. Optimization parameters (-O) are safe :)
-
Cool, thanks.
Yeah i wasn't interested in changing the optimization level but that was the most convenient example i could find of what i meant.