TF card not working

ROCK 3 Series CM3
1

I have loaded the firmware with through RKDevtool,
After loading the firmware i want to access external sd card.

So when I connect with radxa CM3 IO board, its detecting the TF card.

image
image463×182 4.69 KB

but when I connected to waveshare board.
i am using this board

and its not able to detect the TF card.
As it seems like we have to enable SDMMC0_PWREN.

image
image435×151 4.23 KB

any ideas how to enable this, so that i can able to mount my sd card.

Thanks

2

Do you insert the TF card before the system booting up ?
CM3 doesn’t support dynamic detection of the SDcard after the system boots up on RPI CM4 IO board.

3

yes i did, and still the same not finding it.

4

as I am using waveshare board and not the radxa IO board.
I want to get working with waveshare board.

5

Please use this image to try
https://github.com/radxa-build/radxa-cm3-rpi-cm4-io/releases/download/b15/radxa-cm3-rpi-cm4-io_debian_bullseye_kde_b15.img.xz

6

The Raspberry Pi CM4 IO board, and the other fork of the CM4 IO board design, don’t have the sd_detect signal, so the SD card must persist before power on.

When working with Radxa CM3, it’s a headache for us, we need to support SD card hotplug on regular condition(Radxa CM3 IO board), we also have to support these none sd_detect IO boards.

7

tried but didnt worked and the same thing, and i have connected the sd card before powered on and still the same thing now and after.

8

Tried connecting the sd card before powering on and still not able to detect it, but it detects in CM3 IO board but not on waveshare board.

Could you help in how to detect in waveshare board aswell.

The below is the board i am using for it now
https://www.waveshare.com/cm4-to-pi4-adapter.htm

9

I recommend you to try the following, after backing up the relevant files according to your needs.

1) Specify 'dtb file' directly.

/boot/extlinux/extlinux.conf # (‘b15’)

## /boot/extlinux/extlinux.conf
##
...
label l0
        menu label Debian GNU/Linux 11 (bullseye) 5.10.160-19-rk356x
        linux /boot/vmlinuz-5.10.160-19-rk356x
        initrd /boot/initrd.img-5.10.160-19-rk356x
#       fdtdir /usr/lib/linux-image-5.10.160-19-rk356x/
        fdt    /usr/lib/linux-image-5.10.160-19-rk356x/rockchip/rk3566-radxa-cm3-rpi-cm4-io.dtb
...
label l0r
        menu label Debian GNU/Linux 11 (bullseye) 5.10.160-19-rk356x (rescue target)
        linux /boot/vmlinuz-5.10.160-19-rk356x
        initrd /boot/initrd.img-5.10.160-19-rk356x
#       fdtdir /usr/lib/linux-image-5.10.160-19-rk356x/
        fdt    /usr/lib/linux-image-5.10.160-19-rk356x/rockchip/rk3566-radxa-cm3-rpi-cm4-io.dtb
...

or
2) Replace ‘dtb file’

# cp -av /usr/lib/linux-image-5.10.160-19-rk356x/rockchip/rk3566-radxa-cm3-rpi-cm4-io.dtb /usr/lib/linux-image-5.10.160-19-rk356x/rockchip/rk3566-radxa-cm3-io.dtb

The above example is for ‘b15’, but the operation method is the same for ‘b25’, only the version number is different.
b15: ‘5.10.160-19-rk356x’
b25: ‘5.10.160-18-rk356x’

Also, you should know that the above changes will be rewritten if you update the kernel.
For example, ‘apt upgrade’ or ‘rsetup’ … etc.

10

Thanks for the info,

I will give a try once, hope this should not be facing issues. lol…

Thanks