Failed Update

[dmitri]

At this stage, provided you select the right crystal frequency, i.e. matching the actual Atmega crystal and that you actually press the DOWN key (i.e. it is not mixed up with the RIGHT key) and that your MIDI LED is really ok (which I doubt, and your bootloader is in fact of an old type) I would suggest you to try the procedure on another computer.

This is why I assumed I had a new bootloader:

5 down button on MD. The LED should come on (but it didn't).

Looks like you have the latest version of the bootloader after all so you should do it with MIDI-OX. Follow this: http://www.megadrum.info/forums/viewtopic.php?f=3&t=622 and come back with the results

Confirmed crystal is 16MHz. If I had pressed the right button, would the 'send Sysex now' message appear?

It would and it could probably change the bootloader frequency without you even realising it for the reason I explained a few posts before in http://www.megadrum.info/forums/viewtop ... 7272#p7272

I will double check the wiring. If my LED is not working, it must've broken while installed. I know that it worked before I tried updating. I have a laptop so I will install the necessary programs and give it a shot on another computer.

[The reason I doubt that the bootloader in your Atmega of a new type is that you were able to erase the MegaDrum firmware by just pressing keys in first place. Who did you get your Atmega from?

Synthex

Why wouldn't you double check with Synthex what version of a bootloader you have?

[Thurston]

It would and it could probably change the bootloader frequency without you even realising it for the reason I explained a few posts before in viewtopic.php?p=7272#p7272

Got it, thanks.

Why wouldn't you double check with Synthex what version of a bootloader you have?

MCT reported that I hard an older version but what you had said seemed to say different. I guess I just got confused.

Anyway...I tried updating without using the erase_firmware.syx file and instead loaded the latest version in MIDI-OX. After a few seconds a sucessful update!!!

Could this be a bug with MCT? I'll get in touch with eRules and direct him to this thread in case there have been similar cases.

Thank you once again for all your help dimitri. You deserve a lot of credit for giving a new guy like me so much time to get this figured out.

[dmitri]

It would and it could probably change the bootloader frequency without you even realising it for the reason I explained a few posts before in http://www.megadrum.info/forums/viewtop ... 7272#p7272

Got it, thanks.

Why wouldn't you double check with Synthex what version of a bootloader you have?

MCT reported that I hard an older version but what you had said seemed to say different. I guess I just got confused.

Anyway...I tried updating without using the erase_firmware.syx file and instead loaded the latest version in MIDI-OX. After a few seconds a sucessful update!!!

Could this be a bug with MCT? I'll get in touch with eRules and direct him to this thread in case there have been similar cases.

Thank you once again for all your help dimitri. You deserve a lot of credit for giving a new guy like me so much time to get this figured out.

Good that it worked after all! Was the MIDI LED flashing when you were sending the firmware sysex? Is the MIDI LED working now?

[Thurston]

I'm not sure if the MIDI light flashed while sending firmware sysex. I'll check it next time (although I'm nervous to do it again).

However, LED is working. I plugged in my first foam cone style, mesh head DIY tom to input 7. Without yet going through the configuration process for megadrum, MCT is reading a constant MIDI note 38 at a level of 2 as if I'm constantly doing a soft, fast drum roll. The MIDI LED appears constantly lit to coincide with the MCT MIDI log. I'm hoping after I configure the MD this will only occur when the drum is actually struck.