Increase baud rate to 115200 #65
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@ARMmbed/mbed-os-core Please see the PR description. Increasing the baud rate stabilises this example in CI, but there's no issue on a local board to begin with. Could someone with serial/UART expertise please suggest why it happens? Or whether/why/when some output can be lost at a low baud rate? Every |
|
(Fix for CMake & Travis to come as another PR) |
LDong-Arm
added a commit
to LDong-Arm/mbed-os
that referenced
this pull request
Apr 13, 2021
At 9600 baud, a large part of the serial output of the crash reporting example is missing on CI boards, causing the example test to fail. At a higher serial speed (115200 baud), the entire output is intact. This is in alignment with ARMmbed/mbed-os-example-crash-reporting#65. Fixes ARMmbed#14535
Patater
approved these changes
Apr 14, 2021
|
Change looks fine. Needs Travis CI updates to pass Travis before merge. |
Travis fixed in #67, I'll rebase after that gets merged. |
|
Travis passed, this can be merged |
Patater
approved these changes
Apr 14, 2021
pennam
pushed a commit
to pennam/mbed-os
that referenced
this pull request
Apr 23, 2021
At 9600 baud, a large part of the serial output of the crash reporting example is missing on CI boards, causing the example test to fail. At a higher serial speed (115200 baud), the entire output is intact. This is in alignment with ARMmbed/mbed-os-example-crash-reporting#65. Fixes ARMmbed#14535
JeanMarcR
pushed a commit
to JeanMarcR/mbed-os
that referenced
this pull request
Apr 26, 2021
At 9600 baud, a large part of the serial output of the crash reporting example is missing on CI boards, causing the example test to fail. At a higher serial speed (115200 baud), the entire output is intact. This is in alignment with ARMmbed/mbed-os-example-crash-reporting#65. Fixes ARMmbed#14535
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes ARMmbed/mbed-os#14535
The full log of this example looks like (note
1st runand2nd run):Code
When running the example at 9600 baud in CI, a huge part of the serial output is lost, and we're left with:
Code
This issue only happens in CI, and the "cut-off" position is random. This causes the example to fail randomly in CI, depending on whether
= System will be rebooted due to a fatal error =expected by crash-reporting.log happens to be lost or not.This problem doesn't happen on a local board when using
mbedgtto run the example & compare the log.Increasing the serial baud rate resolves the issue in CI.