"Everything okay" seems too broad/optimistic for what sounds like just a DC test.Trilok wrote: ↑We crossed checked hardware data lines(D0 - D3) it seems to be everything okay.
What does "access" mean?Trilok wrote: ↑1. I booted AT-91Bootstarp and U-boot from QSPI, in U-boot i can able to access the SD card. I'm still in confusion why AT91Bootstrap is not able to load the files from SD card.
Does it mean read and write operations with 100% data integrity?
Maybe you're "in confusion" because you haven't grasped that there's more than one configuration of the sdmmc interface for reading from the SDcard?
Besides the numerous sdmmc configurations (for data width, voltages, and speeds), there are the various SoC configurations to also consider (e.g. clock sources).
Nor have you provided any evidence that your hardware is reliable.
In fact your own tests indicate that your confusion seems to be based on a denial that your HW could be faulty.
"Bare metal example code" is a vague description of what you're using.Trilok wrote: ↑2. I loaded bare metal example code from IAR embedded studio.
Are those "errors" during the "When SD detected" sequence significant or not?Trilok wrote: ↑In the that some times SD is detecting some times SD is not detecting(Init failing). Here is the log :
I. When SD detected
II. When SD not detected
Do you have proven known-functional hardware to perform this same test with your "bare metal example code" for comparison?
Does this "bare metal example code" work consistently and reliably on known-functional hardware?
If so, then this "sometimes works, sometimes doesn't" results on your HW essentially defines flaky hardware and contradicts your "everything okay" assessment.