Skip to content

Cypress: Add CYESKIT-064B0S2-4343W #12787

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 22 commits into from
Apr 21, 2020

Conversation

kyle-cypress
Copy link

Summary of changes

Add CYESKIT-064B0S2-4343W target

Impact of changes

NA

Migration actions required

NA

Documentation

NA


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)
[] Covered by existing mbed-os tests (Greentea or Unittest)
[x] Tests / results supplied as part of this PR

CYESKIT_064B0S2_4343W.zip
(Zipping test reports together because they are greentea HTML output which github will not allow to be attached as-is)
The sleep test failures are known issues which are not unique to this board. See #12434.


Reviewers

@ARMmbed/team-cypress


dustin-crossman and others added 22 commits April 5, 2020 13:52
@ciarmcom ciarmcom requested review from maclobdell and a team April 10, 2020 01:00
@ciarmcom
Copy link
Member

@kyle-cypress, thank you for your changes.
@maclobdell @ARMmbed/mbed-os-tools @ARMmbed/mbed-os-test @ARMmbed/mbed-os-maintainers @ARMmbed/mbed-os-hal please review.

@0xc0170
Copy link
Contributor

0xc0170 commented Apr 16, 2020

There are errors in BLE, please review

@sreeharshaangara
Copy link

@maclobdell @OPpuolitaival
The CI tests are failing at the cysecuretools sign step. From the logs, it looks like the CI maybe missing a key used to sign the hex file.

The tests pass for other Cypress Secure targets like the CY8CPROTO_064_SB, so can you confirm if there is some CI specific variable which needs to be added to this target to populate a dummy key?

@0xc0170
Copy link
Contributor

0xc0170 commented Apr 16, 2020

cc @ARMmbed/mbed-os-test ^^

@jamesbeyond
Copy link
Contributor

signing key been added @0xc0170

@0xc0170
Copy link
Contributor

0xc0170 commented Apr 17, 2020

CI restarted

@mbed-ci
Copy link

mbed-ci commented Apr 17, 2020

Test run: FAILED

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

Failed test jobs:

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

@jamesbeyond
Copy link
Contributor

Some CI bug, fixed now
CI restarted

@mbed-ci
Copy link

mbed-ci commented Apr 19, 2020

Test run: FAILED

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

Failed test jobs:

  • jenkins-ci/mbed-os-ci_greentea-test

@0xc0170
Copy link
Contributor

0xc0170 commented Apr 20, 2020

@jamesbeyond I restarted test but I've seen the error in tests in another PR, will keep an eye today

@0xc0170
Copy link
Contributor

0xc0170 commented Apr 20, 2020

CI started

@mbed-ci
Copy link

mbed-ci commented Apr 20, 2020

Test run: FAILED

Summary: 1 of 6 test jobs failed
Build number : 5
Build artifacts

Failed test jobs:

  • jenkins-ci/mbed-os-ci_greentea-test

@mbed-ci
Copy link

mbed-ci commented Apr 21, 2020

Test run: SUCCESS

Summary: 6 of 6 test jobs passed
Build number : 6
Build artifacts

@0xc0170 0xc0170 merged commit aec6303 into ARMmbed:master Apr 21, 2020
@mergify mergify bot removed the ready for merge label Apr 21, 2020
@mergify
Copy link

mergify bot commented Apr 21, 2020

This PR does not contain release version label after merging.

@mergify mergify bot added the release version missing When PR does not contain release version, bot should label it and we fix it afterwards label Apr 21, 2020
@0xc0170 0xc0170 added release-version: 6.0.0-beta-1 and removed release version missing When PR does not contain release version, bot should label it and we fix it afterwards labels Apr 21, 2020
@maclobdell
Copy link
Contributor

@sreeharshaangara I believe the infrastructure is there to download the keys to the right location before building, however it is a per-target script. I've emailed our team to add it for this target also.

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.

9 participants