2025-05-18 7:53 PM
The reason is that the update of the HAL library caused the SD card problem, which led to bus_hault after the restart. The SD card will only be restarted when there is a read/write issue. The reset process is deinit followed by init.
Later, it was found that DPSM was an unexplainable setting, causing the driver to believe that there was data directly read from the fifo, but the data program was written to DPSM in conjunction with SDMMC_CK.
Then I changed the driver code to seem to have solved the problem, and restarted the code by adding abort before deinit and init.
1、Why does the SD card often malfunction? Is it caused by the clock waveform? Is this waveform setting incorrect for DPSM?
I adjusted the frequency to 4M, but the Voltage overshoot was very large.Yellow represents CK and pink represents 3.3V voltage
2、I used a soft restart for the SD card, but it seems to be of no use. Is there a way to solve the problem of the SDMMC getting stuck at a certain state due to being stuck at the DPSM?
If the abort continues, it will cause the IDMA to step on other stack Spaces, thereby resulting in a hardfault.So if abort fails once, I won't use the SD card anymore.
When there is a problem with the SD card, it will keep waiting for the flag bit. The same is true of reinitialization
Thank you for your help.
2025-05-18 10:29 PM
>1、Why does the SD card often malfunction?
Probably a hardware problem.
- How long are wires/connection from cpu pin to sd-card ?
- pin speed you set ?
- clock for sdmmc is ..? MHz
- DMA used ? (Tried without DMA ?)
2025-05-18 11:31 PM
The cable from the CPU to the sd card is 32.9MM long
SDMMC_CK is 4Mhz
IO speed is GPIO_SPEED_FREQ_MEDIUM
yes,i use dma;I didn't try not to use dma