M2354: Fix TF-M 1.4

[ccli8]

Summary of changes

This PR, following #15050, tries to fix NSC call broken on M2354 with TF-M 1.4 upgrade. It has the following modifications:

1. In TF-M, fix NSPE interrupt-disabled NSC call broken. Check https://developer.trustedfirmware.org/T966.
2. In TF-M, enable mcuboot log forcibly. This is to help check firmware update process.
3. Update readme and script

---

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

---

[ciarmcom]

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

[ccli8]

@LDong-Arm Same as #14441, this PR changes frozen tools/targets to update post-build script for M2354 for Mbed CLI 1.

Then this PR can land in 6.15? Otherwise, M2354 will break.

[LDong-Arm]

@ccli8 Thanks for the PR. How is "NSPE interrupt-disabled NSC call broken" reproduced?

Anyway, given that the TF-M code in https://github.com/OpenNuvoton/trusted-firmware-m/tree/nuvoton_mbed_m2354_tfm-1.4 has new commits added, updating binaries in mbed-os is fine.

[LDong-Arm]

@ccli8 (As a follow-up) If a more verbose boot log is helpful with firmware update, could you please raise a PR to mbed-os-tf-m-regression-tests to pass additional cmake options during TF-M build, at least when the target is NU_M2354?

[Patater]

CI started

[ccli8]

How is "NSPE interrupt-disabled NSC call broken" reproduced?

On Mbed, call __disable_irq() first and then call any PSA API. As I know, Musca boards needn't this path, but M2354 does.

@LDong-Arm

If a more verbose boot log is helpful with firmware update, could you please raise a PR to mbed-os-tf-m-regression-tests to pass additional cmake options during TF-M build, at least when the target is NU_M2354?

nuvoton_mbed_m2354_tfm-1.4 has enabled it
https://github.com/OpenNuvoton/trusted-firmware-m/blob/1b83c833390a784d1612622273953463bf5c555e/platform/ext/target/nuvoton/m2354/config.cmake#L43

[mbed-ci]

Jenkins CI Test : ✔️ SUCCESS

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-cloud-example-ARM	✔️
jenkins-ci/mbed-os-ci_build-cloud-example-ARM	✔️
jenkins-ci/mbed-os-ci_build-cloud-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_cmake-cloud-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_build-greentea-ARM	✔️
jenkins-ci/mbed-os-ci_build-greentea-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_cmake-example-ARM	✔️
jenkins-ci/mbed-os-ci_cmake-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_build-example-ARM	✔️
jenkins-ci/mbed-os-ci_build-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_greentea-test	✔️