1
Discussion - Hardware / Re: FT4232H using MPSSE for I2C on channel B
« on: January 25, 2019, 11:21:21 pm »Hi,
Could you send your code in as a zip file (re-named to .zi_ ) to us at our support address support1@ftdichip.com. We got port B working on a copy here and so can check your code.
It is also worth checking that you only have one FTDI chip connected as the index values are across all FTDI chips connected. You could try opening by description and appending a B (replace FT4232H Module with your own modules description which can be checked with USBview or FT_Prog).
ftStatus = myFtdiDeviceB.OpenByDescription("FT4232H Module B");
//ftStatus = myFtdiDeviceB.OpenByIndex(1);
Best Regards,
FTDI Community
Thanks! Even though this is the only FTDI device plugged in, and the FT2322H didn't have the issue, I was not successful in opening by Index or Description, but I did have success using SerialNumber.
Code: [Select]
ftStatus = myFtdiDeviceCHB.OpenBySerialNumber("FT3Q5SRXB");
But I figured I was missing something. So I took the description from FT_PROG, ie, "Acme Serial Debug", and then used:
Code: [Select]
ftStatus = myFtdiDeviceCHB.OpenByDescription("Acme Serial Debug B");
I think finding by index would have been better so we didn't rely on EEPROM. I bought two of the same breakout boards bought from Digikey. One came with an EEPROM programmed and one didn't. So they had different descriptions. But for our actual debug board, they should all be the same, either default blank or programmed to our chosen description. So I won't worry about it and will go by name. Though it would be good to be able to check a couple of descriptions without needing a recompile.
p.s. for anyone else, in the snippet above, it would be myFtdiDeviceCHB.OpenByDescription. I got compile errors on just myFtdiDeviceB.
Thanks again!