Closed gurcei closed 1 year ago
Added message to windows autodiscover, which is triggered by libusb_open result code -5:
2022-09-25T08:59:36.322Z NOTE MEGA65 Cross-Development Tool 20220923.10-refact-b9d4282
2022-09-25T08:59:36.322Z INFO using default FPGA ID ffffffff
2022-09-25T08:59:36.835Z INFO detected FTDI serial port COM13 (0403/6010, serial 210292B17EA1B)
2022-09-25T08:59:36.865Z DEBG could not open USB device [0403:6010]: Entity not found (-5)
2022-09-25T08:59:36.865Z NOTE please check USB driver for Serial Converter A / Interface 0: needs to be WinUSB!
2022-09-25T08:59:36.865Z INFO found 0 candidate USB devices.
2022-09-25T08:59:36.865Z INFO requested id ffffffff does not match any usb interface
2022-09-25T08:59:36.865Z CRIT no valid jtag port not found, aborting
or without debug:
2022-09-25T08:59:04.224Z NOTE MEGA65 Cross-Development Tool 20220923.10-refact-b9d4282
2022-09-25T08:59:04.843Z NOTE please check USB driver for Serial Converter A / Interface 0: needs to be WinUSB!
2022-09-25T08:59:04.843Z CRIT no valid jtag port not found, aborting
There's a bit of rigmarole involved for Windows users to get bitstreams uploaded to their devices via the '-b' argument.
So if they attempt to, and it fails, I'd like to point them to a page with information on the preparatory steps, most of which I've outlined here (but perhaps it could have a better home somewhere else too):