Posts by Zameero

Quote from chewitt

"arm" is 64-bit kernel and 32-bit userspace for compatibilty with add-ons that need software widevine (DRM) support, and aarch64 is 64-bit kernel

If the add-on compatibility is not needed, is there any actual advantage/hindrance in using arm or aarch64 images? I recall reading balbes150 mentioning temperature, but maybe I'm having a Mandela effect... Does one perform better than the other?

Regarding memory this board is very strange: I'd think that boards with fake RAM would have less RAM (as in actual memory IC), and I've actually seen one of these: just 4 x 256MB installed became 2GB advertised.

But this one has the real deal (2x1GB + 2x512MB=3GB), however at boot only 2GB are recognized and then they are faked to 3GB.

DR4 chl: Rank0+1 @ 1008MHz - PASS
Rank0: 1024MB(auto)-2T-18
Rank1: 1024MB(auto)-2T-18
[...]
U-Boot 2015.01-ga4d8f5c-dirty (Dec 07 2017 - 19:23:54)
DRAM:  3 GiB

Quote from chewitt

You cannot "replace emmc with nand" on boxes

This board has provision for EMMC (BGA) or NAND (TSOP) memory, and I've seen similar (cheaper) boxes where they use NAND TSOP.

Quote from chewitt

you can replace the bootloader - if - you have the fip sources for the box

The problem is that the EMMC has a region that is write protected, so the bootloader CAN'T be overwritten. That's why I was looking to replace the chip with a NAND.

Have you got any info on how to disable the write protection on the EMMC? Maybe there's some u-boot command that can do that?

On an S912 is it possible to get analog audio?

Also I tried LibreELEC-ARM-ALL.arm-9.80-devel-20200406105758.... image on my S10 but when I do:

Quote

LibreELEC:~ # uname -m

aarch64

So what's the difference between arm and aarch64 images?

One more question: The S10 has some weird bootloader that fakes the amount of RAM, apparently it's impossible to replace it because there's some security mechanism or encryption in the image or the EMMC.

If I remove the EMMC and replaced it with a NAND, can I then upload (via burning tool) an image with a "normal" bootloader?

Or is the fake bootloader somehow locked in by in the CPU EFUSEs?

Quote from balbes150

If you are a LE developer, email me at Slake in PM, I will explain in detail how to do this.

I can barely compile a Makefile, so I don't think I qualify.

But there's something else I'd like to ask you:

As I already written, only your Armbian/Libreelec images work on the R-TV S10. Is it possible to apply your "magic" to a foreign .img and cook a bootable image?

Software decoding is enough for 1080p media, but not for anything higher.

The dtb from the Khadas Vim 2 works fine.

I have an R-TV S10 (aml912 3GB 2GB/32GB) box and nothing works on it except for balbes150 images, so thanks for that!

However I'd like to use it as a LibreELEC dedicated machine and while the newer images work (sorta), I'd like to have an older build installed, since the test versions aren't really usable (missing HW decode and too new for my old skin/addons).

balbes150 , is there some place where one can download your older builds, those where the HW acceleration wasn't broken?

Alternatively, is it possible to build from source an Image that works with your boot system? I've tried to look into it, but the guides are outdated and the required files aren't there anymore.