Incorrect bInterfaceProtocol value for ACM Serial

[greatscottgadgets]

Incorrect bInterfaceProtocol value for ACM Serial

[ktemkin]

Thanks for reporting this -- it looks a lot like I typo'd and inserted a 0x02 when I meant 0x01. Testing stuff out on macOS now and will report back. :)

[BracketMaster]

Haha. No probs.
Also, MacOS wouldn't allow me to write to the device with screen.
I was however able to write to the device directly with PyUSB...

Which brings me to my next comment. Perhaps it might make sense to
include a PyUSB serial demo in the same folder as the ACMSerial demo
python code.

[ktemkin]

MacOS seems happy with the technically-correct value of 0x01. About to test on Windows.

Also, MacOS wouldn't allow me to write to the device with screen.
I was however able to write to the device directly with PyUSB...

There was another bug that I think was triggering this behavior (macOS was interleaving control request transactions with its IN tokens; and a bug in handling that caused the IN endpoint to get stalled). That's fixed in 087ad9c, and dterm seems happy to work with the terminal.

I'll try screen after I try Windows to verify. :)