It’s going to fail, I’m afraid. It’ll probably work with Radxa image, but the speed will be limited.
5A corrupts eMMC (was 5A does not boot)
1 Like
After more testing we found that if we bump eMMC voltage from 1.8V to 1.825V we can have HS400 working with Samsung eMMC module on ROCK 5A.
We will check if this is with-in specs with Rockchip before rolling this change out.
Update: another fix was discovered without the need to increase voltage.
BTW: It seems that I have the same problem with the SPINOR at the EMMC socket. When I try to write it, thw write operation “hangs”, and no data is written.
What’s the other fix?
The other fix disabled HS400ES:
&sdhci {
bus-width = <8>;
no-sdio;
no-sd;
non-removable;
max-frequency = <200000000>;
mmc-hs400-1_8v;
/delete-property/ mmc-hs400-enhanced-strobe;
pinctrl-names = "default";
pinctrl-0 = <&emmc_rstnout &emmc_bus8 &emmc_clk &emmc_cmd>;
//pinctrl-0 = <&emmc_rstnout &emmc_bus8 &emmc_clk &emmc_cmd &emmc_data_strobe>;
status = "okay";
};
I think this information is already unnecessary. I was able to confirm that the following image works in one way.
Ubuntu booting, GPU, HDIMI sound output, etc.
I think this image worked most correctly, although it is a third party.
After some more testing the above 2 fixes can’t fix all HS400 issues. We will keep the HS200 workaround.
2 Likes
I have the same issue. Tried 32gb and 64gb card with no luck including the image above. What’s the current solution for using EMMC?
As an update, Orange Pi eMMC 256GB module FEMDNN256G-A3A56 works just fine, and is cheap as hell.
3 Likes
iNAND CHINA SDINBDV4-256G (same capacity, bought from Orange pi) - so far works well with Armbian on 5a
I’ve been watching this issue for a long time.
When do you think you will be able to resolve it?
I think this is the solution. You might add an overlay that sets the speed to HS400 for “known good” EMMCs, but I doubt something better will be found (except a new HW revision maybe).
One way to “fix” it is to use Orange Pi eMMC modules instead of the ones sold at AllNet China (Samsung ones, to be specific). These are dirt-cheap and have no issues with 5A and HS400ES.
We just created a RC build for ROCK 5A which contains the HS200 fix. We should have an official release soon.
I think this is something we could do but probably in a future release.
Is it possible for Orange pi emmc to work with Rock 5A after writing the image with emmc witer purchased from allnet china?
If it is possible, I will give it a try.
the connector should work in the same way on the rock and on the eMMC writer
Just to add data to the pile, I got a 5A yesterday, and tried it with a 64GB module from Hardkernel that I got with an Odroid-N2 a while ago. With the Radxa b16 image I get a steady stream of errors on any attempted write.This module is a KLMCG4JETD-B041.
As expected, Armbian works just fine. I installed from the 23.5.4 Jammy Legacy image linked from Armbian’s rock5b page. The userland has upgraded to 23.08.0-trunk Jammy but the kernel is still 5.10.160-rk35xx
I have an OrangePi module coming (thanks for the tip on the cheap 256GB!) as well as a 64GB from Allnet and will report back on those.
Given that Radxa’s solution for their builds appears to be slowing down to HS200, I guess I’ll stick with Armbian.
2 Likes
I also have this problem. I wrote Armbian_23.5.4_Rock-5a_bookworm_legacy_5.10.160_minimal.img to the 16GB emmc I bought together with the Rock 5A from allnetchina, using the USB emmc writer also from allnetchina.
It boots up and I can ssh in and perform the first configuration steps. I have tried from the initial Armbian image three times now. It always ends up with block I/O errors within 5-15 minutes. I even managed to do the first apt update/dist-upgrade once. But eventually after too many write operations the I/O errors show up.
Is there a workaround/solution? Thanks.
# dmesg | grep -i mmc
[ 8.667384] dwmmc_rockchip fe2c0000.mmc: IDMAC supports 32-bit address mode.
[ 8.667406] dwmmc_rockchip fe2c0000.mmc: Using internal DMA controller.
[ 8.667417] dwmmc_rockchip fe2c0000.mmc: Version ID is 270a
[ 8.667469] dwmmc_rockchip fe2c0000.mmc: DW MMC controller at irq 77,32 bit host data width,256 deep fifo
[ 8.667562] dwmmc_rockchip fe2c0000.mmc: Looking up vmmc-supply from device tree
[ 8.670355] sdhci-dwcmshc fe2e0000.mmc: Looking up vmmc-supply from device tree
[ 8.670376] sdhci-dwcmshc fe2e0000.mmc: Looking up vmmc-supply property in node /mmc@fe2e0000 failed
[ 8.672722] sdhci-dwcmshc fe2e0000.mmc: Looking up vqmmc-supply from device tree
[ 8.672741] sdhci-dwcmshc fe2e0000.mmc: Looking up vqmmc-supply property in node /mmc@fe2e0000 failed
[ 8.673116] dwmmc_rockchip fe2c0000.mmc: Looking up vqmmc-supply from device tree
[ 8.688728] mmc_host mmc1: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
[ 8.704207] mmc0: SDHCI controller on fe2e0000.mmc [fe2e0000.mmc] using ADMA
[ 8.742961] mmc0: Host Software Queue enabled
[ 8.742988] mmc0: new HS400 Enhanced strobe MMC card at address 0001
[ 8.744191] mmcblk0: mmc0:0001 AJTD4R 14.6 GiB
[ 8.744619] mmcblk0boot0: mmc0:0001 AJTD4R partition 1 4.00 MiB
[ 8.745064] mmcblk0boot1: mmc0:0001 AJTD4R partition 2 4.00 MiB
[ 8.745384] mmcblk0rpmb: mmc0:0001 AJTD4R partition 3 4.00 MiB, chardev (237:0)
[ 8.750791] mmcblk0: p1
[ 9.325467] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null)
[ 10.049354] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,errors=remount-ro
[ 13.060354] blk_update_request: I/O error, dev mmcblk0, sector 2708872 op 0x1:(WRITE) flags 0x4800 phys_seg 7 prio class 0
[ 13.060374] EXT4-fs warning (device mmcblk0p1): ext4_end_bio:347: I/O error 10 writing to inode 2180 starting block 338687)
[ 13.060388] Buffer I/O error on device mmcblk0p1, logical block 334513
[ 13.060428] Buffer I/O error on device mmcblk0p1, logical block 334514
[ 13.060436] Buffer I/O error on device mmcblk0p1, logical block 334515
[ 13.060441] Buffer I/O error on device mmcblk0p1, logical block 334516
[ 13.060447] Buffer I/O error on device mmcblk0p1, logical block 334517
[ 13.060455] Buffer I/O error on device mmcblk0p1, logical block 334518
[ 13.060461] Buffer I/O error on device mmcblk0p1, logical block 334519
[ 13.060465] Buffer I/O error on device mmcblk0p1, logical block 334520
[ 13.060470] Buffer I/O error on device mmcblk0p1, logical block 334521
[ 13.060475] Buffer I/O error on device mmcblk0p1, logical block 334522There’s an RC build a few posts up that slows down the MMC to HS200 to make it work. Or you could run Armbian, which doesn’t seem to have this problem.
1 Like