Bringing up a custom board. MMC1 works for u-boot but after loading kernel, it cannot detect the sd card. Scoping the nets shows activity during u-boot but no activity once booting the kernel.
This same kernel and device tree boots fine on the AM574 IDK.
I've confirmed the card detect works and double checked the pinmux just incase.
U-Boot 2019.01-00919-g3bda0db8d9ba-dirty (Aug 20 2020 - 17:27:58 -0400)
Linux version 4.19.79-00309-g5d39485ad75a-dirty
[ 2.881536] sdhci: Secure Digital Host Controller Interface driver [ 2.887774] sdhci: Copyright(c) Pierre Ossman [ 2.893070] sdhci-pltfm: SDHCI platform and OF driver helper [ 2.900399] sdhci-omap 4809c000.mmc: Linked as a consumer to regulator.12 [ 2.907253] sdhci-omap 4809c000.mmc: failed to set system capabilities [ 2.913898] sdhci-omap 4809c000.mmc: Dropping the link to regulator.12 [ 2.921773] ledtrig-cpu: registered to indicate activity on CPUs [ 2.933756] NET: Registered protocol family 10 [ 2.939189] Segment Routing with IPv6 [ 2.942930] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver [ 2.949388] NET: Registered protocol family 17 [ 2.954046] Key type dns_resolver registered [ 2.958513] Registering SWP/SWPB emulation handler [ 2.963330] omap_voltage_late_init: Voltage driver support not added [ 2.969733] Power Management for TI OMAP4+ devices. [ 2.975333] Loading compiled-in X.509 certificates [ 3.005410] dmm 4e000000.dmm: workaround for errata i878 in use [ 3.012979] dmm 4e000000.dmm: initialized all PAT entries [ 3.020680] sdhci-omap 4809c000.mmc: Linked as a consumer to regulator.12 [ 3.027550] sdhci-omap 4809c000.mmc: failed to set system capabilities [ 3.034217] sdhci-omap 4809c000.mmc: Dropping the link to regulator.12 [ 3.042011] sdhci-omap 4809c000.mmc: Linked as a consumer to regulator.12 [ 3.048901] sdhci-omap 4809c000.mmc: failed to set system capabilities [ 3.055529] sdhci-omap 4809c000.mmc: Dropping the link to regulator.12 [ 3.062945] hctosys: unable to open rtc device (rtc0) [ 3.068744] ALSA device list: [ 3.071726] No soundcards found. [ 3.075928] Waiting for root device PARTUUID=611581f2-02... [ 13.287736] random: fast init done [ 13.291223] random: crng init done [ 33.127768] vdd_3v3: disabling [ 33.130839] aic_dvdd_fixed: disabling [ 33.134521] pbias_mmc_omap5: disabling
Checking pinmux. It looked alright. Slightly different in u-boot which was configuring "Virtual Muxes" which has something to do with the IO Timings. I tried to match u-boot but this didn't help.
=> mm 4A003754 4a003754: 000601b0 ? 4a003758: 000601b0 ? 4a00375c: 000601b0 ? 4a003760: 000601b0 ? 4a003764: 000601b0 ? 4a003768: 000601b0 ? 4a00376c: 000e0000 ? 4a003770: 000d0000 ? root@mitysom-am57x:~# omapconf dump 0x4a003754 0x4a003770 |----------------------------| | Address (hex) | Data (hex) | |----------------------------| | 0x4A003754 | 0x00060000 | | 0x4A003758 | 0x00060000 | | 0x4A00375C | 0x00060000 | | 0x4A003760 | 0x00060000 | | 0x4A003764 | 0x00060000 | | 0x4A003768 | 0x00060000 | | 0x4A00376C | 0x000E0000 | | 0x4A003770 | 0x000D0000 | |----------------------------| devmem2 0x4a003754 w 0x000601b0 devmem2 0x4a003758 w 0x000601b0 devmem2 0x4a00375c w 0x000601b0 devmem2 0x4a003760 w 0x000601b0 devmem2 0x4a003764 w 0x000601b0 devmem2 0x4a003768 w 0x000601b0 root@mitysom-am57x:~# omapconf dump 0x4a003754 0x4a003770 |----------------------------| | Address (hex) | Data (hex) | |----------------------------| | 0x4A003754 | 0x000601B0 | | 0x4A003758 | 0x000601B0 | | 0x4A00375C | 0x000601B0 | | 0x4A003760 | 0x000601B0 | | 0x4A003764 | 0x000601B0 | | 0x4A003768 | 0x000601B0 | | 0x4A00376C | 0x000E0000 | | 0x4A003770 | 0x000D0000 | |----------------------------|