Skip to content

MX25LM51245G QSPI test config file #11290

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 5 commits into from
Aug 29, 2019

Conversation

LMESTM
Copy link
Contributor

@LMESTM LMESTM commented Aug 22, 2019

Description

This PR adds test config file for MX25LM51245G single and octal IO serial flash memory.

This memory does not support Dual or Quad lines transfers so that test files have been modified in consequence to keep only the valid configurations.

See #11287 for question related to this memory

Pull request type

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

Reviewers

@bulislaw @MarceloSalazar

Release Notes

LMESTM added 3 commits August 22, 2019 15:10
For memories like MX25LM51245G that do not support dual or quad read (in
this case because it supports single and octo-IO modes)
@ciarmcom
Copy link
Member

@LMESTM, thank you for your changes.
@bulislaw @MarceloSalazar @ARMmbed/mbed-os-hal @ARMmbed/mbed-os-test @ARMmbed/mbed-os-maintainers please review.

LMESTM and others added 2 commits August 23, 2019 14:47
For STM32 platforms that embed an OSPI IP, we're offering
a QSPI fallback support with this commit.

When OSPI is supported in mbed, we can consider adding full
OSPI support
@0xc0170 0xc0170 removed the request for review from a team August 26, 2019 11:05
@0xc0170
Copy link
Contributor

0xc0170 commented Aug 26, 2019

CI started

@mbed-ci
Copy link

mbed-ci commented Aug 26, 2019

Test run: FAILED

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

Failed test jobs:

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

@LMESTM LMESTM force-pushed the MX25LM51245G_QSPI_test_config branch from 136df33 to 8cd00b3 Compare August 28, 2019 11:29
@0xc0170
Copy link
Contributor

0xc0170 commented Aug 28, 2019

@LMESTM what was the last push about? This is ready now for CI , isn't it?

@LMESTM
Copy link
Contributor Author

LMESTM commented Aug 28, 2019

@0xc0170 it was a mistake as I pushed to the wrong branch, the commit was for #11291
I've restored this one to the same previous state without any change, ready for CI indeed.

@0xc0170 0xc0170 mentioned this pull request Aug 28, 2019
@0xc0170
Copy link
Contributor

0xc0170 commented Aug 28, 2019

This PR is part of rollup PR #11366

Please do not update this PR, or if needed, let us know asap

@0xc0170 0xc0170 removed the rollup PR label Aug 29, 2019
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.

6 participants