(OSX) Ecpprog and FTDI USB Serial driver not working together for ECP5 Versa board

[cbrinkerink]

I hope this is the correct place to report the issue, I will gladly follow pointers to the appropriate place if it is not.

I am using MacOS X Mojave, 10.14.6.

The ECP5 Versa board, connected over USB, seems to not be recognised by ecpprog when I make use of the FTDI USB serial drivers instead of the native OSX FTDI driver:

$ ecpprog -S full-correlator.bin
init..
Can't find iCE FTDI USB device (vendor_id 0x0403, device_id 0x6010 or 0x6014).
ABORT.
$ sudo kextunload /System/Library/Extensions/FTDIUSBSerialDriver.kext/
$ sudo kextload -b com.apple.driver.AppleUSBFTDI
$ ecpprog -S full-correlator.bin
init..
IDCODE: 0x02224086 does not match :(
reset..
programming..
Bye.
$

The IDCODE warning message notwithstanding, the bitfile is successfully loaded in the second instance.

While the FTDI USB serial driver is active, the connected board does show up normally in /dev:

crw-rw-rw- 1 root wheel 18, 23 Aug 24 19:30 /dev/cu.usbserial-FT1V75R1A
crw-rw-rw- 1 root wheel 18, 25 Aug 24 19:30 /dev/cu.usbserial-FT1V75R1B

and also appears when I use the lsusb command:

$ lsusb
0403:6010 (bus 20, device 10) path: 1
047d:1020 (bus 20, device 7) path: 2.3
05ac:0221 (bus 20, device 6) path: 2.2
<snip>
$

The top entry in the list above shows the ECP5 Versa board appearing through the expected vendor and product IDs for the FT2232H chip involved (0x0403 and 0x6010). I am therefore not sure why ecpprog does not recognise it.

Happy to provide more information if needed!

[gregdavill]

I'm not familiar enough with OSX's drivers to have any extra insight on this unfortunately.

[motylewski]

under Linux, I need to unload ftdi serial driver
rmmod ftdi_sio
each time after I plug the Lattice LFE5UM-45F-VERSA-EVNG board before using Lattice Programmer (diamond 3.14)

ecpprog -t works with both ftdi_sio.ko driver loaded or not.

Still unloading the driver to get an access to the raw FTDI device is not uncommon.