Version 0.7

• Enabled write access to VMU memory
  • Use at your own risk (not thoroughly tested yet)
    • To use on Windows or Linux, copy file exactly 128 kb in size and with the same name of the target VMU to the drive
    • Deleting files is not internally supported, even if the OS appears to successfully delete the file
    • The DC-Memory drive appears to have 128 kb of free memory, but this is just for the host operating system to proceed past the check for enough memory before allowing overwrite; writing a file with a unique name to this empty space will always fail
  • Drive will detach if too many write failures occur, will reattach once any VMU is removed and re-inserted
    • Write to a block of memory is retried until timeout
    • A "failure" is flagged if access timeout is reached for any block of memory (250 ms for write); 50 failures will cause the drive to detach
    • The host will usually attempt to write another block of memory and try to return to this block later; drive detach was added to prevent this infinite loop in the event of a major fault
  • It takes 15 seconds to write a full VMU file
  • Things will get weird if any VMU is added or removed during read or write which will be addressed later (#19)
  • Refer to this tool to be able to view/modify contents: http://evmu.elysianshadows.com/
    • Export from this tool directly to drive does not currently work; instead, export file to local system before copying to DC-Memory
• Fixed some USB CDC serial interface issues
  • Handle all different types of end-of-line (CR, CRLF, LF) and backspace (BS, DEL) characters properly
  • Handle multiple commands at once (if more than one end-of-line received in a batch of characters)
  • Output CRLF instead of just LF
  • Output bus index (0-3) that custom command was sent on ex:
    09414001 00000008
    11: added {09414001 00000008} -> [1]
    11: complete {08404102 00000008 FF000000}
    09010001 00000008
    5: added {09010001 00000008} -> [0]
    5: complete {08000102 00000008 FF000000}
• Minor tweak to attempt to correct for occasional Maple Bus write issues
• Increased MAPLE_RESPONSE_TIMEOUT_US to 1000 to help with VMU access
• Function definition found in device info is passed to peripheral