s905x box can't see emmc

[Тарас Артюшенко]

Hi
I have x96 box with s905x cpu, a long time ago i flashed it with libreelec and it was running from emmc only without a problem.
Now flashed armbian to emmc but bootloader works only from usb or sdcard (cannot see mmc). Tried images s905x and s905x-t95 - same result.

Is this a result of some misconfiguration/image selection or ..?

Currently using sdcard for boot partition only as workaround.

[Teh Scuddles]

hello, I have ran into this issue recently with two different X96 mini boxes. One box which had a 8GB Samsung KLM8G1GEME-B041 NAND chip which worked fine, the other box's had a 16GB SK hynix H26M52103FMR and it failed to mount as eMMC.

I investigated both chips and it turns out KLM8G1GEME-B041 supports HS200 bus speed mode, but H26M52103FMR does not. I found in the the .dtb file I was using it will try to use HS200 mode. So I decompiled the .dtb file and commented out the HS200 bus speed line in mmc and it successfully mounted as eMMC afterwards.

			mmc@74000 {
				compatible = "amlogic,meson-gx-mmc\0amlogic,meson-gxbb-mmc";
				reg = <0x00 0x74000 0x00 0x800>;
				interrupts = <0x00 0xda 0x04>;
				status = "okay";
				clocks = <0x03 0x60 0x03 0x7d 0x03 0x04>;
				clock-names = "core\0clkin0\0clkin1";
				resets = <0x11 0x2e>;
				pinctrl-0 = <0x29 0x2a>;
				pinctrl-1 = <0x2b>;
				pinctrl-names = "default\0clk-gate";
				bus-width = <0x08>;
				cap-mmc-highspeed;
				max-frequency = <0xbebc200>;
				non-removable;
				disable-wp;
				mmc-ddr-1_8v;
				//mmc-hs200-1_8v; // <- Comment out this line
				mmc-pwrseq = <0x2c>;
				vmmc-supply = <0x2d>;
				vqmmc-supply = <0x25>;
				phandle = <0xa0>;
			};

That worked for me, so I'm submitting this finding to give back as I have had relied on community help trying to get started.

But I really don't want to get any further into TV boxes, this is once again yet another problem caused by cost cutting measures of manufacturing cheap TV boxes and there will only be more problems trying to get further.

[SteeMan]

Thanks for investigating this.  I have seen this issue reported quite a bit recently.  I assumed it was something that had changed at the dtb level.  Knowing this helps provide guidance to others in the same situation.