--- Quote Start ---
I was installing a FTDI interfaced USB relay board yesterday, for high-pressure gas flow control, and noticed that having installed as com8:, when I moved it to other usb ports it remained as com8: - a considerable improvement over what used to happen with usb com ports on a PC.
--- Quote End ---
This occurs if the USB device has a unique serial number. I use the FTDI tool FT_PROG to re-write the serial numbers on most devices. Eg., the USB-Blasters on my two Stratix IV GX development kits were the same, so I reprogrammed them with serial numbers S4GXDK00 and S4GXDK01. You can do the same with your FTDI cables.
--- Quote Start ---
I have been thinking in the meanwhile - you have really helped me with these discussions - now I have invested some months of work and also serious money in hiring a vhdl engineer to work on the state machine for this code, so I can not make this a habit, but would you like a (personal) copy of my interface firmware for the MorphicII or the FT2232H mini modules ? I will have to do some documentation.
--- Quote End ---
Sure, if you don't mind me critiquing the code :)
I don't have the Morph-IC-II, so don't really care about the top-level code. But I'd be interested in your FTDI interface code.
Here's how I coded an FTDI asynchronous interface;
1) Created a bus functional model of the FTDI interface
2) Created an Avalon-ST interface to the FTDI device, i.e., an FTDI-to-Avalon-ST bridge.
3) Created an Avalon-ST to Avalon-MM master component
4) Wired them together as an FTDI-to-Avalon-MM master.
Using that interface, I can open a com port and write to an address via
w 0 12345678
or read and receive a response
r 0
12345678
I need to document that code too :)
I've also implemented a UART-to-Avalon-ST bridge, which can then be connected to the Avalon-ST to Avalon-MM master, to enable RS232 command access. Again, its in need of documentation :)
Cheers,
Dave
Honored Contributor
