I want to use a ATMEGA2560 in a future Project.
Till now i used a ATMEGA1280 CPU which was easily burned with a bootloader by using the arduino ide and a usbtiny.
I googled for ATMEGA 2560 support in the web, but there seem to be many workarrounds.
I use a unmodified Arduino 022 IDE
It would be nice to use a bootloader which can use the whole 256kb of the 2560, but is this possible with the stk500 protocoll, or is stk500v2 needed, it seems yes.
As far i understood there is a workaround for the stk500 in which only 128kb are adressed.
And as far i understood there is a way to use the 256kb when using the stk500v2 protocoll.
So the question ist is it impossible to use the STK500 only USBTINY for using the 256kb?
Where do i find the newest bootloader which support the 256KB?
How do i burn it, i suggest with the DIamexSTK500 and AVRDUDE and the AVR-BURN-OMAT, using the Arduino IDE would be my favorite choice?
The Arduino Mega2560 uses a different bootloader than the Uno, and that bootloader does use STK500v2, and as far as I know it does support 256K (minus the bootloader size (8k!)) sketches. (and has additional features, too.)
Many thanks, i burned the Atmega2560 Bootloader from the Arduino 022 with AVRStudio by a STK500V2 capable programmer.
I think this will enable the 256kb, thanks for the reply.
Hi, I'm trying to build the .hex file that ultimately turns into the stk500boot_v2_mega2560.hex file. I made what I think are the necessary adjustments to the makefile under hardware/arduino/bootloaders/stk500v2 and can run "make clean; make all" to create a stk500boot.hex file. I've also modified the 'program' rule in that makefile to allow me to directly download to my 2560 using avrdude -c avrispv2. When I run this on my board, I am able to type '!!!' and it returns the multiple lines of exclamation points indicating that the firmware has entered the RunMonitor() function; however, after that the code uses PrintFromPROGMEMln() and the loop looking for a null terminator never ends because the data pointed to is 0xff. The .hex file appears to have the data consistent with the .lss file; however, the data pointed to in the runtime code doesn't seem to agree with that. Not being very familiar with AVR, I'm hoping someone can give me the magic formula (probably some parameter in the makefile I haven't set) that will get me over this.
Anyone know what I'm doing wrong?
Thanks,
Ed