Version 0.5
- Added a TTY parser to the USB CDC (serial) interface
- Enter "h" for help
- Any command starting with ASCII hex character is interpreted as raw data in ASCII hex to send to maple bus, and the result is returned as ACII hex
example 1:
09010001 00000008
6: added {09010001 00000008}
6: complete {08000102 00000008 FF000000}
example 2 (when no VMU connected):
09010001 00000008
14: added {09010001 00000008}
14: failed read
example 3 (length in frame word doesn't match number of words given):
09010002 00000008
0: failed packet invalid
example 4 (all hex values must be present):
09010001 8
0: failed missing data
example 4 (X is ignored):
09010001 X0000008
0: failed missing data
When parsing, all non-hex characters are ignored, and exactly 8 hex characters must be present for each word. After raw ASCII hex is accepted, either the transmission ID is displayed followed by confirmation of data added or "0:" followed by failure reason. After the command is successfully sent, the next message will be transmission ID followed either by "complete" and received data or "failed" and failure reason.
The selected bus is done based on source address: {0x00, 0x40, 0x80, 0xC0} for player 1 through 4. All Maple Bus communication through this interface takes highest priority.
Any line coding variables are ignored, so it doesn't matter what BAUD rate, stop bits, parity, or number of data bits are set for this USB CDC serial interface.