Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

[U(S)ART] hardware flow control support#1634

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
fpistm merged 6 commits intostm32duino:mainfromakasona:uart_flow_control_support
Feb 2, 2022

Conversation

@akasona
Copy link
Contributor

Summary

Add hardware flow control configuration APIs for U(S)ART. (list item of#1418)

voidsetRts(_rts);voidsetCts(_cts);voidsetRtsCts(_rts, _cts);

You can enable flow control on RTS/CTS separately, or enable both.
These APIs accept either uint32_t pin number or PinName.

Validation

  • All CI checks are passed.
  • I tested RTS/CTS controls with logic analyzer.
  • Tested on STM32L476RG. (Our product development board)

void setRts(_rts);void setCts(_cts);void setRtsCts(_rts, _cts);These APIs accept either uint32_t pin number or PinName.
@akasona
Copy link
ContributorAuthor

akasona commentedJan 26, 2022•
edited
Loading

Screenshots

CTS control

The external devices's RTS signal (STM32's CTS input) rises every 4 characters, and the STM32 stops transmitting. (460800bps)

test_serial_data_integrity_with_flow_control_CTS1

RTS control

Disable the STM32's RX interrupt every 10 character reception, and the RTS signal keeps HIGH while stopping receiving. (460800bps)
Every 1 character reception causes RTS edge (I think it's because the UART has only 8bits hardware buffer).

test_serial_data_integrity_slowly_RTS

@akasonaakasona mentioned this pull requestJan 26, 2022
4 tasks
@fpistmfpistm requested a review fromABOSTMJanuary 26, 2022 12:59
@fpistmfpistm added this to the2.3.0 milestoneJan 26, 2022
Copy link
Contributor

@ABOSTMABOSTM left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

@akasona, thanks for this Pull Request.
Few inlines comments, otherwise LGTM

@akasonaakasona requested a review fromABOSTMJanuary 29, 2022 12:28
Copy link
Contributor

@ABOSTMABOSTM left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

LGTM

@fpistmfpistm removed their request for reviewJanuary 31, 2022 13:17
@fpistmfpistm merged commit497ea5a intostm32duino:mainFeb 2, 2022
@fpistm
Copy link
Member

Fixes#394

@fpistmfpistm added enhancementNew feature or request and removed New feature labelsJul 16, 2024
@fpistmfpistm linked an issueJan 22, 2025 that may beclosed by this pull request
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@fpistmfpistmfpistm left review comments

@ABOSTMABOSTMAwaiting requested review from ABOSTM

Assignees

No one assigned

Labels

enhancementNew feature or request

Projects

None yet

Milestone

2.3.0

Development

Successfully merging this pull request may close these issues.

Hardware Flow control for serial communication

3 participants

@akasona@fpistm@ABOSTM
[8]ページ先頭
©2009-2025 Movatter.jp