[sdiy] FW: Simple MIDI Seq for firmware updates
MTG
grant at musictechnologiesgroup.com
Sat Mar 13 06:00:41 CET 2010
> Boot loaders are a bit tricky, you need to know the image is not corrupted
> and need to be able to roll back to the original boot loader in the case
> of
> a programming flaw, incomplete program update, memory corruption etc. A
> simple way to do this using a protected (hardware write protection is
> best)
> boot loader that is always in place, the system starts the boot loader
> runs
> a checksum on the image and looks for an abort load signal of some sort.
> The
> abort signal can be a jumper or other message. If there is no abort signal
> received the loader executes the program.
Thanks for the good tips above and below. I have a bootloader working well
over RS232, but for obvious reasons I don't want to have people pull out a
DB9 cable. Also, I don't really want to write a MIDI app of my own at this
time because that would be a steep hill to climb right now (unless someone
has a great Borland MIDI component). But I digress...
> Now using MIDI System Exclusives is not hard, and its function is open
> ended.
> For the handshake your target system can Send a System Exclusive message
> block of its own. A MIDI receiver is also allowed to act as a MIDI
> transmitter.
I don't think a handshake is possible if I use a SysEx loader like MidiOx or
a sequencer to play MID files. Right?
GB
More information about the Synth-diy
mailing list