Like I said before, a 'headless' megadrum has fewer components and is therefore easier and less expensiveto build.
With no buttons or LCD it follows that it must also be more reliable too.
There are four requirements to the above:
1. Be backward compatible with existing designs.
Succ-U-Bus is compatible with all standard MIDI baud rate designs.
2. Replace all of the
bootloader button operations.
Succ-U-Bus is controlled by the MCT.
3. Handle the manual 'power-up' "RIGHT" key (reset) sequence.
As a general enhancement to megadrum I would suggest a MIDI spec' RESET sysex should handle this.
4. MCT must be able to enter the
bootloader at any time without needing the manual 'power-up' "LEFT" key sequence.
Succ-U-Bus v0.7 currently responds to the existing megadrum ERASE sysex but because there is a standard
mechanism to 'locate' a particular device on the system - I suggest that in any future versions use the standard
MIDI spec' DEVICE ID sysex.
Megadrum Succ-U-Bus *test version *
+ Hardware:
Should work with any 644 using any xtal - from 12Mhz upwards, but mostly
tested on a 644p @ 16Mhz... (The code for smaller devices is in place but untested).
+Software:
MCT built for XP with java version "1.6.0_07" (Oops!)
Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
Java HotSpot(TM) Client VM (build 10.0-b23, mixed mode, sharing)
+ To try the three supplied AppFWtest files:
Burn Succ-U-Bus.hex
Delete or otherwise save your MegadrumConfigTool options directory to check out the
'first run' port scan.
Run the supplied test .\dist\MegadrumConfigTool.jar.
NB.
It is ok to leave the bootlock fuses.unset.
Although this MCT test build has a 9 second time out for a manual reset of the AVR, if you
want to test it with your own firmware then that should be able to respond to an ERASE sysex by
doing a WDT reset (although see requirement 4 above).
Ken Forgettable 091118
<CUT>
So what advantages are there in this for the vast worldwide megadrum community?
Well - you don't need the unsupported Midiport.dll on the Microsfot platfrom, in fact what you end up with is a pure java cross-platform MIDI
bootloader that actually works (All due respect to Florian here).
Succ-U-Bus has error codes - these highlight hardware and/or OS comm's errors (and don't think there aren't any).
Succ-U-Bus disables the new firmware until the very last byte is verified as being flashed correctly - you can unplug megadrum while the update is in progress without your brains turning to mush.
+ MCT can find a Succ-U-Bus
bootloader on any PC automatically
+ Succ-U-Bus lets the MCT know which firmware Dimtri has released is suitable for it's hardware.
The Succ-U-Bus debugger CAN EVEN MAKE TEE!
<CUT>
With regaurds to AVR freaks - did I mention Succ-U-Bus can do fragmented hex records too?