Page 1 of 2

Lost in arv programming/updating

PostPosted: Sat Oct 17, 2009 7:36 pm
by julijustri
Hello friend. First: sorry for my bad english. I read a lot of messages of this forum and i know that this theme is the most "popular", but i stuck doing it and i don´t know to do. I´m triyng to update the avr because the MCT try to recor something about a slot 1 and, in this moment, the MD doesn,t work correcly. I try to update, to record firmware with midi-ox, but say to me somethin about "enough memory for sysex records" (Ya ya, i indicate ouput buffers to 60000). I don´t have idea to do anithing. My megadrum is a synthex kit of 56 inputs , very recently. I hope will be work again, thanks in advantage, from Spain!!

Re: Lost in arv programming/updating

PostPosted: Sat Oct 17, 2009 8:12 pm
by dmitri
I'm sorry but I'll have to point you to this: viewtopic.php?f=3&t=352
This is how the questions should look like when describing a problem: viewtopic.php?p=11629#p11629
And also I advise you to find someone who can properly translate from Spanish to English so that I had a chance to help you.

Re: Lost in arv programming/updating

PostPosted: Sat Oct 17, 2009 9:10 pm
by julijustri
Well, in this moment i only have a megadrum kit without pads. Is a syntex kit, with programmed mcu and pic. The oscilator is 20 Mhz for avr and 12Mhz for PIC. ¿Is fossible i do anithing that corrupt the bootloader and for this i have a lot of problems?. I have the possible solution for my problem programming via rs232 and LPT1, but my laptop not have any of these ports. I´m trying to write the firmware with MIDI-OX, and readind other messages, i follow the instructions to use this program, but always send messages like "No output device is selected or there are no sysEx buffers, only manual dump is supported", or "not enough memory for sysEx in buffer n.1". With MCT can write firmware, but the screen of MD only puts "Fw updater 20 Mmz send sysEx now" and no more. My question is about not work correctly the MIDI-OX program, and if i can´t program via USB, how i can program the MCU without LPT (I only have a usb to rs2 converter and works to others aplications like TE-20 programmer). Thanks for all.

Re: Lost in arv programming/updating

PostPosted: Sat Oct 17, 2009 9:20 pm
by dmitri
Sorry, but I couldn't understand your description of the problem and, of course, how you tried to fix it.

Re: Lost in arv programming/updating

PostPosted: Sat Oct 17, 2009 9:39 pm
by julijustri
There isn´t other way to write the firmware ??? Only can write firmware by USB or MIDI??? The MEGADRUM is dead after connect with Megadrum Config Tool. . Before this worked correctly with addictive drums. thanks.

Re: Lost in arv programming/updating

PostPosted: Sat Oct 17, 2009 10:01 pm
by dmitri
If Atmega has a bootloader, you can upgrade firmware over USB/MIDI.
If Atmega dosn't have a bootloader, you can write a bootloader or firmware with an ISP cable.
Both of these procedures are described in in http://www.megadrum.info/content/programming-mcus

Re: Lost in arv programming/updating

PostPosted: Sun Oct 18, 2009 10:07 am
by Firelord
julijustri wrote:There isn´t other way to write the firmware ??? Only can write firmware by USB or MIDI??? The MEGADRUM is dead after connect with Megadrum Config Tool. . Before this worked correctly with addictive drums. thanks.

So you already had MegaDrum running and after trying to update via MCT MD does not boot up any longer?

I should point out that this is not the only occasion. There is a bug in there somewhere causing this. And it might have something to do with ATMega's fuses.

Now, what I've noticed myself: when you program fuses first (as documented) and then program flash memory, the BLB11 & 12 bits are reset to their unprogrammed state leaving the bootloader section vulnerable to SPM, so whatever the problem, the documentation on programming the chips could be inaccurate.

Re: Lost in arv programming/updating

PostPosted: Sun Oct 18, 2009 11:01 am
by dmitri
Firelord wrote:Now, what I've noticed myself: when you program fuses first (as documented) and then program flash memory, the BLB11 & 12 bits are reset to their unprogrammed state leaving the bootloader section vulnerable to SPM, so whatever the problem, the documentation on programming the chips could be inaccurate.

You are right, my mistake in the documentation. I've changed the order now.
Nevertheless, it might be irrelevant here since from julijustri's description it is impossible to figure out if he can enter bootloader or not.

Re: Lost in arv programming/updating

PostPosted: Sun Oct 18, 2009 12:02 pm
by Firelord
I've managed to decipher some information from the previous posts :-) (no offence, julijustri!)

So, presumably the bootloader is still working, since the 'Fw updater 20 MHz send sysEx now' message appears. In this case I put my money on wrong MIDI-OX settings.

julijustri, set both buffers in the SysEx settings to 60000. Then send the erase firmware file 'erase_firmware.syx' and then send the correct firmware syx file. Also make sure you have MegaDrum in the Input/Output devices settings in MIDI-OX.

Re: Lost in arv programming/updating

PostPosted: Mon Oct 19, 2009 2:14 pm
by julijustri
I try to did that, exactly you says about a MIDI - OX config, buffers, send erase file and send firmware, but the MIDI - OX program report many errors about "not enought memory for sysex buffers", and i follow the instructions i found in this web. In other laptops i´m trying to do the proccess, but doesn´t work, similar errors like this. If i dispose a LPT port for re- program atmega... Thanks to everybody!