Bootloader test

[dmitri]

Since you can write the bootloader, I presume you can write the MegaDrum firmware.
Write the MegaDrum firmware and using MIDI-OX make sure that MIDI is working over USB. After that try MegaDrum Config Tool and make sure you can send/receive settings to/from MegaDrum.
Only after you've made sure MIDI is working over USB, write the bootloader firmware and try load the MegaDrum firmware with the bootloader using either MIDI-OX or better MegaDrum Config Tool.

ok i have writen the firmware via megadrum config tool, but it didn't reset it self...and when i reset manuallly as the program suggests, i just go back to square one with the boxes, and when i push left all i get is the sysex screen.

This is not what I suggested you to do.

[hartl0602]

Since you can write the bootloader, I presume you can write the MegaDrum firmware.
Write the MegaDrum firmware and using MIDI-OX make sure that MIDI is working over USB. After that try MegaDrum Config Tool and make sure you can send/receive settings to/from MegaDrum.
Only after you've made sure MIDI is working over USB, write the bootloader firmware and try load the MegaDrum firmware with the bootloader using either MIDI-OX or better MegaDrum Config Tool.

ok i have writen the firmware via megadrum config tool, but it didn't reset it self...and when i reset manuallly as the program suggests, i just go back to square one with the boxes, and when i push left all i get is the sysex screen.

This is not what I suggested you to do.

sorry forgot to mention that part...i had hooked megadrum up to my mac and i was getting notes through to garage band; would this be the same as using mid-ox for checking midi-usb comunication?

[dmitri]

sorry forgot to mention that part...i had hooked megadrum up to my mac and i was getting notes through to garage band; would this be the same as using mid-ox for checking midi-usb comunication?

And did you try it with MCT to test two-way communication?

[hartl0602]

sorry forgot to mention that part...i had hooked megadrum up to my mac and i was getting notes through to garage band; would this be the same as using mid-ox for checking midi-usb comunication?

And did you try it with MCT to test two-way communication?

no i didn't; do i try it with firmware installed or with the bootloader installed?

[dmitri]

You have to test it with MegaDrum firmware already installed. You need to test that you can receive/change/send settings with MCT.

[scilence]

it seems i am having this problem too. All i get is the 16 boxes on the top. I have tested in midi-ox and all inputs work. used MCT and loaded settings from the megadrum changed them saved them restarted the megadrum loaded them and it kept the change i had made. I am not using the bootloader just programmed with cable

[dmitri]

it seems i am having this problem too. All i get is the 16 boxes on the top. I have tested in midi-ox and all inputs work. used MCT and loaded settings from the megadrum changed them saved them restarted the megadrum loaded them and it kept the change i had made. I am not using the bootloader just programmed with cable

Completely different problem as far as I can judge. You have an LCD problem.

[dmitri]

This is a new version of the bootloader. This version has a kind of protection from accidental MegaDrum firmware erasure.
In this version, you not only need to press DOWN to erase an old firmware, but also send "F0 7F 41 F7" SysEx message first and wait a couple of seconds before sending a new MegaDrum firmware SysEx.

MegaDrum_bootloader.zip

Source code:

BootloaderSysex.zip

The old MegaDrum firmware will be erased only if the bootloader receives the "F0 7F 41 F7" SysEx after you pressed DOWN so there is no way to accidentally erase it by pressing buttons.
I hope elrules will add support for this bootloader feature in a new version of MCT.

[Synthex]

Very very good feature Dmitri !

[Sonic]

Hi, Dmitri!
Whether it is necessary to expose with the new software a tag on BootLock11 at programming? And, if Mega 32 it is stitched for the first time, whether it is necessary to enter " F0 7F 41 F7 ", or it concerns only to earlier stitched AVR?
Thanks.