I need little guidance here. I am using the latest mission planner software. (Using MissionPlanner32-1.1.86.msi) When i select the correct icon (in my case ArduCopter V2.5.5 Alpha Quad) from the firmware menu. It detects the APM1 and also starts uploading the program on the APM1 but after while i get an error saying that
"Firmware is to big for a 1280. Please upgrade!!!"
I am not sure what i am doing wrong. I have selected the correct COM port as well as the baud rate (115200). I also haven't clicked on connect in Mission Planner as it says in the Manual. It would be so much helpful if anyone give me their input on this. I have attached few screenshots of the error i got. Please take a look at them and also let me know the solutions. Thank you so much for your time.
Kur, the hexes in MP are compiled for 2560 APM1 and APM2.
For 1280 processors, you have to compile for 1280 using the arduino ide yourself, and load the hex that way.
Ellison do you happen to know if the 1280 board and 2560 board are identical except for the Atmega? I'm thinking of just replacing the chip. Been a while since I've soldered a TQFP 100 but I've done it before...
I know there are a few other differences, but I'm not sure if any of them really matter for what you intend to do. For example, the linear voltage regulator is different between APM1 and APM1.4. But obviously this doesn't matter. Also the fact that I have never seen any configuration differences with the code (other than memory space) would indicate there is no difference.
As for the original topic, maybe what would be helpful is if a developer could create an Atmega 1280 profile in APM_Config. Something that would know which features should be turned off. CLI, Test, CopterLEDS, etc.
There's no 1280 config per se, but sprinkled throughout the code there's '__AVR_ATmega1280__' checks that disables functions if you're compiling for 1280, mostly to save on memory, from what I can see. The Arduino ide sets that define to the make, if you select 1280 as the target.
But that still won't help the 1280 users, since it's MP that checks your board id, and output the message. We'd have to modify MP to load the 1280 pre-compiled hexes instead of just the message and of course we'd have to compile and place the 1280 hexes in the depository.
Andrew. 2560 has the same pins, the difference is more memory but it might be easier to make and upload your own firmware using the arduino ide or visual studio.