hyperFlash write access

rans — Sun, 16 Sep 2018 06:56:14 GMT

Hello,

I would please like to ask about hyperFlash example (evkmimxrt1050_flexspi_hyper_flash_polling_transfer):

In the example, I see the following parts:

1. hyperFlash initialization

2. hyperFlash write of page

3. hyperFlash read of page

4. compare the read and write contents.

I had assumed that flexSPI interface only needs to be initialized (There is LUT for read and write command) , and then can be accessed by direct read/write from the absolute address (where the device is mapped to).

Yet, I see that the write functionality is done through wrappers:

flexspi_nor_flash_page_program -> FLEXSPI_TransferBlocking -> FLEXSPI_WriteBlocking

The read is done by direct access to address, is expected.

Can someone explain why the write must use this wrappers ?

Thank you,

ranran

Re: hyperFlash write access

igorpadykov — Mon, 17 Sep 2018 23:31:39 GMT

Hi ranran

>Can someone explain why the write must use this wrappers ?

since writing procedure requires some time for performing flashing
sequence, it waits (using blockng wrapper) until hyperflash will be ready for
next usage.

Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

i.MX RT Crossover MCUsのトピックhyperFlash write access

hyperFlash write access

Re: hyperFlash write access