stm32mp131fae7 Baremetal Fall into a busy state after QuadSPI Dual initialization.
hello
@SL2
I am configuring with QuadSPI Dual and encountering an issue where it remains in a busy state and does not resolve.
The circuit is not properly connected yet, so I am currently only testing the pin output.I want to output to Bank2 IO.
I initialized it as follows:
static void MX_QUADSPI_Init(void)
{
hxspi.Instance = QUADSPI;
hxspi.Init.ClockPrescaler = 255;
hxspi.Init.FifoThresholdByte = 1;
hxspi.Init.SampleShifting = XSPI_SAMPLE_SHIFTING_NONE;
hxspi.Init.MemorySize = 0;
hxspi.Init.ChipSelectHighTimeCycle = 1;//XSPI_CS_HIGH_TIME_1_CYCLE;
hxspi.Init.ClockMode = XSPI_CLOCK_MODE_3;
hxspi.Init.MemoryMode = HAL_XSPI_DUAL_MEM;//XSPI_DUALFLASH_ENABLE;
if (HAL_XSPI_Init(&hxspi) != HAL_OK)
{
Error_Handler();
}
}
XSPI_ResetChip();
HAL_Delay(2);
XSPI_AutoPollingMemReady();
XSPI_WriteEnable();
HAL_XSPI_Command(&hxspi, &sCommand, HAL_XSPI_TIMEOUT_DEFAULT_VALUE);
XSPI_Configuration();
XSPI_AutoPollingMemReady();
while (1)
{
HAL_XSPI_Command(&hxspi, &sCommand, HAL_XSPI_TIMEOUT_DEFAULT_VALUE);
HAL_XSPI_Transmit(&hxspi, QSP_DATA, 1000);
HAL_Delay(200);
}
When proceeding as described above, after the XSPI_AutoPollingMemReady function, unknown data is output and the system enters a busy state.
Even when I break in the IDE debug mode, data continues to be output on the oscilloscope.
It seems like the XSPI.c file wasn't generated correctly during CubeMX code generation. As a workaround, you copied the XSPI.c file from the STM32MP135DK example to use in your project.
Please fill in the contents of each function below.
Please review for any potentially problematic areas in the entire content.
Thank you.