CYW43362
4.2.1.1 Command Structure
The gSPI command structure is 32 bits. The bit positions and definitions are as shown in Figure 12.
Figure 12. gSPI Command Structure
BCM_SPID Command Structure
27
31 30 29 28
11 10
0
C
A
F1 F0
Address – 17 bits
Packet length - 11bits *
* 11’h0 = 2048 bytes
Function No: 00 – Func 0: All SPI specific registers
01 – Func 1: Registers and meories belonging to other blocks in the chip (64 bytes max)
10 – Func 2: DMA channel 1. WLAN packets up to 2048 bytes.
11 – Func 3: DMA channel 2 (optional). Packets up to 2048 bytes.
Access : 0 – Fixed address
1 – Incremental address
Command : 0 – Read
1 – Write
4.2.1.2 Write
The host puts the first bit of the data onto the bus half a clock-cycle before the first active edge following the CS going low. The fol-
lowing bits are clocked out on the falling edge of the gSPI clock. The device samples the data on the active edge.
4.2.1.3 Write/Read
The host reads on the rising edge of the clock requiring data from the device to be made available before the first rising clock edge
of the clock burst for the data. The last clock edge of the fixed delay word can be used to represent the first bit of the following data
word. This allows data to be ready for the first clock edge without relying on asynchronous delays.
4.2.1.4 Read
The read command always follows a separate write to set up the WLAN device for a read. This command differs from the write/read
command in the following respects: a) chip selects go high between the command/address and the data and b) the time interval
between the command/address is not fixed.
4.2.1.5 Status
The gSPI interface supports status notification to the host after a read/write transaction. This status notification provides information
about any packet errors, protocol errors, information about available packet in the RX queue, etc. The status information helps in
reducing the number of interrupts to the host. The status-reporting feature can be switched off using a register bit, without any timing
overhead. The gSPI bus timing for read/write transactions with and without status notification are as shown in Figure 13 below and
Figure 14 on page 19. See Table 6 on page 19 for information on status field details.
Document No. 002-14779 Rev. *G
Page 17 of 60
CYPRESS [ CYPRESS ]
