Second example demonstrating input and output asynchronicity #3
Conversation
This file contains hidden or 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
1 participant
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.
Hello,
Even though I had access to several UART implementations for the iCEstick already, including one I had implemented myself, it was indeed yours with your very intuitive naming of ports that helped my in identifying my own logic flaw. So, many thanks for you effort and for bringing it online.
To give something back and help others in a similar situtaion, I am offering an extension of your example. I named it uart_adder and hope that you consider to rename yours to uart_echo. Its grand achievement is to separate the input from the output and have a bit of computation in between - adding two bytes. The communication is not performed with a terminal program, a separate C program is provided.
I took some freedom to add a bit of verbosity to the README.md. This shall help google to find the project (it was only via a post in some forum that I found it) and give folks that stumble across it a bit more of a direction what this is all about.
Best,
Steffen