Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
iceprog does not find iCEstick on Windows
See original GitHub issueHello, I got a new iCEstick today, trying to use it with the icestorm toolchain on Windows. I can get a bitstream generated fine, but when I do iceprog my_bitstream.bin I just get this:
Can't find iCE FTDI USB device (vendor_id 0x0403, device_id 0x6010).
ABORT.
I’m thinking this is a bug in icestorm/iceprog itself, since Diamond Programmer off the Lattice site can program the iCEstick with no problem. I also double checked what device/vendor IDs it’s showing up as, and they matched 0x0403/0x6010, as shown in this screenshot.
How would I fix this? I even tried with -d i:0x0403:0x6010, although that didn’t fix it at all.
Issue Analytics
- State:
- Created 5 years ago
- Comments:24 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
For custom boards such as the icebreaker (cc @esden), I wonder if this could be fixed by disabling VCP in the EEPROM for the first port? Or does Windows need to be explicitly told to use libusb, as opposed to just not autobinding the serial port?
LibFTDIdoesn’t really play nice w/ Windows by default. Unlike Linux, it’s not possible forlibusb/libFTDIto switch between a serial port USB device and FTDI functionality at will; you need a special driver for this.… and @daveshah1 beat me to it 😃.