You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The API does not prevent an attempt to initialize multiple UART stdio driver instances. I can't find any documentation saying this isn't allowed. It would also be possible to implement. For example:
The expectation here might be that the greeting is output to both UARTs.
This could be fixed by changing the documentation and maybe adding a runtime assertion or by actually making it work.
If it's going to work, issue #811 is impacted because the signature of stdio_uart_deinit_full() should change to identify which UART driver instance is uninitialized:
May I suggest to use the more standard handles, stdout and stderr, stdin.
And in startup code application can initialize which uart(or usb) is what pipe
May I suggest to use the more standard handles, stdout and stderr, stdin. And in startup code application can initialize which uart(or usb) is what pipe
I think @alastairpatrick 's point was that the uartn_ handles could be used in addition to stdout etc. for finer grained control
The API does not prevent an attempt to initialize multiple UART stdio driver instances. I can't find any documentation saying this isn't allowed. It would also be possible to implement. For example:
The expectation here might be that the greeting is output to both UARTs.
This could be fixed by changing the documentation and maybe adding a runtime assertion or by actually making it work.
If it's going to work, issue #811 is impacted because the signature of stdio_uart_deinit_full() should change to identify which UART driver instance is uninitialized:
Somewhat more involved, it would be useful if something like this worked:
The text was updated successfully, but these errors were encountered: