Update CYSBSYSKIT_01

[dustin-crossman]

Summary of changes

Updates COMPONENT_SCL to support WiFi SCAN.
Updates board assets and linker scripts

Impact of changes

Migration actions required

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

08_06_MCUBoot-mbed-os-6.2.0.txt

Test failure explanations:

• Watchdog/reset related failures: These fail due to the custom CM0 application (see Add target CYSBSYSKIT_01 #12603 for background) taking longer than normal to start up, causing an infinite watchdog reset loop. Setting the reset duration to be longer fixes these failures.
• All others: All other failures are related to deep sleep. Currently the CM0 image on this board does not support deep sleep and thus locks deep sleep capability.

---

Reviewers

---

[ciarmcom]

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

[0xc0170]

Please review travis failures, related to the target (missing sectors).

[adbridge]

@dustin-crossman please note, target updates are not features . Unless you are changing an mbed-os api etc then these should be patches. Also considering code freeze is tomorrow, this has landed a little late...One futher point, you cannot assume what the next release version will be as the version is determined by the content which has landed by the time we hit code freeze. Could you please update the PR title accordingly. Thanks.

[dustin-crossman]

@adbridge Good point on the versioning. Title and PR type updated.

[0xc0170]

@dustin-crossman if you can resolve failures in tools today, we can restart CI and get this in for the upcoming release (code freeze today)

[dustin-crossman]

@0xc0170 Sectors info added in! Hopefully that resolves the CI failures.

[0xc0170]

CI started

[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_build-ARM	✔️
jenkins-ci/mbed-os-ci_build-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_dynamic-memory-usage	✔️
jenkins-ci/mbed-os-ci_greentea-test	✔️
jenkins-ci/mbed-os-ci_cloud-client-pytest	✔️

[0xc0170]

@dustin-crossman test passed but travis did not, can you verify?

[0xc0170]

I restarted. sectors are present in target.json, I am not seeing why it would assert now :/

[0xc0170]

@dustin-crossman We would like to code freeze the next release today. Shall we postpone this to the next one?

[0xc0170]

cc @ARMmbed/team-cypress ^^

[dustin-crossman]

I think it wants the sectors to be in the tools/arm_pack_manager/index.json instead of just the targets.json. Yea lets postpone this to the next one.

Pull request has been modified.

[dustin-crossman]

Added sectors info the arm_pack_manager/index.json. Looks like that fixed up the CI issues.

[dustin-crossman]

@0xc0170 Does this look ready to go with the CI issues fixed up?

[0xc0170]

CI started

[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_build-ARM	✔️
jenkins-ci/mbed-os-ci_build-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_dynamic-memory-usage	✔️
jenkins-ci/mbed-os-ci_greentea-test	✔️
jenkins-ci/mbed-os-ci_cloud-client-pytest	✔️