Fixing BF4.6 passthrough incompatibility issue #3164
Merged
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.
In the BetaFlight 4.6, several changes caused incompatibility of ELRS RX BF Passthrough flashing.
In the recent BF versions,
#, not#\r\n(newline automatically added fromSerialHelper.write_str()). This PR modifiedwrite_str()to allow writing without newline characters.Example)
0instead ofUART1). ELRS BF Passthrough flashing parses those index numbers, but this breaking change prevented go get into passthrough mode. In this PR, I updated the regex expression to recognize theUART\dstrings patterns.