Added partial synchronous bit-bang support for FT4232H ports C and D #55
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First of all: do not merge this!
This PR relates to issue #54
I've made a partial implementation of the bit-bang support required to make use of ports C and D of a FT4232H device, as those ports do not have a MPSSE unit. (Only on Ports A and B have it.)
The idea was to add a specialized class (FtHalSbb) that operates in synchronous bit-bang mode, so all ports on this device can be used (C and D with reduced functionality: gpio-only) in an embedded-hal context.
What is missing is support for anything other than the ftdi-rs driver. The closed-source driver does not work on my system.
At any rate, this PR is mainly here in case this (partial) implementation is use to someone. It has been tested only a little thus far, and definitely needs more confrontations with reality. And the code definitely needs an expert's eye and touch.