-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Issues with SFDP parsing of the Sector Map Parameter Header and Table parsing #11722
Comments
Notes: - CRC and TRNG are disabled on this board since the MCU on this board does not have the required hardware. - QSPI and QSPIF are temporarily removed due to issues related to supporting the new S25FS512S flash chip we have on this board. These will be enabled as soon as we can get the issues resolved. ARMmbed#11722
Internal Jira reference: https://jira.arm.com/browse/MBOCUSTRIA-1940 |
cc @ARMmbed/mbed-os-storage |
@maclobdell Cypress will have one board that will be released publicly at the beginning of 2020 that is impacted by this defect. The impact is that we can't use QSPIBlockDevice with this device as the SFDP results for it are not parsed correctly. Thank you, Ian |
…on this board since the MCU on this board does not have the required hardware. - QSPI and QSPIF are temporarily removed due to issues related to supporting the new S25FS512S flash chip we have on this board. These will be enabled as soon as we can get the issues resolved. #11722
@ARMmbed/mbed-os-storage - Please review and make a suggestion. |
@miteshdedhia7 would you please split the bugs as their own issues. The first bug is fixed by the PR #12270 |
Fixed by #12270. I would close this issue. |
Description
The QSPIFBlockDevice and potentially the SPIFBlockDevice implementation has the following issues,
Commit: fe12608 (HEAD -> master, origin/master) Merge pull request #11444 from jeromecoutant/PR_QSPI_EXTERNAL
Toolchain: All toolchains
Spec Link: JESD216
_sfdp_parse_sfdp_headers()
function on line 787param_header[0] == 81
, the check needs to check for 0x81 (hex) instead of 81 (dec).Spec Reference: JESD216 pg 54 section 6.5.1
Issue request type
The text was updated successfully, but these errors were encountered: