MSPI_DebugSop¶
Revision History¶
| Revision NO. | Description |
Data |
|---|---|---|
| 1.0 | Initial release | 03/30/2024 |
1. Overview¶
During the use of MSPI, issues do not occur frequently, mostly related to specific scenario requirements. This document provides several situations for reference debugging.
It includes data transmission anomalies, data reception anomalies, communication timeouts, etc., and provides troubleshooting flowcharts and explanations for each step.
The internal registers of mspi on various platforms are generally unchanged, but there may be differences in the CLKGEN, PADMUX, and BDMA registers. Please refer to the actual platform during troubleshooting.
2. Keyword¶
-
GPIO mode: PAD can be multiplexed into mspi pins through padmux, or it can be set as GPIO pins. When set to GPIO mode, the priority of multiplexing mspi is lower and may be affected.
-
PADMUX: The PADMUX setting bank is PADTOP, used to specify the multiplexing relationship.
-
CLKGEN: Source clock setting register, used to select the clock source for the IP.
-
BDMA: The mspi dma mode requires the BDMA IP to assist in operation, which is responsible for data transfer between memory and mspi.
3. Data Anomalies¶
Data transmission anomalies include no waveform, data errors, and individual pins (CS/CK/MOSI) without waveforms. Among them, the absence of a waveform may be accompanied by a timeout error log, which can be checked in the timeout section.
3.1. Troubleshooting Flowchart¶
3.2. Step Descriptions¶
| Process Node | Node Description |
Exit | Required Analysis Data |
|---|---|---|---|
| A | Capture waveform, this is the most intuitive analysis method for communication issues | B C | - |
| B | Compare waveform analysis with expected data | D E F | - |
| C | In the case of no waveform, it generally occurs due to pin errors (set as GPIO and pull high/low to confirm if the pin is correct), padmux errors, and clk not being enabled, which prevents communication. It may also be that the set trigger condition happens to be an issue with individual pins. Try setting other pins as trigger conditions. When individual pin anomalies occur, check if GPIO mode is enabled and if there are hardware influences | G H I J | - |
| D | Data loss, which may be due to incorrect set transmission byte length | K L | mspi bank register bdma bank register |
| E | Data error | L M | - |
| F | Whether individual pins have no waveform | N | - |
| G | Captured waveform pin error, re-confirm with HW which pins should be captured | O | - |
| H | Incorrect padmux register setting, reconfigure | P | - |
| I | clkgen not enabled, check CLKGEN register table, confirm if gate bit is open | Q | - |
| J | The trigger condition pin of LA or oscilloscope happens to be inactive | - | - |
4. Timeout¶
When an mspi timeout error log occurs, it is generally due to unreasonable code trigger timing, both systems having MSPI enabled, or clkgen not being enabled. Please directly provide the code branch, mspi bank, and clkgen bank.