Skip to content

Moved Cypress TriggerMux initialization out of the HAL and into the BSP #11590

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

Merged
merged 1 commit into from
Sep 30, 2019

Conversation

morser499
Copy link

Description

Update Cypress targets using UDB SDIO to have the target board perform the TriggerMux initialization rather than the lower level driver. This is important as the board is what knows which trigger muxes are actually used. Upcoming boards will need to use a different set of TriggerMuxes that what the first two boards use.

Pull request type

[x] Fix
[ ] Refactor
[x] Target update
[ ] Functionality change
[ ] Docs update
[ ] Test update
[ ] Breaking change

… that is what dictates what trigger muxes actually need to be used
@ciarmcom ciarmcom requested review from maclobdell and a team September 27, 2019 21:00
@ciarmcom
Copy link
Member

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

@morser499 morser499 changed the title Moved TriggerMux initialization out of the HAL and into the BSP since… Moved Cypress TriggerMux initialization out of the HAL and into the BSP Sep 27, 2019
@morser499
Copy link
Author

morser499 commented Sep 27, 2019

Test results were generated with changed build on #11542

CYW943012P6EVB_01-GCC_ARM.txt
CY8CKIT_062S2_43012-GCC_ARM.txt

@0xc0170
Copy link
Contributor

0xc0170 commented Sep 30, 2019

CI started

@mbed-ci
Copy link

mbed-ci commented Sep 30, 2019

Test run: FAILED

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

Failed test jobs:

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

@mbed-ci
Copy link

mbed-ci commented Sep 30, 2019

Test run: FAILED

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

Failed test jobs:

  • 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_build-IAR

@mbed-ci
Copy link

mbed-ci commented Sep 30, 2019

Test run: SUCCESS

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants