www.megadrum.info

Been using my MD all day with no problems, then I loaded MCT to load in the latest firmware, but now when it boots I get a steady blinking backlight with the LED lit solid, but it doesn't boot. I can boot with left button for it to receive firmware, but it's not getting it from my MCT. I'm running version 1.5 on an intel macbook pro. I tried doing it from my PC and I get an error sending sysex. What can I do now? I downloaded midiOx, but it doesn't seem to be doing it either, but I'm not familiar with that program, so I may be doing something wrong.

I must add to the help manual the installation steps for Mac users as they are a bit tricky...

Download mmj:
http://www.humatic.de/htools/mmj.htm

To make mmj available to all Java applications simply drop both mmj.jar and libmmj.jnilib into /Library/Java/Extensions

Now MCT should work more or less better (it's not clear if it depends on the version of the OS you have).

Make sure you have configured correctly the Hardware options in MCT so they match your Megadrum.

Try several times. Sometimes when you don't have a perfectly assembled hardware or if you use a wrong crystal, it is very difficult for it to update correctly. Are you overclockint the atmega?

Probably is a hardware issue. Let me now your progress

I already had those 2 files in my extension folder from when I first installed MCT. Settings are all correct, although I don't know if the SYSEX send setting would work better at a setting other than 100(ms).

Should the MD react in anyway when it's receiving the sysex? I've read that the let should flash, and that it should re-boot when completed, but then I've also read that in fact it Doesn't do this??

Could I use ponyprog to update the firmware?

on my PC I get "error sending the sysex file"

jeffbeckib wrote:Could I use ponyprog to update the firmware?

Don't try that yet; you could trash the bootloader!

Make sure you have the correct firmware and try MCT from a PC.

I've tried from the PC and I get error sending the sysex file
I've tried loading both the 32_16_32_20090306.sys, and the 32_16_32_20090211.sys, both give the same error.
MCT is set to "usb audio" on both midi in and out, don't know if anything else needs to be changed.
MCT must see the MD because everytime I run MCT it confirms that I'm on 90211 and tells me that 90306 is available and asks me to update the firmware. Which is how this mess got started in the first place.

This is from the application log:

10:28:03 INFO: Initialization started
10:28:03 INFO: Configuration file read successfully
10:28:03 INFO: Input names file read successfully
10:28:07 INFO: MIDI IN connection opened
10:28:07 INFO: MIDI OUT connection opened
10:28:07 INFO: Megadrum settings from last session read successfully
10:28:07 INFO: Initialization finished
10:29:37 ERROR: Trying to send BIG SYSEX message The error was: MIDI error return code: 4
10:29:37 ERROR: Updating firmware
10:30:01 ERROR: Trying to send BIG SYSEX message The error was: MIDI error return code: 4
10:30:01 ERROR: Updating firmware

10:30:01 - Four

Check out MIDIOX:
..Options-> Midi Devices
....Choose the Megadrum as the output

..View-> SysEx then
....SysEx-> Configure
......Set the device output buffer size big enough for the firmware ie. 60000
......Set a long delay ie 100ms

....Command Window-> Load file (megadrum32_16_32_20090306.syx)

[Ready the Megadrum bootloader at 16Mz]

....Command Window-> Send SysEx

Check if Prosser is still outside before power cycling your brain.

PS. you may have a loose connection somewhere...

I had a problem sending a file with mine. When you go into the bootloader like it describes I had to press the right button to start transfer mode instead of down and then it worked fine. I'm not sure why it did this?