Hello TI team,
OSPI on current SDK 6.0.0.7 is not working, somehow we found a workaround to boot the EVM. But later we found sd card (MMC1) is not working at all. Please help to investigate.
Thank you.
Best Regards
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hello TI team,
OSPI on current SDK 6.0.0.7 is not working, somehow we found a workaround to boot the EVM. But later we found sd card (MMC1) is not working at all. Please help to investigate.
Thank you.
Best Regards
Hi Kemal,
I have looked the thread, I think It's irrelevant to our issues.
Could you please to reproduce on latest SDK 6.0.0.3 ?
Thank you.
Hello,
I am helping a colleague of yours on the OSPI issue and I am wondering if you could please share the workaround to boot the board. I am investigating any board differences and it would help if you could please share your board information.
Regards,
Krunal
Hello,
I am not having any OSPI boot issues but I am able to replicate the SD card problem on my EVM. I have reached out to our driver expert and I will be keep you posted on any updates.
Regards,
Krunal
Hello,
The issue is that the Uboot code in PSDK6.0 does not observe the MMC controller card detection debounce delay but instead proceeds straight from am654_sdhci_init() to probing the SDHCI controller via sdhci_probe() (all in drivers/mmc/am654_sdhci.c). Later TI U-Boot versions (tag ti2019.02 +) implement a dynamic delay between am654_sdhci_init() and sdhci_probe().
However, you should be able to apply the following two patches on top of the Uboot in PSDK6.0 and resolve your problem:
“mmc: sdhci: Implement SDHCI card detect”
“HACK: mmc: am654_sdhci: Wait for 1 second card detect debounce”
Regards,
Krunal