search

ARMmbed / mbed-os

Arm Mbed OS is a platform operating system designed for the internet of things
https://mbed.com
Other
4.67k stars 2.98k forks source link

QSPIF is giving error -0x4002 (Parse SFDP Headers Failed) #13710

Closed ranjitsinh-rathod closed 3 years ago

ranjitsinh-rathod commented 4 years ago

Description of defect

I am working on custom hardware based on PSoC 6 Wi-Fi BT Prototyping Kit (CY8CPROTO-062-4343W) and working on Mbed OS 5.15.4. Currently moved to Mbed OS 5.15.5 and the same issue observed in it, too. I am working on this project for Datahoist.

In our custom hardware, we have used the S25FL064L chip as a QSPI flash.

We have an issue in init using QSPIFBlockDevice. When I have enabled traces, I got a print “Init - Verification of SFDP signature and version failed”. Also, a strange thing is this issue comes when we do init -> deinit ->init. So the first time the flash was successfully getting initialized, but after the deinit, when we do init again, it is having issues in SFDP header. I have printed the SFDP header for success as well as failure case, which will be in the log.

Target(s) affected by this defect ?

custom hardware based on PSoC 6 Wi-Fi BT Prototyping Kit (CY8CPROTO-062-4343W)

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

ARM6 using from Mbed Studio

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

mbed-os-5.15.4

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

ARM Compiler - 6.14 Clangd - 8.0.2 Python tools - 0.5.3 mbed - 1.10.2

How is this defect reproduced ?

1) Initialising QSPI 2) Deinit QSPI 3) Again Init QSPI and got issue in SFDP Header parsing QSPIF_IssueInSFDPHeader.txt

ranjitsinh-rathod commented 4 years ago

I am working on custom hardware based on PSoC 6 Wi-Fi BT Prototyping Kit (CY8CPROTO-062-4343W) and working on Mbed OS 5.15.4. I am working on this project for Datahoist.

In our custom hardware, we have used the S25FL064L chip as a QSPI flash.

We have an issue in init using QSPIFBlockDevice. When I have enabled traces, I got a print “Init - Verification of SFDP signature and version failed”. Also, a strange thing is this issue comes when we do init -> deinit ->init. So the first time the flash was successfully getting initialized, but after the deinit, when we do init again, it is having issues in SFDP header. I have printed the SFDP header for success as well as failure case, which will be in the log.

ciarmcom commented 4 years ago

@ranjitsinh-rathod thank you for raising this issue.Please take a look at the following comments:

Could you add some more detail to the description? A good description should be at least 25 words. What version of Mbed OS are you using (tag or sha)?

NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'.This indicates to us that at least all the fields have been considered. Please update the issue header with the missing information, the issue will not be mirroredto our internal defect tracking system or investigated until this has been fully resolved.

ranjitsinh-rathod commented 4 years ago

@ranjitsinh-rathod thank you for raising this issue.Please take a look at the following comments:

Could you add some more detail to the description? A good description should be at least 25 words. What version of Mbed OS are you using (tag or sha)?

NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'.This indicates to us that at least all the fields have been considered. Please update the issue header with the missing information, the issue will not be mirroredto our internal defect tracking system or investigated until this has been fully resolved.

Description added.

0xc0170 commented 4 years ago

cc @ARMmbed/mbed-os-core

adbridge commented 4 years ago

@ranjitsinh-rathod you are also missing the mbed-os version in the header, could you please add this. Ahh I see you mention it in the description but did not put it in the required field. I'll fix this for you.

ciarmcom commented 4 years ago

Thank you for raising this detailed GitHub issue. I am now notifying our internal issue triagers. Internal Jira reference: https://jira.arm.com/browse/IOTOSM-2468

ranjitsinh-rathod commented 4 years ago

It was closed by mistake. Reopening it. sorry for the inconvenience caused.

0xc0170 commented 3 years ago

cc @ARMmbed/team-cypress

kyle-cypress commented 3 years ago

@ranjitsinh-rathod , is this issue reproducible on the standard CY8CPROTO-062-4343W? Or only on your custom hardware?

ranjitsinh-rathod commented 3 years ago

@kyle-cypress no, it is not reproducible on the CY8CPROTO-062-4343W kit. But it is always reproducible on the custom board we have designed. Please note that we have used different Qspi chip S25FL064L in our board.

ciarmcom commented 3 years ago

This issue is on our backlog, but given our current priorities we can make no commitment to address this in the near term.

As an open source project, we welcome fixes to Mbed OS, so we have opened this issue up for community contribution.

If this is an issue you think you could address yourselves, then we'd welcome the contribution. Please see our guidelines here - https://os.mbed.com/docs/mbed-os/latest/contributing/workflow.html#contributions .

ciarmcom commented 3 years ago

We closed this issue because it has been inactive for quite some time and we believe it to be low priority. If you think that the priority should be higher, then please reopen with your justification for increasing the priority.