cpu/msp430/periph_uart: Fix uart_write() for USCI peripheral #20572
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.
Contribution description
In TX-only mode the UART was previously release before all bits of the last byte were shifted out. This adds a busy loop waiting while the peripheral is still busy, fixing the issue.
Testing procedure
make BOARD=olimex-msp430-h2618 flash term -C tests/sys/busy_wait
now gives:With
master
, there is no output shown because pyterm is waiting for the\n
to complete the line. But since\n
is incidentally the last char in all strings send (and, therefore, corrupted), it will never show any output.Issues/PRs references
Regression introduced by #20357