-
Notifications
You must be signed in to change notification settings - Fork 157
Please update mbed-os to have stdio baud rate configurable #23
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
Comments
Could you please help to explain how to override the default baud rate for serial port & stdio? Thanks |
I'm not sure I understand this. Currently, blinky doesn't use the serial port, so why do we need to configure the stdio baud rate for blinky? |
True, that it doesn't user serial. But I took it as a starting point for an STM32F4 device. Possibly I should have filed this issue against mbed-os. So, at the moment there are still hard-coded 9600 in the targets, which then make printf() (not pc.printf() ) not work as expected. |
ARM Internal Ref: IOTMORF-332 |
What is expected? 9600 is the default baudrate |
If I modify the config.json of this example with core.stdio-serial-baudrate, I would expect it to use that value for pc.printf(), printf() and in other repos ns_trace() right from the beginning. What I have seen is that parts of the output are with 9600 and other parts with the configured value. |
Thanks for the clarification. @geky |
I think it is mostly this issue: ARMmbed/mbed-os#1969 and the related 9600 occurences: https://github.com/ARMmbed/mbed-os/search?utf8=%E2%9C%93&q=serial_baud%28obj%2C+9600&type=Code |
@markus-becker-tridonic-com the best would be to move this to mbed-os repo. What's your target device? |
NUCLEO_F401RE, NUCLEO_F091RC and K64F. Are you able to transfer this issue. Or shall I re-create? |
Please recreate, provide a simple code snippet to reproduce. Thanks |
Moved to ARMmbed/mbed-os#2396 |
No description provided.
The text was updated successfully, but these errors were encountered: