Hi,
I followed the instructions in this forum thread - viewtopic.php?t=302634&sid=d30bb238b83d ... b&start=25 to add a sd card to the CM4 using the GPIO pins 22-27 with a custom DTS overlay.
I am using a CM4 module with eMMC and WiFi. OS is the latest Raspberry Pi OS, bullseye 64 bit flashed last month (April 2024) and I have updated the boot loader to pieeprom-2024-04-15.bin.
I compiled the custom DTS overlay from Lauszus (see thread link above) after writing the sd0-overlay.dts file and runningThis should set the GPIO pin 22-27 to SD0 alt and set the pull-ups. I have appended the following line to the bottom of /firmware/boot/config.txt The SD card can be seen by the cm4 but the partitions cannot. I have formatted the relevant SD card as Fat32 with partition scheme GUID (using disk utility Mac).
I have then tried to mount/ check for errors on the SD card on the cm4 but this fails. The card works fine on my Mac.
Does anyone have any ideas why this might be? I have triple checked the wiring.
I followed the instructions in this forum thread - viewtopic.php?t=302634&sid=d30bb238b83d ... b&start=25 to add a sd card to the CM4 using the GPIO pins 22-27 with a custom DTS overlay.
I am using a CM4 module with eMMC and WiFi. OS is the latest Raspberry Pi OS, bullseye 64 bit flashed last month (April 2024) and I have updated the boot loader to pieeprom-2024-04-15.bin.
I compiled the custom DTS overlay from Lauszus (see thread link above) after writing the sd0-overlay.dts file and running
Code:
sudo dtc -@ -I dts -O dtb -o /boot/overlays/sd0.dtbo sd0-overlay.dts
Code:
dtoverlay=sd0,overclock_50=10
Code:
$ # raspi-gpio get 22-27GPIO 22: level=0 alt=0 func=SD0_CLK pull=NONEGPIO 23: level=1 alt=0 func=SD0_CMD pull=UPGPIO 24: level=1 alt=0 func=SD0_DAT0 pull=UPGPIO 25: level=1 alt=0 func=SD0_DAT1 pull=UPGPIO 26: level=1 alt=0 func=SD0_DAT2 pull=UPGPIO 27: level=1 alt=0 func=SD0_DAT3 pull=UP
Code:
pi@cm4:~ $ lsblkNAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTSmmcblk0 179:0 0 7.3G 0 disk ├─mmcblk0p1 179:1 0 512M 0 part /boot/firmware└─mmcblk0p2 179:2 0 6.8G 0 part /mmcblk2 179:32 0 14.8G 0 disk mmcblk0boot0 179:64 0 4M 1 disk mmcblk0boot1 179:96 0 4M 1 disk
Code:
pi@cm4:~ $ dmesg | grep mmcblk[ 2.219819] mmcblk0: mmc0:0001 8GTF4R 7.28 GiB[ 2.240172] mmcblk0: p1 p2[ 2.273538] mmcblk0: mmc0:0001 8GTF4R 7.28 GiB[ 2.333643] mmcblk0boot0: mmc0:0001 8GTF4R 4.00 MiB[ 2.367908] mmcblk0boot1: mmc0:0001 8GTF4R 4.00 MiB[ 2.371934] mmcblk2: mmc2:aaaa SC16G 14.8 GiB[ 2.377356] mmcblk0rpmb: mmc0:0001 8GTF4R 512 KiB, chardev (243:0)[ 2.393011] mmcblk2: mmc2:aaaa SC16G 14.8 GiB (quirks 0x00004000)[ 4.934665] EXT4-fs (mmcblk0p2): mounted filesystem 93c89e92-8f2e-4522-ad32-68faed883d2f ro with ordered data mode. Quota mode: none.[ 6.833568] EXT4-fs (mmcblk0p2): re-mounted 93c89e92-8f2e-4522-ad32-68faed883d2f r/w. Quota mode: none.[ 50.989722] /dev/mmcblk2p1: Can't lookup blockdev
Code:
pi@cm4:~ $ sudo fsck /dev/mmcblk2p1fsck from util-linux 2.38.1e2fsck 1.47.0 (5-Feb-2023)fsck.ext2: No such file or directory while trying to open /dev/mmcblk2p1Possibly non-existent device?
Statistics: Posted by tennisparty — Sun May 05, 2024 6:57 am