[3.8.13] Unable to read SD card

He had an issue with BBB and kernel 3.8.13-bone84 and we were unable to flash eMMC. We managed to solve this issue [3.8.13 - Unable to flash Beaglebone Black Rev C] but now we are facing yet another issue.
If we push the image to eMMC via UMS or by simple booting from a new kernel and copy the image to the eMMC ,the SD card is no longer visible as a device by the BBB.
Any idea how we can solve it;

root@beaglebone:~# dmesg |grep mmc
[ 0.129394] vmmcsd_fixed: 3300 mV
[ 0.719592] bone-capemgr bone_capemgr.10: slot #4: Requesting firmware ‘cape-bone-2g-emmc1.dtbo’ for board-name ‘Bone-LT-eMMC-2G’, version ‘00A0’
[ 0.719609] bone-capemgr bone_capemgr.10: slot #4: dtbo ‘cape-bone-2g-emmc1.dtbo’ loaded; converting to live tree
[ 0.760733] omap_hsmmc mmc.5: of_parse_phandle_with_args of ‘reset’ failed
[ 0.767954] omap_hsmmc mmc.5: Failed to get rstctl; not using any
[ 0.768646] mmc.5 supply vmmc_aux not found, using dummy regulator
[ 0.769069] omap_hsmmc mmc.5: pins are not configured from the driver
[ 0.796288] omap_hsmmc mmc.6: Got rstctl (gpio:#0 name eMMC_RSTn) label:eMMC_RSTn
[ 0.796893] mmc.6 supply vmmc_aux not found, using dummy regulator
[ 0.796961] omap_hsmmc mmc.6: pins are not configured from the driver
[ 0.907797] mmc1: BKOPS_EN bit is not set
[ 0.911646] mmc1: new high speed MMC card at address 0001
[ 0.912179] mmcblk0: mmc1:0001 MK2704 3.53 GiB
[ 0.912406] mmcblk0boot0: mmc1:0001 MK2704 partition 1 2.00 MiB
[ 0.912598] mmcblk0boot1: mmc1:0001 MK2704 partition 2 2.00 MiB
[ 0.913832] mmcblk0: p1 p2
[ 0.916330] mmcblk0boot1: unknown partition table
[ 0.918354] mmcblk0boot0: unknown partition table
[ 2.308240] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 4.318205] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro
[ 9.257209] lun0: LUN: removable file: /dev/mmcblk0
[ 13.518341] lun0: LUN: removable file: /dev/mmcblk0
root@beaglebone:~#
root@beaglebone:~# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 3.4G 2.0G 1.3G 61% /
udev 10M 0 10M 0% /dev
tmpfs 100M 616K 99M 1% /run
/dev/disk/by-uuid/8a679461-43b8-4028-99d0-3c2d05b6a343 3.4G 2.0G 1.3G 61% /
tmpfs 249M 0 249M 0% /dev/shm
tmpfs 249M 0 249M 0% /sys/fs/cgroup
tmpfs 100M 0 100M 0% /run/user
tmpfs 5.0M 0 5.0M 0% /run/lock
/dev/mmcblk0p1 96M 47M 49M 49% /media/BEAGLEBONE
root@beaglebone:~# fdisk -l

Disk /dev/mmcblk0: 3791 MB, 3791650816 bytes
4 heads, 16 sectors/track, 115712 cylinders, total 7405568 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x1f5e84ca

Device Boot Start End Blocks Id System
/dev/mmcblk0p1 * 2048 198655 98304 e W95 FAT16 (LBA)
/dev/mmcblk0p2 198656 7405567 3603456 83 Linux

Disk /dev/mmcblk0boot1: 2 MB, 2097152 bytes
4 heads, 16 sectors/track, 64 cylinders, total 4096 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Just for context, 3.8.13-bone84 was tagged/released on 2017-02-13… 3.8.13 itself was tagged on 2013-05-11

The sdhci/mmc/microSD spec has seen a ton of changes.

The Linux Kernel sdhci driver has had a ton of changes…

It’s 2024, so either find ancient microSD cards or time to finaly upgrade…

(i’m not touching 3.8.13)…

Regards,

It is probably a hardware issue and not a software issue. I tried to upgrade our project by downloading am335x-debian-11.7-iot-armhf-2023-09-02-4gb.img, but we experienced the exact same behavior. After hours of probing, I realized that the mmc0_cd does not behave as expected. We tried to force it to GND for one second, and the SD card became detectable. Thanks for your time.

update: mmc0_cd was not properly soldered in the latest batch. The issue was fixed by reflow the SD card slot