sofu_4755251 Before we go to the SDIO issue, was the port of WHD to the STM32 and the 4343 onto the Cube successful? I am not so familiar with the CubeMX environment so please do bear with me if I ask a few basic questions.
STM32F469 porting in WICED This blog post talks about porting of STM32 to WICED which used WWD. Now I know that you are using WHD, but since the two are pretty similar, it may add some value and give you some pointers on what maybe going wrong.
Regarding the SDIO spec and the wwd implementation under the host_platform_sdio_enumerate(), as far as I am aware, our implementation is also based on the spec and is reduced and simplified to have the bare minimum to get the chip up and running.
Do let me know if this helps or if you need help regarding something more specific.
Thanks for the answer. It is good to know that the init sequence in WWD is enough to bring the chip up and running. So i will keep to this implementation in my project, insteading of the whole FSM in the Specs.
Regarding the porting, I have finished (more or less) the work according to the porting guide from WHD and now tried to have the "first contact" with the module. At the moment, I am stucked in the init sequence. I was able to send CMD0. But after sending CMD5, I got a timeout for receiving the response R4. Maybe it is more related to STM than WHD. I will come back if I got more concrete questions.
Anyway, in my opinion, the implementation of such init sequence can/should be included in WHD since the underlying SDIO commands are implemented during the porting process. Or at least, the porting guide can mention that what the "user" of the driver must implement this and maybe also how it can be implemented. At the moment, such information are missing on the WHD page.