Closed gabbla closed 1 year ago
Yes, you are write. This is a limitation and should be addressed. It seems there are few more issues with the FT232H. This should require investigations.
Note FT4222 has been proved to work nicely: https://github.com/dotnet/iot/tree/main/src/devices/Ft4222
So that can be a good solution for you as well.
Thank you for the confirmation. I'll take a look during the holidays to see if I can spot anything strange. Unfortunately I need to stick to the FT232 since my company has stocked several units. Thanks for the suggestion tho!
Gab
Closing this one as seems to be fixed by the last PR!
I am writing a program to control a test bench which is equipped with several IO expanders (PCA9554), a temperature sensor SHT31 and and ADC (ADS7828). The bench is connected to the PC via a FT232H based cable. I am able to interact with the IOEXPs just fine, but when I need to read a temperature or an ADC channel the bus stalls. I investigated further on the ADC side and found that reading more than 1 byte results in a unusable bus.
The reading process is simple: write the channel you want to read, then read 2 bytes.
The hardware has been validated with a nucleo, which works as expected:
Steps to reproduce
Since the ADS7828 is not available in the library, I wrote my driver. I guess you can try to read more than 1 byte from any device and get the same issue.
Expected behavior
It should be possible to read more than 1 byte while using the FT232H binding.
Versions used
System.Device.Gpio
2.3.0-prerelease.22520.10Iot.Device.Bindings
2.3.0-prerelease.22520.10