2025-09-12 8:52 AM - last edited on 2025-09-12 10:06 AM by Andrew Neil
Greetings All,
I am using STM32CubeIDE Version 1.18.0, and MxCube Version 6.14.0
I have several configured UARTs with the Yellow Triangle Warning, all of them
start with "Hardware Flow Control (RS232) conflict ......." and each has a unique
conflict.
The UARTs are configured with just the TX and RX pin in Asynchronous mode,
and Hardware Flow Control (RS232) set to Disabled.
Question 1: Are these conflicts something I should be paying attention to, is something
drastically incorrect, and will cause failures?
As I am not using RTS/CTS pins, I cannot have flow control enabled? Correct?
Why the warning?
The UARTs seem to be functional.
Question2: Hovering the mouse over the Yellow Triangle, or any Yellow warning, seems very
inconsistent, sometimes it shows the warning reason, sometimes it doesn't, and you have
to move the mouse around, until it finally shows you the error, is this be design, or just
a problematic user interface? :)
Thanks
Ken
Solved! Go to Solution.
2025-09-12 9:43 AM - edited 2025-09-12 9:44 AM
Yellow triangles are not errors and can be ignored. They are there to let you know that additional functionality cannot be enabled, but they don't indicate errors with the current settings. In this case, it's letting you know that one flow control option is not available.
A2) Never had this problem myself. Sometimes the message displayed is not overly helpful, but having the mouse outside, then bringing it to the highlighted region and leaving it there works. I have seen reports of this not working well on non-Windows platforms.
2025-09-12 9:43 AM - edited 2025-09-12 9:44 AM
Yellow triangles are not errors and can be ignored. They are there to let you know that additional functionality cannot be enabled, but they don't indicate errors with the current settings. In this case, it's letting you know that one flow control option is not available.
A2) Never had this problem myself. Sometimes the message displayed is not overly helpful, but having the mouse outside, then bringing it to the highlighted region and leaving it there works. I have seen reports of this not working well on non-Windows platforms.