Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
Please see the attached document for a description of the issue being seen. Here is a summary:
We are interfacing it with STM32L476VGT Cube 4.26.1. Our firmware is running on STM32Cube_FW_L4_V1.12.0 (equivalent to 1.13.0 qspi). We have been able to successfully read the device ID (0x01 0x60 0x19), erase block (cant verify). Below are the routines, and the capture from our Saleae analyzer. I am looking for any guidance to help understand what the cypress part is looking for.
As per my understanding customer is observing issues with erase and read operations. Is customer setting QPI bit in configuration register 2? If yes, they have to use 4 lines for command, address and data.