Skip to content
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

FPGA tests: SPI test cases order issue #11757

Closed
yarbcy opened this issue Oct 28, 2019 · 5 comments
Closed

FPGA tests: SPI test cases order issue #11757

yarbcy opened this issue Oct 28, 2019 · 5 comments

Comments

@yarbcy
Copy link
Contributor

yarbcy commented Oct 28, 2019

Description of defect

FPGA tests: SPI test case order issue

@0xc0170 @mprse

I run SPI tests.

Case cases[] = {
// This will be run for all pins
Case("SPI - init/free test all pins", all_ports<SPIPort, DefaultFormFactor, spi_test_init_free>),

// This will be run for all peripherals
Case("SPI - basic test", all_peripherals<SPIPort, DefaultFormFactor, spi_test_common<SPITester::Mode0, 8, TRANSFER_SPI_MASTER_WRITE_SYNC, FREQ_1_MHZ> >),

Expected is to PASS 2 test cases. First passed, second failed.
When I run them separatelly - each of them passed.

Target(s) affected by this defect ?

Tested on CY8CKIT_062_WIFI_BT

Toolchain(s) (name and version) displaying this defect ?

Tested on GCC_ARM

What version of Mbed-os are you using (tag or sha) ?

Latest

What version(s) of tools are you using. List all that apply (E.g. mbed-cli)

N/N

How is this defect reproduced ?

Always.

@ciarmcom
Copy link
Member

Internal Jira reference: https://jira.arm.com/browse/MBOTRIAGE-2282

@yarbcy
Copy link
Contributor Author

yarbcy commented Oct 30, 2019

@0xc0170 Could you please take a look?

@0xc0170
Copy link
Contributor

0xc0170 commented Oct 30, 2019

@0xc0170 Could you please take a look?

@ARMmbed/mbed-os-hal to review

@mprse
Copy link
Contributor

mprse commented Oct 30, 2019

This also looks like a problem with releasing the peripheral. @yarbcy How the test fails? Can you provide the output?

@yarbcy
Copy link
Contributor Author

yarbcy commented Oct 30, 2019

@mprse Looks like the problem is different. Now working on debug. Close this issue.

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

No branches or pull requests

5 participants