Update secure binaries with platform init fix for ARM_MUSCA_S1

[LDong-Arm]

Summary of changes

Due to a bug in TF-M v1.2, Musca S1 is not fully initialised by the secure binary. This leads to malfunctioning and performance issues around timer, IRQ, sleep, etc. Thanks to our Greentea test suites, we've caught this in our nightly CI - the failing suites are:

• hal-tests-tests-mbed_hal-common_tickers
• hal-tests-tests-mbed_hal-sleep
• hal-tests-tests-mbed_hal-sleep_manager
• platform-tests-tests-mbed_platform-wait_ns
• rtos-tests-tests-mbed_rtos-event_flags

The fix is ARMmbed/trusted-firmware-m#15 which will also be upstreamed to the trusted-firmware-m project. This PR brings in the secure binaries containing the fix.

Impact of changes

Timings, IRQ and sleep related issues on Musca S1 are now fixed. All Greentea tests pass.

Migration actions required

None.

Documentation

None.

---

Pull request type

[x] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[] Feature update (New feature / Functionality change / New API)
[] Major update (Breaking change E.g. Return code change / API behaviour change)

---

Test results

[] No Tests required for this change (E.g docs only update)
[x] Covered by existing mbed-os tests (Greentea or Unittest)
[] Tests / results supplied as part of this PR

---

Reviewers

@evedon

---

[ciarmcom]

@LDong-Arm, thank you for your changes.
@evedon @ARMmbed/mbed-os-maintainers please review.

[0xc0170]

cI started

[mbed-ci]

Jenkins CI Test : ❌ FAILED

Build Number: 1 | 🔒 Jenkins CI Job | 🌐 Logs & Artifacts

CLICK for Detailed Summary

jobs	Status
jenkins-ci/mbed-os-ci_unittests	✔️
jenkins-ci/mbed-os-ci_cmake-example-ARM	✔️
jenkins-ci/mbed-os-ci_cmake-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_build-greentea-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_build-greentea-ARM	✔️
jenkins-ci/mbed-os-ci_build-example-ARM	❌
jenkins-ci/mbed-os-ci_build-example-GCC_ARM	❌
jenkins-ci/mbed-os-ci_build-cloud-example-ARM	✔️
jenkins-ci/mbed-os-ci_build-cloud-example-GCC_ARM	✔️

[LDong-Arm]

We have a CI issue today. We can wait for ARMmbed/trusted-firmware-m#15 to get in first, after which I'll need to update VERSION.txt in this PR anyway.

Pull request has been modified.

[LDong-Arm]

Rebased and added VERSION.txt

[mbed-ci]

Jenkins CI Test : ✔️ SUCCESS

Build Number: 2 | 🔒 Jenkins CI Job | 🌐 Logs & Artifacts

CLICK for Detailed Summary

jobs	Status
jenkins-ci/mbed-os-ci_unittests	✔️
jenkins-ci/mbed-os-ci_cmake-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_cmake-example-ARM	✔️
jenkins-ci/mbed-os-ci_build-greentea-ARM	✔️
jenkins-ci/mbed-os-ci_build-greentea-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_build-cloud-example-ARM	✔️
jenkins-ci/mbed-os-ci_build-example-ARM	✔️
jenkins-ci/mbed-os-ci_build-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_build-cloud-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_cmake-example-test	✔️
jenkins-ci/mbed-os-ci_greentea-test	✔️
jenkins-ci/mbed-os-ci_tfm-integration	✔️