Windows: chrome.usb misbehaves on control-out transfer without payload
Reported by
andrzej....@gmail.com,
Apr 22 2016
|
||||
Issue description
Chrome Version : 50.0.2661.87 (Oficjalna wersja) m (32-bitowa)
URLs (if applicable) :
Other browsers tested: chromium for linux
Add OK or FAIL after other browsers where you have tested this issue:
Safari: NOT APPLICABLE
Firefox: NOT APPLICABLE
IE: NOT APPLICABLE
What steps will reproduce the problem?
(1) Clone gitlab repository https://gitlab.com/aszu/DigisparkUSBTemplate
(2) Checkout to tag chrome_interrupt_issue
(3) Connect to device (manifest.json tweaking may be required unless
you use firmware for Digistump Digispark that is attached)
(4) Send control-out transfer without any data.
What is the expected result?
Expected result: transfer is succesful (and this is the case when running Linux version).
What happens instead?
Transfer failed with result code 1.
--
The repository contains chrome app that uses chrome.usb API and the source code for the firmware for digispark, that was using to test the issue (the project was started for something like workshop on MCUs).
If you wish, I may provide compiled version of firmware for digispark, if you have hardware for it handy ;). But the issue was reproducible also on other devices, so I believe this is not a requirement.
,
Jul 1 2016
,
Jun 7 2017
,
Jun 8 2018
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||
►
Sign in to add a comment |
||||
Comment 1 by tkonch...@chromium.org
, Apr 25 2016