OSPI driver object.
Data Fields | |
OSPI_Handle | handle |
uint32_t | transferMode |
uint32_t | xferLines |
uint32_t | rdDummyCycles |
uint32_t | cmdDummyCycles |
uint32_t | rdDataCapDelay |
uint32_t | phyRdDataCapDelay |
uint32_t | numAddrBytes |
uint32_t | cmdExtType |
uint32_t | isOpen |
SemaphoreP_Object | lockObj |
SemaphoreP_Object | transferSemObj |
HwiP_Object | hwiObj |
uint32_t | phyEnableSuccess |
OSPI_Transaction * | currTrans |
void * | ospiDmaHandle |
OSPI_Handle OSPI_Object::handle |
Instance handle
uint32_t OSPI_Object::transferMode |
Polling, Blocking or Callback mode. Refer OSPI_TransferMode
uint32_t OSPI_Object::xferLines |
Number of lines used for OSPI reading/writing
uint32_t OSPI_Object::rdDummyCycles |
Number of dummy cycles needed for read
uint32_t OSPI_Object::cmdDummyCycles |
Number of dummy cycles needed for cmd
uint32_t OSPI_Object::rdDataCapDelay |
Read data capture delays needed
uint32_t OSPI_Object::phyRdDataCapDelay |
Read data capture delays needed when phy is enabled
uint32_t OSPI_Object::numAddrBytes |
Number of bytes used to represent address to be sent to flash. This is the actual number of bytes used. The code to be programmed to registers is this value-1. That is, for 4-byte addressing mode, register should be programmed as 3
uint32_t OSPI_Object::cmdExtType |
In dual byte opcode mode, the extended opcode can vary depending on flash This variable should be populated from the flash driver using the OSPI_setCmdExtType API
uint32_t OSPI_Object::isOpen |
Flag to indicate if the instance is already open
SemaphoreP_Object OSPI_Object::lockObj |
Driver lock object
SemaphoreP_Object OSPI_Object::transferSemObj |
Transfer Sync Semaphore object
HwiP_Object OSPI_Object::hwiObj |
Interrupt object
uint32_t OSPI_Object::phyEnableSuccess |
This has to be set from the flash driver if the PHY tuning completed successfully
OSPI_Transaction* OSPI_Object::currTrans |
Pointer to current transaction struct
void* OSPI_Object::ospiDmaHandle |