Well, as far as I can tell, it's because Espruino enumerates as 2 USB devices - the virtual COM port (so you can talk to it) and the HID device.
I think Windows just looks at the USB ID and loads ST's driver for it, even though the board itself is saying it also supports HID.
Possibly someone could write in 'inf' file for it which would fix it - that'd be awesome but I don't know enough about Windows driver development for it.
The actual fix I was going to do in firmware was to just allow you to put it into a 'HID-only' mode (no com port) which I'm sure would work fine on everything. It's just a bit sad as once you do that you can then only debug Espruino by wiring up a USB-Serial converter to it!
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Well, as far as I can tell, it's because Espruino enumerates as 2 USB devices - the virtual COM port (so you can talk to it) and the HID device.
I think Windows just looks at the USB ID and loads ST's driver for it, even though the board itself is saying it also supports HID.
Possibly someone could write in 'inf' file for it which would fix it - that'd be awesome but I don't know enough about Windows driver development for it.
The actual fix I was going to do in firmware was to just allow you to put it into a 'HID-only' mode (no com port) which I'm sure would work fine on everything. It's just a bit sad as once you do that you can then only debug Espruino by wiring up a USB-Serial converter to it!