History of MegaDrum firmware versions

[dmitri]

When MegaDrum starts it checks the version of the EEPROM content. If it differs from the firmware version it invalidates all existing saved configs in the EEPROM and won't load anything from it until new configs have been saved. Yet it doesn't prevent you from sending incompatible configs to MegaDrum over SysEx which wil very likely screw things up.

[Ken Forgettable]

Does the MIDI LED flash for SysEX messages!

[dmitri]

Does the MIDI LED flash for SysEX messages!

It doesn't.

[kimouette]

Well the latest firmware does the same thing with my MD

Oh and another weird symptom that goes with the Vu-Meter blocs problem... a sound! A sound coming from my tom piezo whenever I have one of the two laterst firmware installed. That bug is terrible. It literally makes my piezo squeal! I hope it didn't kill it! Didn't have the time to check this morning.

I'll try to look at that Cocoa source code... but even though I'm the only one with this weird bug, I still dont understand how MCT could manage to let me install a firmware correctly and not a certain upgrade of that same firmware

Geez I'm really starting to pile up problems!

Borrow a PC, install the latest firmware using MIDI-OX just make sure it is MCT which causes the firmware corruption.

I bought a PC and installed the latest firmware using midi OX. No problem during the installation.
Everyhing seems fine until I load config 2 (config 1 doesn't cause any problem anymore ). But config 2 shows the exact same thing as it did (a weird big Vu-Meter and only drum maps can be chosen when I press any button).

It's not the end of the world. But still, I'd like to understand whats happening and why I am the only one experiencing this!

[dmitri]

I bought a PC and installed the latest firmware using midi OX. No problem during the installation.
Everyhing seems fine until I load config 2 (config 1 doesn't cause any problem anymore ). But config 2 shows the exact same thing as it did (a weird big Vu-Meter and only drum maps can be chosen when I press any button).

It's not the end of the world. But still, I'd like to understand whats happening and why I am the only one experiencing this!

Describe the whole process to reproduce it starting with the loading firmware and not omitting how you change settings and save/load configs.

[kimouette]

I bought a PC and installed the latest firmware using midi OX. No problem during the installation.
Everyhing seems fine until I load config 2 (config 1 doesn't cause any problem anymore ). But config 2 shows the exact same thing as it did (a weird big Vu-Meter and only drum maps can be chosen when I press any button).

It's not the end of the world. But still, I'd like to understand whats happening and why I am the only one experiencing this!

Describe the whole process to reproduce it starting with the loading firmware and not omitting how you change settings and save/load configs.

Geez, I wonder what happened. The bug disapeared!

The only thing I did between yesterday and today, is use MCT to import all settings from MD and overwrite my 2 configs (which I've never done before since MCT didn't allow me to send my pad's settings to MD using my Mac).

I guess I was "carrying the bug" for a while and saving with MCT kinda "cleaned" my configs.

That's odd, but everything seems normal now!
Thanks anyway

[gabriel1712]

Geez, I wonder what happened. The bug disapeared!

The only thing I did between yesterday and today, is use MCT to import all settings from MD and overwrite my 2 configs (which I've never done before since MCT didn't allow me to send my pad's settings to MD using my Mac).

I guess I was "carrying the bug" for a while and saving with MCT kinda "cleaned" my configs.

That's odd, but everything seems normal now!
Thanks anyway

I had the same issue with old configs messing up new firmware. It's not a bug, but a competability issue, really. With all the firmware changes to the hihat lately, trying to load old configs (via MD load config or via MCT All to MD) is a really bad idea. You can use MCT to load pads, except HHpedal ONE-BY-ONE. HHpedal has to be set manually in MD settings. Don't forget to overwrite the bad config once you're up and running.

If your config already is messed up, boot MD with RIGHT button held. That'll start MD with the new firmwares default settings. If the MD menues is back to functional and without the weird symbols, you'll know who the villain is.

[kimouette]

I had the same issue with old configs messing up new firmware. It's not a bug, but a competability issue, really. With all the firmware changes to the hihat lately, trying to load old configs (via MD load config or via MCT All to MD) is a really bad idea. You can use MCT to load pads, except HHpedal ONE-BY-ONE. HHpedal has to be set manually in MD settings. Don't forget to overwrite the bad config once you're up and running.

If your config already is messed up, boot MD with RIGHT button held. That'll start MD with the new firmwares default settings. If the MD menues is back to functional and without the weird symbols, you'll know who the villain is.

Like I said, the weird symbols disappeared, but what you wrote makes sens!
I'll do that tonight.. I'll load my latest config on MD and send each pad's setting (except HH pedal) into MCT. I'll boot MD with right button held and then, send each pad from MCT back to MD and save that as config 1.

I dont have many pads anyway, so I might just do that everytime I have to update the firmware.

[gabriel1712]

Like I said, the weird symbols disappeared, but what you wrote makes sens!
I'll do that tonight.. I'll load my latest config on MD and send each pad's setting (except HH pedal) into MCT. I'll boot MD with right button held and then, send each pad from MCT back to MD and save that as config 1.

I dont have many pads anyway, so I might just do that everytime I have to update the firmware.

If all is well, you should just load each pad from MCT, manually set Pedal in MD and save the config.

The right button thing is for when things are a royal mess and you need a clean start without reinstalling the firmware.

[Ken Forgettable]

Dmitri hi,

+ Because the ATmega32 seems to becoming more expensive than the ATmega324p, can you build a 16MHz version of the next firmware for the ATmega324p please?

+ If you were to use different mCUs on the same board (same speed xtal and number of inputs) do you just need to consider the memory sizes and some port #defines for different builds?

Hi, It's me again. (The central scrutiniser).

+ If I woke up in a ditch and it smelt good. Do you think I could still get funding