-
Notifications
You must be signed in to change notification settings - Fork 976
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hardware Flow control for serial communication #394
Comments
HW flow control is not implemented. |
Okay, thanks. |
Hey are you going to implement this feature in future, also please give me some suggestions to implement by myself |
If I well remember it is based on how MBed implement UART. And if I well remember, flow control is also implemented on MBed side. So this could be a good starting point. |
Thanks i will look into it |
@mayurharge |
@fpistm I saw this line in cores/arduino/stm32/uart.c Arduino_Core_STM32/cores/arduino/stm32/uart.c Line 272 in 7b48eff
|
I guess you have also to init the RTS/CTS pin also. |
Just a quick thought if the buffer is full.
You can redefined them by adding a new file (Tab on Arduino IDE) named build_opt.h Increasing only one of both works also but I advise to keep them aligned. |
@fpistm I am already using the BUFFER_SIZE =256.
This was mentioned in the datasheet of SIM800. |
@mayurharge you can of course use the HAL manually for now by calling HAL_GPIO_* and HAL_UART_* functions |
Added to [U(S)ART] request list #1418 |
Done thanks #1634 |
Hello,
I am using the STM32f103c series controller with GSM module. Sometimes Serial buffer of GSM is getting full and the communication is not happening as expected. During my search, I came across Hardware Flow control using RTS/CTS. As stm has dedicated H/W flow control pins [For UART 2 PA0:- CTS2 & PA1:-RTS2] is there any option available in board files to enable hardware flow control?
if yes please let me know how to enable it
if not then it would be really helpful if you can integrate this in next version.
Thanks
The text was updated successfully, but these errors were encountered: