DAPLink WebUSB identified as LPC1768 on first connection
- Dominant language
- C
- Stars
- 2.8k
- Forks
- 1.1k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 1
Description
Opening this issue to separate the side-discussion in https://github.com/ARMmbed/DAPLink/issues/479.
When a micro:bit with DAPLink with WebUSB is plugged for the first time, chrome will list the name of the WebUSB device as `LPC1768 `:

And once it's paired it will be listed in Chrome as a USB device without a name:

To replicate follow the steps below, assuming you are on a Windows 10 computer that has successfully used a WebUSB enabled micro:bit already:
* Disconnect any DAPlink/Mbed device from the computer
* Go to https://makecode.microbit.org/beta?webusb=1#editor
* Revoke access to all previously connected devices to this website
- At the left of the URL click on "secure"
- Click on the cross for each entry on the list:
* Plug in a micro:bit
* Go to the Device Manager and remove all DAPLink drivers
- On the `Ports (COM & LPT)` list find the `USB Serial Device (COMXX)` entry, right click and `Uninstall device`
- On the `Universial Serial Bus Controllers`, find the `USB Mass Storage Device` entry with VID 0x0d28 and PID 0x0204, right click and `Uninstall device`
- On the `Universial Serial Bus Controllers`, find the `USB Composite Device` entry with VID 0x0d28 and PID 0x0204, right click and `Uninstall device`
* Unplug the micro:bit
* Close and reopen chrome to go again to https://makecode.microbit.org/beta?webusb=1#editor
* In MakeCode, click on the cog at the top right corned and Pair device:
* You should see the connection window with the wrong name:

After you've paired once, the next time the right device name appears:

But the next time you pair, the list of USB devices increases by adding another USB device instead replacing the previous entry:

Contributor guide
Assessment
This issue has not been assessed yet.