This event will be generated as a response to any QSPI task. Address offset into the external memory for Execute in Place operation. Value must be a multiple of 4. Minimum amount of time that the CSN pin must stay high before it can go low again.
Value is specified in number of 16 MHz periods Mode 0: Data are captured on the clock rising edge and data is output on a falling edge. Mode 3: Data are captured on the clock falling edge and data is output on a rising edge.
QSPI peripheral is busy. Value of external flash device Status Register. When the external flash has two bytes status register this field includes the value of the low byte. Duration needed by external flash to enter DPM. Duration needed by external flash to exit DPM. A new custom instruction is sent every time this register is written. Enable long frame mode. Block diagram. Configuring peripheral Before any data can be transferred to or from the external flash memory, the peripheral needs to be configured.
See Reference circuitry for the recommended pins. The READY event will be generated when the interface has been activated and the external flash memory is ready for access. Important: If the IFCONFIG0 register is configured to use the quad mode, the external flash device also needs to be set in the quad mode before any data transfers can take place. Figure 2. XIP memory map. Figure 3. Sending custom instruction. Deep power-down mode The external flash memory can be put in deep power-down mode DPM to minimize its current consumption when there is no need to access the memory.
Instruction set The table below shows the instruction set being used by the QSPI peripheral when communicating with an external flash device. Table 1. Interface description Figure 4. Figure 5. Figure 6. Figure 7. Figure 8. Figure 9. Figure Registers Table 2. Table 3. LEN 0x Size of block to be erased.
IO2 0x Pin select for serial data IO2. Trigger 1 Trigger task. NotGenerated 0 Event not generated Generated 1 Event generated. The length must be a multiple of 4 bytes. LEN Address offset: 0x Size of block to be erased. PP opcode 0x PP2O opcode 0xA2. PP4O opcode 0x PP4IO opcode 0x Disable 0 Disable DPM feature. Enable 1 Enable DPM feature. Exit 0 Exit DPM. Enter 1 Enter DPM. Disabled 0 External flash is not in DPM. Enabled 1 External flash is in DPM. NoInstr 0 Do not send any instruction.
Opcode 1 Send opcode. OpByte0 2 Send opcode, byte0. All 3 Send opcode, byte0, byte1. Disable 0 No wait. Enable 1 Wait. Write enable. Read status register. Write status register.
Read bytes at higher speed. Dual-read output. Quad-read output. Page program. Dual-page program output. Quad-page program output. Sector erase. Block erase. Chip erase.
Enter deep power-down mode. Exit deep power-down mode. Enable 32 bit address mode. External memory interface. Activate QSPI interface. Enable or disable interrupt. Enable interrupt. Disable interrupt. Flash memory source address. RAM destination address. Read transfer length. Flash destination address. RAM source address. Write transfer length. Start address of flash block to be erased. Size of block to be erased. Pin select for serial clock SCK.
Pin select for chip select signal CSN. Pin select for serial data IO2. Pin select for serial data IO3. Interface configuration. Status register. Forgot Your Password? Forgot your Username? Haven't received registration validation E-mail? User Control Panel Log out. Forums Posts Latest Posts. View More. Recent Blog Posts. Unread PMs. Forum Themes Elegant Mobile. Essentials Only Full Version. Starting Member. If so can somebody refer on schematic and code?
Super Member. A Guy on the Net. Unless I have mis read the data sheet. I let it go at least by now. Lab Member No. I believe the MZ However it is designed to boot Linux, so maybe. Unfortunately I didn't save the datasheet when someone here linked to it.
NKurzman Unless I have mis read the data sheet. The MZEF data sheets say that the SQI module is configurable as an extra SPI port, though I have to admit that it wasn't obvious to me how to do this - I was considering the feasibility of implementing the 4 bit interface mode to an SD card, but that requires initialization in 1 bit SPI mode and it would be a hassle to route both interfaces to the card.
The problem with the 4 bit interface to SD cards is that it may require licensing money. I am not a lawyer but the SD card association holds the interface definition behind a membership fee, and seems to require each OEM to license it - it would be really nice if Microchip would cover the license and we could all use it, but I think there are serious barriers to that.
Thanks, but it may be too late for me now. I may be in my final board spin. Oh well. But it is good to know. Here something another It wold be useful, if somebody from mChip staff explaine the situation. If you want Microchips take on the subject you would need to put in a support ticket.
0コメント