11-17-2020, 06:11 PM
(11-14-2020, 05:07 PM)poVoq Wrote: Funny, with the old 16gb emmc from Odroid, it also doesn't work, but it seems to fall back to the "drr" mode even on system images without the above mentioned software fix applied. So there I get the above new dmesg error message on stock sopine64 armbian images.
Edit: -110 seems to indicate a time-out error...
it very well could be cluster board version, im on 2.3
interestingly enough my 128gb also says A64-DB-E MMC-v1_0 on the back, which i guess is just for the interposer board from the emmc to the connector on the cluster board.
i dont think it would have anything to do with the board version however, since the traces would stay the same as would the chip.
have you check the DTS config for mmc2? this is likely where the issue is, heres some cli to convert it if that helps:
sudo dtc -I dtb -O dts -o /tmp/temp.dts /usr/lib/linux-image-current-sunxi64/allwinner/sun50i-a64-sopine-baseboard.dtb
then just put it in vim and you can read the output, were looking for anything relating to mmc2 as thats whats controlling the gpio for it, as well as what does the init process, mine is /soc/mmc@1c11000.
i can also share my DTS file with you if that helps
here is my DMESG init of the mmc:
Code:
[ 2.603079] mmc2: mmc_select_hs200 failed, error -74
Code:
[ 2.658828] mmc2: new MMC card at address 0001
Code:
[ 2.660156] mmcblk2: mmc2:0001 DA4128 116 GiB
Code:
[ 2.660783] mmcblk2boot0: mmc2:0001 DA4128 partition 1 4.00 MiB
Code:
[ 2.661428] mmcblk2boot1: mmc2:0001 DA4128 partition 2 4.00 MiB