diff options
| author | Donald Delmar Davis <don@suspectdevices.com> | 2013-09-27 20:24:52 -0700 |
|---|---|---|
| committer | Donald Delmar Davis <don@suspectdevices.com> | 2013-09-27 20:24:52 -0700 |
| commit | bf7248f854905949cdcfef4ebe9511376d043e17 (patch) | |
| tree | 13919c56f750770fddd4260011b7b4be0c9ee49a | |
| parent | 496c23ef4d3f222139231d34177427bd03d0aafb (diff) | |
Docs.
| -rw-r--r-- | README.md | 5 |
1 files changed, 5 insertions, 0 deletions
@@ -3,6 +3,7 @@ The goal is twofold 1) to isolate the lower level usb functions from the actual and 2) to create a minimal framework for identifying resetting and loading code onto midi devices. + The majority of the usb-midi specification is in simgle 4 byte events or packets. The exception to this are sysex messages which are arbitrary in length. @@ -26,5 +27,9 @@ void SendSysex (uint8_t *messege, [interface] The remaining details should be as hidden and interchangable as possible. +A minimal sysex handler called by either the maintaince tasks or by GetMidiEvent should handle at a minimum the +universal sysex id request and response and a (mma) vender specific sysex to jump to a bootloader. This handler +also bufferes sysex's that are not ours or that it does not handle itself. + |