-
Notifications
You must be signed in to change notification settings - Fork 3k
Release candidate 3 for Mbed OS 5.14 #11524
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
Conversation
Random initialization sequence is causing start up issues in multiple platform when done at construction phase. The right thing is to delay the random initialization to later stage when the message id is actually required. This provides system to do all necessary allocation upfront without causing any random race condition at startup phase.
Remove checking that vectors were copied to RAM as not all targets have NVIC_RAM_VECTOR_ADDRESS defined as public. Instead always call NVIC_SetVector unconditionally as old implementation does.
1. All TZ targets should have name pattern: PLATFORM_[PSA_/NPSA_]S/NS, where: (1) 'PLATFORM' for test spec platform name (2) 'PSA/NPSA' for PSA/non-PSA targets. Defaults to PSA target on absent. (3) 'S'/'NS' for secure/non-secure targets 2. Secure target may participate in Greentea, so its name is also truncated here.
This is unnecessary because all TZ targets must follow the naming rule: PLATFORM_[NPSA_]S/NS
This will add back immediately after target renaming is done.
1. Create a private target name NU_PFM_M2351_CM which stands for the NuMaker-PFM-M2351 board and is to be extended. 2. NU_PFM_M2351_NPSA_S/NS target names for non-PSA secure/non-secure targets respectively. 3. The original target name NUMAKER_PFM_M2351 is recycled and cannot be used. Use NU_PFM_M2351_S/NS for non-PSA secure/non-secure targets instead. NOTE: Target name doesn't follow the rule below because online database has limit of max 20 chars: NUMAKER_PFM_M2351_PSA/NOPSA_S/NS Instead, it has the rule: NU_PFM_M2351_[NPSA_]S/NS NU_PFM_M2351_S/NS for PSA targets. This is to be consistent with current PSA target naming. So the resolved target names are: NU_PFM_M2351_S : PSA secure target NU_PFM_M2351_NS : PSA non-secure target NU_PFM_M2351_NPSA_S : Non-PSA secure target NU_PFM_M2351_NPSA_NS : Non-PSA non-secure target
Support secure/non-secure combined build for non-PSA target: 1. In secure post-build, deliver built secure image to TARGET_NU_PREBUILD_SECURE directory which is to combine later. 2. In non-secure post-build, merge non-secure image with secure image saved in TARGET_NU_PREBUILD_SECURE directory. 3. In non-secure post-build, user can also drop pre-built secure image saved in TARGET_NU_PREBUILD_SECURE directory and provide its own by adding the line below in mbed_app.json: "target.extra_labels_remove": ["NU_PREBUILD_SECURE"]
NOTE1: USB UART is partitioned for non-secure world. Secure world still can share it with limit that its interrupt cannot use in secure world. NOTE2: In secure world, USB UART is only for Greentea and STDIO. Developers shouldn't use it for other purposes.
This is necessary for exporting M2351 uvision project.
…..c473148 c473148 Merge branch 'release_internal' into release_external d7ad405 Merge pull request #2179 from ARMmbed/release_internal_merge 668fc82 Merge branch 'master' into release_internal 9458a30 Added crypto library to unit test makefile ff83e4b Added crypto library include path 4292326 Updated eapol TLS library to use extended version of export keys callback f8f0762 Corrected authenticator EAP-TLS start retries 00fdf8d Added sending of initial EAPOL-key to original target during bootstrap 313794c Wi-sun neighbor temporary neigh update 05fa359 added support for EAPOL timing adjustment cfc3223 RPL parent confirmation process update c3a2c5c Added limit to BR supplicant entries 21de90d RPL dio handler update 425a04a Fix Slaac Handler for not native IPv6 stack. 5722a4a Wi-sun multicast neighbour and RPL update git-subtree-dir: features/nanostack/sal-stack-nanostack git-subtree-split: c473148
Mbed TLS's export keys callback requires the hello.random (for both server and client) to be const. Make the callbacks in Mbed OS that use the key export feature use const to match.
Update Mbed TLS to Mbed TLS 2.19.1.
CI started |
@adbridge @MarceloSalazar @AriParkkila @RobMeades |
Test run: FAILEDSummary: 1 of 11 test jobs failed Failed test jobs:
|
This is a manual commit to bring the contents of PR11526 across. The original commit could not be cherry-picked or patched!
When next SysTimer wake-up is scheduler far enough, always consider that deep sleep may be entered and program an early wake-up. So that even if deep sleep is only allowed some time later, it can be entered. If not doing this, then the deep sleep would be prevented by SysTimer itself and may not be entered at all. This has been proved to happen in a simple blinly example.
Suggested-by: @kjbracey-arm Replace the sleep_manager_can_deep_sleep() with !_deep_sleep_locked. Indeed, if we know we've taken the lock because we're using us_ticker, no need to do the early wake. Updated comments accordingly.
CI restarted, |
Test run: SUCCESSSummary: 11 of 11 test jobs passed |
Description
Release candidate number 3
Pull request type
Reviewers
Release Notes