// Define first EUDA size of 63736MB
mmc enh_area set -c 0 65265664 /dev/mmcblk0
// Define then the first eGPP of 4GB
mmc gp create -c 4194304 1 1 0 /dev/mmcblk0
// Define then the second eGPP of 4GB (and set finalization bit)
mmc gp create -y 4194304 2 1 0 /dev/mmcblk0
"The core also supports up to seven functions in SD1, SD4, but does not support SPI mode. The Zynq-7000 SoC is expected to work with eMMC devices because the protocol is the same as SD, but this has not been extensively verified."
We have brought the topic to the WD FAE, who responds:
"If the host controller has been implemented hard-coded commands, it might not contain the switch command. The vendor of the SoC/FPGA should be aware. A modern mmc host controller IP should not contain any limitation. If the one you are using is designed strictly for SD cards, that could miss hard-coded commands required for eMMC physical partitions manipulation.
So, I guess you need to verify if there are no software aspects limiting the partition switch commands. If you don't see any obvious limitation in the uboot and kernel, you can then ask the SoC vendor to see if the SD/MMC controller is not limited to a certain set of hard-coded commands."
Hoping someone can clarify, whether I have missed a required configuration or if there might be a known limitation of the SoC about this?