Update Cypress WifiHostDriver to version 1.50

[morser499]

Description (required)

Update the Cypress Wifi Host Driver (WHD) to version 1.50.

Summary of change (What the change is for and why)

Add support for Manufacturing Test
Update 43012 firmware images
Move WHD from being identified as a Target to being a Component

Documentation (Details of any document updates required)

---

Pull request type (required)

[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 (required)

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

CYW9P62S1_43012EVB_01-GCC_ARM.txt
CYW943012P6EVB_01-GCC_ARM.txt
CY8CKIT_062S2_43012-GCC_ARM.txt
CY8CPROTO_062_4343W-GCC_ARM.txt

---

Reviewers (optional)

---

Release Notes (required for feature/major PRs)

Summary of changes

Impact of changes

Migration actions required

[ciarmcom]

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

[0xc0170]

Move WHD from being identified as a Target to being a Component

Please send this separately, it's hard to review when you move and change files within one PR. Can this PR be just about updating the driver?

[morser499]

Move WHD from being identified as a Target to being a Component

Please send this separately, it's hard to review when you move and change files within one PR. Can this PR be just about updating the driver?

I don't understand what splitting it up would achieve. Can you clarify? The changes are already split up into separate commits and can be viewed individually:
6c1c1cc

eab475f

[adbridge]

AFAICT the majority of the PR is only changing target code which we do not really review. Someone in the WiFi team may just wish to check the general principle of moving from target to component and the impact on the targets.json file however...

[SeppoTakalo]

I think it is OK to move the code to COMPONENTS, if they wish.

I don't see the point of splitting this PR, I would accept this as it is. Looks fine.

[0xc0170]

CI started

[mbed-ci]

Test run: FAILED

Summary: 3 of 4 test jobs failed
Build number : 1
Build artifacts

Failed test jobs:

• jenkins-ci/mbed-os-ci_build-IAR
• jenkins-ci/mbed-os-ci_build-GCC_ARM
• jenkins-ci/mbed-os-ci_build-ARM

[0xc0170]

@morser499 Please review build failures

[morser499]

@morser499 Please review build failures

Updated BLE feature to use component instead of target as well. The remaining failures appear to be because the MBED_CONF_APP_WIFI_SSID and MBED_CONF_APP_WIFI_PASSWORD are not defined. Did something change in the application related to these values?

[ifyall]

@0xc0170, There is a change in dfa9692 that impacted both MBED_CONF_APP_WIFI_SSID and MBED_CONF_APP_WIFI_PASSWORD. Can that be causing the issue?

Ian

[0xc0170]

@0xc0170, There is a change in dfa9692 that impacted both MBED_CONF_APP_WIFI_SSID and MBED_CONF_APP_WIFI_PASSWORD. Can that be causing the issue?

The next restart will show us, but should not be there (as this is not supported error , not real error but sometimes I noticed it in the logs being printed along iwth the real error).

Restarted CI

[mbed-ci]

Test run: SUCCESS

Summary: 11 of 11 test jobs passed
Build number : 2
Build artifacts