Release candidate for mbed-os-5.15.0-rc2 #12082
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
If the fault handler was hit before the stdio console was used and initialised, the initialisation code caused a "mutex in ISR" trap, stopping the register dump from happening. Temporarily set the `error_in_progress` flag at the top of the fault handler, and restore it before calling `mbed_error`. Take the opportunity to suppress fault dumps on recursive crashes, much as is done inside `mbed_error`.
…D to COMPONENT_WHD
At IAR linking, the default method of 'initialize by copy' is 'auto', which will estimate different packing algorithms, including complex 'lz77', for smallest memory footprint. But the algorithm itself can consume some SRAM and cause OOM at linking time for NANO130, which just has 16KiB SRAM. To avoid this error, always choose 'none' packing algorithm.
This adjustment is to pass compile on IAR on which heap configuration is hard-coded and cannot be adjusted according to staic SRAM usage.
Related PR: #10924 The above PR adds functions to disable/enable serial input/output. If both serial input and serial output are disabled, the peripheral is freed. If either serial input or serial output is re-enabled, the peripheral is reinitialized. I missed this change while working on the static pinmap and unfortunately it has an impact on it. The reinitialization is a problem for static pinmap. Now the HAL init()/init_direct() function is called not only in the constructor (but also when re-enabling the peripheral). In the current version, even if static pinmap constructor was used to create an object (and init_direct() HAL API), when reinitialization is done it uses init() HAL API. This must be split. If static pinmap constructor is used, then the peripheral must be always initialized using HAL init_direct() function. If regular the constructor is used, then the peripheral must be initialized using HAL init() function. The same split also must be done while setting flow control during reinitialization.
This is done in order to enable static pin-map for Mbed Cloud Client Example. This should give extra ROM savings, ~1KB.
Currently any misconfiguration of, for example, bootloader feature will cause the build system to just silently drop it and continue building which can lead to completed builds of something the user didn't want to build in worst case and failing builds after compilation (=wasted time) in the best.
We removed catching and passing, we want to know for any misconfiguration if bootloader is supported. Regions should check if bootloader is supported. In case not, just return. Otherwise we catch any error. This should help us to uncover missing regions or other config error (in case bootloader is enabled via bootloader_supported set to true).
The config failes with an exception that was previously ignored.
Until the error is fixed:
"start not found in targets.json.".format(active_memory)
device_name is missing
An error to be fixed: tools.config.ConfigException: Missing a memory that is read, write in CMSIS Pack data
device_name is missing
device_name missing
device_name is missing
device_name is missing
device_name is missing
device_name is missing
This should be reverted once bootloader is supported.
|
ci started |
This reverts commit eedfd64. The only changes in this commit are white space changes which are actually wrong and breaking the astyle checks.
|
CI restarted |
0xc0170
approved these changes
Dec 11, 2019
|
Also triggered branch job for release-candidate |
Test run: SUCCESSSummary: 12 of 12 test jobs passed |
|
restarted branch test, looks like there was a possible license error |
Test run: SUCCESSSummary: 12 of 12 test jobs passed |
|
release_candidate branch job upgraded to use ARMC 6.13 so hopefully that will fix the issues. Branch job restarted |
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.