embeddedsw Is this response type correct for CMD5

https://github.com/Xilinx/embeddedsw/blob/45a18907084e77bb3a450a035d280130d7ff6e26/XilinxProcessorIPLib/drivers/sdps/src/xsdps_host.c#L1752

Should it be R4 instead of RESP_R1B?

See https://yannik520.github.io/sdio.html "The normal response to CMD5 is R4 in either SD or SPI format."

Oct 22 '25 02:10 TrevorDev

Thanks. We will analyze and fix it in our next release.

Oct 22 '25 04:10 anirudha1977

Hi @TrevorDev - BareMetal driver does not support SDIO interface devices, it is designed to work only with SD and eMMC cards. The CMD5 (SLEEP_AWAKE) command, which returns an R1b response, is applicable to eMMC cards and is defined accordingly in the driver. We will update the public documentation to explicitly state that SDIO interface cards are not supported by the BareMetal driver.

Oct 22 '25 05:10 saikrishnapotthuri

@saikrishnapotthuri is there any plans to support SDIO interface devices in the future? Or any idea how to extend current driver to support them. If i set this to R4 it gets me passed the cmd5 issue i was facing but now I am seeing that there is no implementation for cmd53. I am trying to add support by copying a similar pattern to XSdPs_Read/Write (eg. XSdPs_SetupReadDma + XSdPs_CmdTransfer(...CMD53...)) but not having much luck.

I saw that it seems there is linux support for this. Do you know why/how it works there but not in baremetal?

Any help would be appreciated. Thanks

Oct 27 '25 22:10 webspatial-admin

Hi @TrevorDev - As of now we don't have any plans to support SDIO in BareMetal. In Linux, MMC core/framework takes care of handling SDIO related commands and driver doesn't handle any device specific commands.

Oct 28 '25 05:10 saikrishnapotthuri