Release candidate #8637
Closed
Release candidate #8637
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
While investigating the RX issue on NRF52_DK after SDK 14 updates, it is observed that the RX FIFO doesn't get filled up, when the flow control is disabled. Hence the readable never returns true. If using Serial interface, the stdio file handles (0, 1, 2) get opened. This results in configuring the flow control for STDIO, and it is observed that the RX FIFO gets filled. However, if RawSerial is used, the STDIO file handles don't get opened. During the debug process it was observed that if the flow control is configured once and then set to disabled, RX worked as expected. Alternative to this approach is that user application specifically enables flow control as done in mbed's Greentea test suite. See https://goo.gl/r8nBYH See https://goo.gl/8VB2qg step 14 for _initio's description. See test code to reproduce the issue and test fix here: https://goo.gl/AQU1xG Description The change in behavior with NRF52's UART RX is documented here. #6891 This change is a fix for the above issue.
While investigating the RX issue on NRF52_DK after SDK 14 updates, it is observed that the RX FIFO doesn't get filled up, when the flow control is disabled. Hence the readable never returns true. If using Serial interface, the stdio file handles (0, 1, 2) get opened. This results in configuring the flow control for STDIO, and it is observed that the RX FIFO gets filled. However, if RawSerial is used, the STDIO file handles don't get opened. During the debug process it was observed that if the flow control is configured once and then set to disabled, RX worked as expected. Alternative to this approach is that user application specifically enables flow control as done in mbed's Greentea test suite. See https://goo.gl/r8nBYH See https://goo.gl/8VB2qg step 14 for _initio's description. See test code to reproduce the issue and test fix here: https://goo.gl/AQU1xG Description The change in behavior with NRF52's UART RX is documented here. #6891 This change is a fix for the above issue.
…ppearing on docs site. - Standardize units of time (microsecond, millisecond). - Improve example description.
This reverts commit 5ee5b07.
Add "s" for agreement.
Edit for active voice.
### Description
Exporting to GNU ARM Eclipse, E2 Studio, and other exclude-based IDEs
currently generats unusable project files online. This is because the
list of directories ignored in the scan is inconsistant about what sort
of paths are used: logical paths, or phisical paths. This patch makes
all paths in ignored_dirs logical. This should fix the excluding tags
in these project files.
### Pull request type
[x] Fix
[ ] Refactor
[ ] Target update
[ ] Functionality change
[ ] Breaking change
### Description
The `mbed compile -S` command is suposed to indicate what targets
support what toolchains. The command was printing out things that
don't make sense, like `GCC_CR` and things that make sense, but are
not offiially supported yet, like `ARMC6`. This PR fixes all of that.
### Pull request type
[x] Fix
[ ] Refactor
[ ] Target update
[ ] Functionality change
[ ] Breaking change
### Description The `mbed compile` would traceback when no linker script is found. This PR changes that behavior to make that into a NotSupportedException, which has decent user behavior. Fixes #7723 ### Pull request type [x] Fix [ ] Refactor [ ] Target update [ ] Functionality change [ ] Breaking change
This is fix for issue 8368. Test is causing some problems on `REALTEK_RTL8195AM` and `ARM` compiler. There is some kind of memory issue. Probably there is not enough memory space for global data provided by the test. Data definitions have been moved into test function body so, they will land on stack. With this fix the test works on `REALTEK_RTL8195AM/ARM`.
as per @kjbracey-arm review
…itally reverts docs PR 8511
cmonr
force-pushed
the
release-candidate
branch
2 times, most recently
from
351121b to
4a14db5
Compare
…Return a bool value on wether parsing of the IPv4 address string was successful
|
The error comes from One more, I could not locate update mbed_version.h file? |
|
I'll close, we will reopen with an update or new PR |
Huh. Thought I ended up applying that last patch. Oh well. |
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.
No description provided.