Hi,My SoC configuration is as below:Core: Arm A65 (v8)U-boot version: 2021-AprExecution and debug environment: Synopsys VDK simulator
My SoC has Synopsys SDHCI. To enable the same in u-boot, I've enabled the following options in defconfig:CONFIG_MMC=y CONFIG_DM_MMC=y CONFIG_MMC_SDHCI=y CONFIG_CMD_MMC=y CONFIG_MMC_SDHCI_ABC=y The last entry above is specific to my SoC. SoC specific sdhci file has been added in drivers/mmc folder and to necessary Kconfig / Makefile. Object dump has been checked to ensure that the default sdhci.c and soc_specific_sdhci.c is part o the binary. Compatible-id has been defined as necessary in the device-tree and soc_specific_sdhci.c. After u-boot board_f / board_r initialisation, dm_dump_all() was executed from cli_simple.c to check the probe status. Following was the uart output: Class Index Probed Driver Name----------------------------------------------------------- root 0 [ + ] root_driver root_driver rsa_mod_ex 0 [ ] mod_exp_sw |-- mod_exp_sw simple_bus 0 [ ] simple_bus |-- dwc_eqos_tlm_bb virtio 0 [ ] virtio-mmio |-- virtio_block@21800000 virtio 1 [ ] virtio-mmio |-- virtio_block@21c00000 serial 0 [ + ] ns16550_serial |-- uart@0070d000 mmc 0 [ + ] abc_xyz_sdhci_5.1 `-- mmc@00716000 blk 0 [ ] mmc_blk `-- m...@00716000.blk Two questions:1. After this output, the command prompt is also printed in the terminal and then a synchronous (data abort) exception is hit. It looks like memory has been corrupted sometime back and the problem shows up later. if i remove mmc from the device tree, then the exception issue does not happen. Can you point me to the areas i need to check / debug for identifying this problem? 2. Another aspect i observed was that after enabling MMC related macros in defconfig, the generated binary size reduced by ~200 kiloBytes (even though two .c files have been added). I've checked the map file but could not deduce the reason for this size reduction. Can you point me to the areas to check? -RegardsVin
