Release candidate for mbed-os-5.12.3 #10532
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
* Unify PSA generators * Replace scanning for mbed_spm templates with json * Make generate_source_files and parse_manifests common * Make assert_int an internal function * Use parse_manifests in pytests * Update docs
…xibilty in application; to use any of the section (data/bss/heap) without updating linker script in every use case, following decisions are made: 1. Fixed size and small sections moved to SRAM2 (32K) Vectors Crash data Remaining section - RW / ZI 2. Large memory space should be used for variable sections RW/ZI Heap - (Minimum - 0x12000) Stack - At bottom
In rtos-less code, heap is defined by assuming one-region. Through weak-reference to ARM_LIB_HEAP, heap definition is fixed if ARM_LIB_HEAP is defined.
* For ARMC6, core types `Cortex-M4` and `Cortex-M7` did not explicitly add `--fpu=none`, so it defaulted to assuming FPU present. This would cause a compilation error if the target's cmsis.h had `__FPU_PRESENT` defined to 0. * For GCC, `Cortex-M33FE` did not include `+dsp` in the architecture selection. * For ARMC5 and ARMC6, `Cortex-M0+` did not pass `M0plus` to the non-Clang tools.
There was a gap in our pattern - we didn't offer M33 with DSP Extension but no floating-point.
KW24D was set to ARMC5 because the ARMC6 tooling didn't correctly handle Cortex-M4 without floating-point. Now fixed.
… events UBLOX_EVK_ODIN_W2 advertises more events than we expect. 1) When disconnecting first network connectivity is lost and then an actual disconnection event arrives. The first one is unexpected. 2) When reconnecting MESH_BOOTSTRAP_START_FAILED shows up, but the board eventually manages to connect
On NUC472, on wake-up from power-down mode, we may meet hard fault or some other unknown error. Before its cause is found, we enter idle mode instead for a workaround. To simulate power-down mode with idle mode, we also disable us_ticker during power-down period.
With this, single linker file can support different TFM security levels.
Signed-off-by: Mahesh Mahadevan <[email protected]>
Socket ID is usually spitted out by the modem, however there are cases when the modem is actully taken in as an input argument, e.g., in the case of QUECTEL M26 modem. This minor knit clarifies that the CellularSocket::id can be an input argument.
Only release if the current _connect_status is CONNECTING. If the semaphore is released many times for each connect, then the next connect will not wait(), as it will be able to decrement the semaphore imediatelly.
- Link to bug tracking: https://developer.trustedfirmware.org/T239 (cherry picked from commit 5f2e4b3)
- Link to bug tracking: https://developer.trustedfirmware.org/T230 (cherry picked from commit 0c23e86)
- Link to bug tracking: https://developer.trustedfirmware.org/T240 (cherry picked from commit fc78640)
) - Link to bug tracking: https://developer.trustedfirmware.org/T241 (cherry picked from commit da01e34)
#236) - Link to bug tracking: https://developer.trustedfirmware.org/T236 (cherry picked from commit 008bf1b)
The sleep locking/unlocking is taken care of by the layer above (driver).
One gets this compiler warning from nvstore.cpp: ``` Compile [ 48.6%]: nvstore.cpp [Warning] nvstore.cpp@814,9: variable 'os_ret' set but not used [-Wunused-but-set-variable] ``` Turns out it's caused by the fact that the variable is only used with MBED_ASSERTs, which get optimized out or not, depending on your build profile. In reality we do not need a separate variable for that in my opinion though, so we can just use the ret-variable instead and drop the os_ret variable completely and thus avoid this compiler warning.
ATHandler::read_string(...) buffer size param was changed a long time ago to include also NULL. Some calls still gave wrong size after this change.
Signed-off-by: Mahesh Mahadevan <[email protected]>
Unify TF-M and Mbed-SPM code generators: - Unify SPM initialization logic: - All partitions are registered at once - Test partitions are guarded by #ifndef - Introduce single template list - Beatify template files and add "Autogen-do not modify" notice Prepare for integration with mbed-os build system: - Generate all the files in a single place Simplify tools/psa/release.py script
PSA code generation will be called automatically upon mbed invocation. The autogenerated files will be created under <mbed-os-root>/PSA_AUTOGEN directory.
Contributor
Author
|
CI started |
0xc0170
approved these changes
May 3, 2019
Contributor
|
Restarted travis |
Contributor
|
Restarted travis again, should not fail with tools error. |
Contributor
|
@ARMmbed/mbed-os-test Please restart CI |
Test run: FAILEDSummary: 6 of 7 test jobs failed Failed test jobs:
|
Contributor
|
CI restarted |
Contributor
|
I restarted the test job |
Test run: FAILEDSummary: 1 of 11 test jobs failed Failed test jobs:
|
Contributor
|
Fyi, a quick look at the logs show that it seems the NRF52 target is failing to be flashed. |
Contributor
|
we should disable the faulty board and restart tests |
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.