9.3.53 SPI Write Protection Status Register
| Name: | FLEX_SPI_WPSR |
| Offset: | 0x4E8 |
| Reset: | 0x00000000 |
| Property: | Read-only |
| Bit | 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | |
| Access | |||||||||
| Reset |
| Bit | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | |
| Access | |||||||||
| Reset |
| Bit | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | |
| WPVSRC[7:0] | |||||||||
| Access | R | R | R | R | R | R | R | R | |
| Reset | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | |
| Bit | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | |
| PADERR | WPVS | ||||||||
| Access | R | R | |||||||
| Reset | 0 | 0 |
Bits 15:8 – WPVSRC[7:0] Write Protection Violation Source
When WPVS = 1, WPVSRC indicates the register address offset at which a write access has been attempted.
Bit 1 – PADERR Output Pad Error (cleared on read)
| Value | Description |
|---|---|
| 0 | No error detected during a character transfer. |
| 1 | Two successive bit periods with a difference between the data read at the output of the MOSI or NPCS0 pad buffers and the corresponding inputs driven by SPI or abnormal number of SPCK edges (or no clock edge) at the output of SPCK pad buffer in synchronous mode. This may be due to erroneous IO multiplexing configuration, external short circuits, etc. |
Bit 0 – WPVS Write Protection Violation Status
| Value | Description |
|---|---|
| 0 | No write protect violation has occurred since the last read of FLEX_SPI_WPSR. |
| 1 | A write protect violation has occurred since the last read of FLEX_SPI_WPSR. If this violation is an unauthorized attempt to write a protected register, the associated violation is reported into field WPVSRC. |
