we are using RT595 board as host and our module connected over SDIO interface to RT595. in longer runs we observed that SDIO write is failing... that's because we are receiving kUSDHC_DataCrcErrorFlag interrupt from hardware.
under which circumstances we see this kind of interrupt from hardware?
Note: we are using SDIO clock @25MHz and even we lowered till 8MHz but still are seeing issue. For SDIO initialization we followed SDK_2.6.0_EVK-MIMXRT595 (1)\boards\evkmimxrt595\driver_examples\sdio\iar Demo
Through SDIO block method(256bytes) we are testing instead of byte by byte. we are sending some audio pkts(367bytes of single data pkt, so SDIO uses 2 blocks to transfer on every single iteration) continuously over sdio interface. within 1-2hrs timeline we are seeing this SDIO Write failed.
Yeah, we too aware that 2.10 is out however for some reason we didn't port/integrate that SDK to our customized IAR project since the project is in production phase. May i know what are SDIO fixes made btw 2.6 & 2.10?
Also in general, what would be the case where we get this kind of kUSDHC_DataCrcErrorFlag interrupt? please share Any Doc would explain about SDIO transfer failures
Thanks,
Sunil Dhath.
Hi @sunildhath ,
This is the changelog. https://mcuxpresso.nxp.com/api_doc/dev/2636_doc/MCUXpresso%20SDK%20ChangeLog_MIMXRT595S.pdf
In sdk2.6.0, sdhc driver version should be 2.2.8. In sdk2.10.1, it is 2.8.0. The SDIO card driver version is also different.
kUSDHC_DataCrcErrorFlag is happened when there is Data CRC error during writing or reading. But there isn't application notes or documents about it.
Regards,
Jing
Hi @sunildhath ,
Can you give more detail about the problem? How you test and how to reproduce the error?
The most update SDK version is 2.10. The SD driver should also be updated. Please test on the new SDK.
Regards,
Jing