Improve QSPIFBlockDevice conformance to SFDP #11531

…tandard

…ssary

Replace with macros from the test flash_config header, consistent with how most commands are built in this test.

This function writes a "config" register to ensure that the flash part is in high performance mode, not low-power mode. This is required at by at least MX25R6435F in order to operate at frequencies > 33MHz (for reference, DISCO_L475VG_IOT01A runs the QSPI interface at 80 MHz). The config register that this writes does not appear to be covered by the SFDP spec (JESD216D.01) so this remains the status quo of unconditional execution, as has been done on master since ARMmbed#8352.

QSPIFBlockDevice::_clear_block_protection() has logic to retain the WIP and WEL bits in status register 1, but it failed to account for the situation where the QE bit is also in status register 1. In _sfdp_set_quad_enabled, note the status register and bit therein for the quad enable, so that _clear_block_protection can retain it.

Introduce a separate function for handling alterations to device interaction which are not covered by the SFDP tables and therefore require checking against the vendor id.

Default to 2 status registers, but update this value if necessary during vendor quirk handling for parts (currently only Macronix) which have one status register and two control registers. For the purposes of QSPIFBlockDevice, these are all considered status (or at least "status-like") registers because they are all written via the Write Status Register instruction. Set the custom RDCR instruction for Macronix during quirk handling. Update reading and writing of status registers to handle a variable number of status registers.

Use a vendor id check to only perform this enable on devices which define the second configuration register where the fast mode enable bit lives. Change _enable_fast_mode to use the standard status register reading and writing functions

4-byte addressing has been seen to cause failures on NORDIC boards and with Macronix memories. Suppress the attempt to enable it on that hardware (via vendor quirks and a target check) until either the failure cause can be fixed or a more robust suppression mechanism is implemented.

The addition of trace logging during greentea tests pushes the multithreaded read-write test beyond the limits of the stack it allocates for its threads. The increase of 128 bytes was chosen by experimentation.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Improve QSPIFBlockDevice conformance to SFDP #11531

Improve QSPIFBlockDevice conformance to SFDP #11531

Commits on Nov 12, 2019