Nope those were off. There were two others that appeared to be commented out: USB_HID_DEBUG and USB_HID_DEBUG_HIGH, but the setting of them to false made no difference.
FYI, to keep it simple, I have been trying the basic MSD example, with no FAT32 SD library. I also commented out all serial messages and there was no significant difference. In Windows 7, the JALLIB USB Mass Storage Device appears in the Device Manager, with no "error" as such, but there is no associated drive, nor an unmounted one in the Disk Management tab (sometimes a drive might not mount and be visible there, inactive). Vista shows an error state in the Device Manager (cannot start) and Windows 10 has the same error. An interesting observation is that the error occurs regardless if a SD card is present or not, so that indicates that the issue manifests itself even before the card is parsed. In your implementation, can you insert an SD card *after *connection, and does it "appear" as a drive thereafter? (it should if it acts like a proper removable media MSD) Thanks. On Saturday, June 4, 2016 at 9:41:39 PM UTC-4, Matthew Schinkel wrote: > > I got it working on my other PC, problem was I had turned debugging on. > This debug feature uses serial, which is too slow. > > Make sure you have both of these set to FALSE > const bit USB_DEBUG = FALSE > const bit USB_DEBUG_HIGH = FALSE > > Wireshark does show me 2 incorrect packets during startup, but the windows > machine does a packet re-request, and it works. I'll look into these errors > further. > > Do you have debug on? > > Matt > -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email to jallib+unsubscr...@googlegroups.com. To post to this group, send email to jallib@googlegroups.com. Visit this group at https://groups.google.com/group/jallib. For more options, visit https://groups.google.com/d/optout.
