Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

PSoC™ 6 Forum Discussions

GrCa_1363456
Level 5
First comment on KBA First comment on blog 250 sign-ins
Level 5

Is it possible to create an SDIO interface on a PSoC 63 in a WLCSP?
Specifically; is it possible to either split the SDIO to multiple ports or route a UDB based SDIO interface to one of the ports with six or more signals?

There is support for creating a UDB based SDIO interface @ https://github.com/Infineon/udb-sdio-whd
The available library supports an SDIO interface on one of three different ports: P2, P9 or P12. The SDIO interface requires six (6) signals on whichever port is selected for SDIO. Reference the table under "Whats included" @ https://github.com/Infineon/udb-sdio-whd

GrCa_1363456_0-1660242397533.png

It appears only a maximum of five (5) signals are available for any of those three ports on a PSoC 63: P2, P9 or P12.
Other ports on the PSoC 63 in a CSP have six or more signals including: P0, P5, P6, P7, P8, P10 and P11.
Reference Table 7 in PSoC 63 CY8C63x6, CY8C63x7 Datasheet @ https://www.infineon.com/dgdl/Infineon-PSoC_6_MCU_PSoC_63_with_BLE_Datasheet_Programmable_System-on-...

GrCa_1363456_1-1660242532467.pngGrCa_1363456_2-1660242546298.png

 

Greg

0 Likes
1 Solution
Ekta
Moderator
Moderator 250 solutions authored 100 likes received 250 sign-ins
Moderator

Hello @GrCa_1363456 

The support for creating a UDB-based SDIO interface provided in the GitHub link is for PSoC 62 devices.
If you compare the .c files for all the ports P12, P2, and P9 you would observe the only difference that exists is in the SDIO_Host_Config_TriggerMuxes() function. This function is mainly used to Connect the input trigger source and output trigger. As far as I understand it should be possible to modify this function to link the SDIO to a different port for the PSoC 63 device.

You can refer to the TrigMux PDL at this link. Refer to the following directory in mtb shared folder for your project: Refer to a family-specific device header file, e.g. <PDL_DIR>/devices/include/psoc6_03_config.h to get the different input and outputs for TrigMux.

Best Regards
Ekta


View solution in original post

0 Likes
1 Reply
Ekta
Moderator
Moderator 250 solutions authored 100 likes received 250 sign-ins
Moderator

Hello @GrCa_1363456 

The support for creating a UDB-based SDIO interface provided in the GitHub link is for PSoC 62 devices.
If you compare the .c files for all the ports P12, P2, and P9 you would observe the only difference that exists is in the SDIO_Host_Config_TriggerMuxes() function. This function is mainly used to Connect the input trigger source and output trigger. As far as I understand it should be possible to modify this function to link the SDIO to a different port for the PSoC 63 device.

You can refer to the TrigMux PDL at this link. Refer to the following directory in mtb shared folder for your project: Refer to a family-specific device header file, e.g. <PDL_DIR>/devices/include/psoc6_03_config.h to get the different input and outputs for TrigMux.

Best Regards
Ekta


0 Likes