Latest MegaDrum firmware version

[timekeeper]

For some reason my LCD doesn't work, all though I thoroughly checked for shorts and found none... I have version 20101020 and I would like to update the atmega to the latest firmware. So I need to be sure how to blindly select the 20Mhz crystal (that's what I have). So, after I start Megadrum with left button pressed, does it still start with the 16Mhz crystal as the default selection? What will happen if I select the wrong frequency (I hope I won't)? Is there any command-line utility where I could pass the right frequency as a parameter? Too many questions, I know....
Thanks once again!

[dmitri]

For some reason my LCD doesn't work, all though I thoroughly checked for shorts and found none... I have version 20101020 and I would like to update the atmega to the latest firmware. So I need to be sure how to blindly select the 20Mhz crystal (that's what I have). So, after I start Megadrum with left button pressed, does it still start with the 16Mhz crystal as the default selection?

It is a bootloader which starts when the left button is pressed and it doesn't change so when it starts it defaults to 16MHz. You have to press Up once to choose 20MHz.

What will happen if I select the wrong frequency (I hope I won't)?

Upgrade just won't work.

Is there any command-line utility where I could pass the right frequency as a parameter?

No and there is no need for that.

[timekeeper]

For some reason my LCD doesn't work, all though I thoroughly checked for shorts and found none... I have version 20101020 and I would like to update the atmega to the latest firmware. So I need to be sure how to blindly select the 20Mhz crystal (that's what I have). So, after I start Megadrum with left button pressed, does it still start with the 16Mhz crystal as the default selection?

It is a bootloader which starts when the left button is pressed and it doesn't change so when it starts it defaults to 16MHz. You have to press Up once to choose 20MHz.

What will happen if I select the wrong frequency (I hope I won't)?

Upgrade just won't work.

Is there any command-line utility where I could pass the right frequency as a parameter?

No and there is no need for that.

Thanks once again!

[timekeeper]

Your new 20110510 firmware solved my problem viewtopic.php?p=18366#p18366 You're great man!!!

[Alworx]

Your new 20110510 firmware solved my problem viewtopic.php?p=18366#p18366 You're great man!!!

Seems like I had a similar issue with my MD that has also been solved with this "magic" update! (Couldn't test it excessively though because of my neighbors ).
Second thing that apperently has been solved was the issue http://www.megadrum.info/forums/viewtopic.php?f=3&t=1546, which was driving me crazy!

Thanks a lot for the firmware update, Dimitri! Got me a lifetime closer to a fully working MD.

One question still remains: Is the only difference between 20110510 and 20110424 really the i2c eeprom, or did you implement any other improvements or bugfixes?
Just wondering why the mentioned issues suddenly disappeared (not that i'm not greatly glad about it)...

Greets

[dmitri]

I've just double checked the changes I've made between 20110424 and 20110510 versions and they are I2C EEPROM related only.

[Alworx]

Thanks for checking.
In the meantime i've done some further testing, finding out that both problems returned/remained...
Seems like my MD needs some more bugfixing...

[timekeeper]

Dmitri I think I found I bug.
Firmware version: 20110510
MD Manager version: 20110415
PCB: Synthex v2.5 32 inputs

The problem:
MD Manager communicates correctly with Megadrum. All auxiliary inputs have their notes set to 0 (disabled). Lets say, I change the Kick note to 50 (could be any number), then press the blue arrow to copy the new setting to all pads. Then I press "Send All". All inputs except the Aux ones, will produce note 50. Aux will produce nothing. I close MDManager, then I open it again. Megadrum is detected. I press "Get All". Now all previous changes are there (all input have their note set to 50), except the auxiliary which are set to 0 again...

[dmitri]

Dmitri I think I found I bug.

Sorry but I cannot reproduce the problem.

[timekeeper]

Dmitri I think I found I bug.

Sorry but I cannot reproduce the problem.

OK my friend, I will try it with my old laptop running WinXP and report back in 2 days, since it's late now and I will be away for tomorrow. From your experience, what would be the right behavior on behalf of Megadrum? Should it keep the changes made in Aux inputs (since being applied to all other input and still persisting after a full power off circle testifies that some changes took place) ?