Posts by dtech

The WeTek_Core project has been re-designed based on the S8X2 project.

• The kernel has been replaced from the official (LE) to the kszaq-based,
• Some disabled things have been enabled in kernel (e.g. CPU temperature, watchdog timer, etc.),
• The HDMI-CEC now works properly,
• Resolution whitelist and 4K patches applied,
• The u-boot-tools-aml package added to image (fw_printenv, fw_setenv),
• Audio output configuration changed (based on S8X2).

Primary download link: Index of /WeTek_Core/

Mirror (GitHub): Release LibreELEC v9.2.8.2 for WeTek Core only (2021-09-24) · dtechsrv/LibreELEC-AML · GitHub

Unfortunately, after building the image, my own Core device died. It worked for about 2 days, but the BGA soldering of the SoC was factory defective. When the heat sink was removed, the PCB was permanently damaged (the copper foil was broken at several points), so unfortunately it is no longer repairable. (It's a little funny, but most sad, that the thermally conductive adhesive was stronger than soldering.)

If anyone knows where I can get another one in Europe at a reasonable price, please contact me in a conversation.

Thanks in advance.

Quote from ochentay4

Will do the following if ok, will reflash original Tronsmart ROM, and use a new 32GB SD Card so I can send you dmesg again. Is this good?

Absolutely, it sounds perfect. I'm waiting for your results.

Quote from kodlz

dtech thank you. .nocompat help me with updating.

Great, I'm waiting for the results from you too.

ochentay4

[    1.813044@0] ethernet base addr is fe0c0000
[    1.847191@0] stmmac - user ID: 0x10, Synopsys ID: 0x33
[    1.852354@0]  Normal descriptors
[    1.855655@0]  Ring mode enabled
[    1.858857@0]  No HW DMA feature register supported
[    1.863541@0]  Wake-Up On Lan supported
[    1.887259@0] libphy: stmmac: probed
[    1.887291@0] eth%d: PHY ID 02430c54 at 0 IRQ POLL (stmmac-0:00) active
[   44.808738@1] eth0: device MAC address 00:01:23:cd:ee:af

This is seemingly good, which unfortunately does not mean good. (Well, that sounds like a pretty paradox.)

I have to ask if the device had the factory Android ROM on it, or is it possible that you crossflashed with the ROM of a similar device, such as the original (non-Tronsmart) MXIII or the ROM of another MXIII clone.

Unfortunately, this is an important question because I can't find any errors based on the kernel log, but this symptom you report usually occurs when it doesn't have the factory uboot bootloader on the device.

Another thing: based on the log, it seems that either the SD card or the slot is problematic because there are a lot of I/O errors:

[    4.791202@2] mmcblk0: r/w command failed, status = 0x80000b00
[    4.791224@2] end_request: I/O error, dev mmcblk0, sector 3887096
[    4.791235@2] Buffer I/O error on device mmcblk0, logical block 485887
[    4.792048@2] mmcblk0: r/w command failed, status = 0x80000b00
[    4.792065@2] mmc_blk_reset 939 reset error md->reset_done:1 and type:1
[    4.792074@2] end_request: I/O error, dev mmcblk0, sector 3887096
[    4.792083@2] Buffer I/O error on device mmcblk0, logical block 485887
[    4.898018@2] mmcblk0: r/w command failed, status = 0x80000b00
[    4.898043@2] end_request: I/O error, dev mmcblk0, sector 3887096
[    4.898056@2] Buffer I/O error on device mmcblk0p2, logical block 353791
[    4.898883@2] mmcblk0: r/w command failed, status = 0x80000b00
[    4.898900@2] mmc_blk_reset 939 reset error md->reset_done:1 and type:1
[    4.898910@2] end_request: I/O error, dev mmcblk0, sector 3887096
[    4.898920@2] Buffer I/O error on device mmcblk0p2, logical block 353791
[    5.389003@0] mmcblk0: r/w command failed, status = 0x80000b00
[    5.389027@0] end_request: I/O error, dev mmcblk0, sector 3887096
[    5.389039@0] Buffer I/O error on device mmcblk0, logical block 485887
[    5.389856@0] mmcblk0: r/w command failed, status = 0x80000b00
[    5.389873@0] mmc_blk_reset 939 reset error md->reset_done:1 and type:1
[    5.389883@0] end_request: I/O error, dev mmcblk0, sector 3887096
[    5.389892@0] Buffer I/O error on device mmcblk0, logical block 485887
...

If the system is already running from internal memory, it is irrelevant, but this log is apparently still made from the SD card.

Quote from ochentay4

Here it is. Tronsmart MXIII / S802 / 2G RAM / 8GB ROM / AP 6330

Thanks, I will check it soon.

Quote from kodlz

Any idea how to update it?

Check it on an SD card first, and only do the update if it works without error.

Because the project name is different (X8H-Plus), you need to create an empty .nocompat file next to .tar in the update directory.

Quote from loki7777

Start reading from this post or few posts above as well RE: LE-9.2.8 builds for some Amlogic S905x, S802/S812 and S805 devices

I didn't try ethernet but will try it today as we are using the same image on similar box.

Your boxes are quite different. For example, your box was equipped with Gigabit Ethernet (Realtek RTL8211F), not 10/100 Mbps.

On the other hand, your box has an S812 SoC and ochentay4 's box has an S802 only.

But nonetheless, I am happy to accept the result from both.

Quote from ochentay4

Ok, image seems to work nicely on Netxeon M82_V4.0_20141106 device (Tronsmart MXIII 2G/8GB Wifi 6330). Wifi worked correctly, funny enough, ethernet did not, cant get ip from DHCP (triple checked connections). Ethernet chip is H1601NL (1502-XG). Any fix you can think of?

I also managed to installtointernal, I like it. If I could get ethernet working Im golden.

H1601NL -> It's just a transformer, your Ethernet chip is actually an IC+ IP101GR.

It is located under the quartz behind your lower USB port.

I need a dmesg.

jim_p

It's good that you're asking me these, but I'm reassuring you, I didn't eat the free space.

The schema of the partitions on the internal NAND/eMMC follows Android, which splits the flash into quite a few pieces.

There are a lot of partitons on it that are unnecessary for LE, or have no file system, just raw data (eg. kernel -> /dev/boot).

But the same is true for bootloader, dtb, recovery, cache, etc.

For example: /dev/system also varies in size for some boxes, in your case ~1GB, but here it usually only contains the SYSTEM (squashfs) file, which is 120-150 MB in size and is basically a non-writable partition.

But on a USB flash drive or an SD card, it’s completely different, so it’s like comparing an apple to a pear.

There are two partitions, one for boot files (kernel, squashfs) and one for data. And that's the story.

Quote from loki7777

Honestly if that would be slowly the end of does devices i would be still more then happy by what you achieved and what i have now installed on my box. While i was running kodi 15 for last few years i might as well run kodi 18.9 for another 3 years(as only using it for playing 1080p files and now maybe even x256 (maybe even in 4k). So i'm good with that. And then i will buy a newer box or something else to use LE.

THANK YOU.

No, I would like to thank you and wish you enjoyable and trouble-free use.

Quote from ochentay4

Hi, love this project. Is Tronsmart MXIII 2GB/8GB (K200) going to be supported anytime soon?

Experience shows that the n200 image is also perfect for k200 devices. Do you know what kind of wifi chip is in your box?

Quote from Jerry

I can't get ffmpeg to work with this addon,

it works on CE, Windows, Linux,

i tried
and,

possibly the builds are incompatible with the kernel of this system

I don't know much about it, but since it works on S905 + processors
then I have to look for some very old version of ffmpeg 

The problem is, I don’t even know if it worked with earlier versions under 3.10/3.14 kernel or not.

Unfortunately, the addon problems are in the same hat as the docker. I have neither the time nor the opportunity to investigate very much.

In the background, I'm also trying to bring back amcodec support to the Kodi Matrix version so that older devices can be used with the older kernel for at least some time. But I can't really move forward with that either.

Apparently, I was left alone for this, because the previous developers had already got out of this "suffering" since LE version 8.2 or 9.0 (kszaq, Demetris, datrh, etc.). Unfortunately, I’m starting to realize that the Amlogic v3.10/3.14 kernels are slowly no longer compatible with anything new.

Quote from loki7777

I can try it but first how to go back to boot from external?

fw_setenv bootcmd 'run startfromext; run storeboot'

Or use the toothpick method again. Both will end up with the same result.

Quote from loki7777

To my surprise this time it booted instantly from flash:)

But... there is always but when external hdd not connected - otherwise is a long boot.

Unfortunately, if a storage device is connected to an external USB (external HDD, flash drive, etc.), it would try to boot from there first.

If you need to ignore startfromext, you need to set this:

fw_setenv bootcmd run storeboot

And then reboot. If all goes well, it will no longer try to boot from an exernal device (not even an SD card).

Quote from huynhdat

please help libreelec for this m8s working box.

Next time please use a translator because the only accepted language on the forum is English.

Thread

Legacy v9.2 (LTS) builds for Amlogic S805/S8X2, S905/S912 and all WeTek boxes

Latest version: LibreELEC 9.2.8.17 (Release date: 2025-02-19)

IMPORTANT NOTICE!

Due to the switch to GLIBC v2.34, all binary addons have been rebuilt. The main version of the add-ons has been changed from v9.2.0 to v9.2.1, so after the system update, the binary add-ons will also be updated. In addition, the default transfer protocol in the repository has also changed from HTTP to HTTPS.

NOTICE: If the auto update is enabled, but the installed version is not the latest, then the supported devices…

dtech

February 7, 2021 at 2:33 PM

Unfortunately, I don’t see exactly the type of wifi chip on your photo, but basically one of two images can be good:

• Universal n200: Ampak AP6330 or Realtek wifi,
• OTT M8S+ (n200C): multiple broadcom/ampak wifi.

Please try them out and report back in the linked topic.

I need some enterprising Minix X8 / X8-H / X8-H Plus testers in this topic:

Post

RE: Legacy v9.2 (LTS) builds for Amlogic S805/S8X2, S905/S912 and all WeTek boxes

LibreELEC v9.2.8.2 (2021-09-12) has been released for S8X2 devices only.

---

Changes since v9.2.8.1 (2021-08-14):

• restore whitelist patch to fix cadence-correct playback problems (eg. 23.976 and 29.97 fps),
• disable all Realtek SDIO and USB wifi/bluetooth adapter drivers in kernel configuration,
• M8S-Plus: enable some external Realtek USB wifi adapter drivers.
• 3rdParty images: enable some updated external Realtek SDIO and USB wifi/bluetooth adapter drivers in options,
• 3rdParty images: merge MXIII-S8X2

…

dtech

September 13, 2021 at 8:58 AM

Quote from loki7777

You are right. How to check flash size then?

Well, the easiest way to really do this is to type the ID at the top of the chip into a search engine.

This really matters if you run from there. (E.g. if it is installed to the internal memory with installtointernal script.)

This is my M8S (n200C), LE runs from the internal NAND:

Filesystem                Size      Used Available Use% Mounted on
devtmpfs                766.4M      4.0K    766.4M   0% /dev
/dev/system             975.9M    124.1M    835.8M  13% /flash
/dev/loop0              122.0M    122.0M         0 100% /
/dev/data                 5.3G      1.3G      3.9G  25% /storage
tmpfs                   768.4M         0    768.4M   0% /dev/shm
tmpfs                   768.4M      9.1M    759.2M   1% /run
tmpfs                   768.4M         0    768.4M   0% /sys/fs/cgroup
tmpfs                   768.4M      2.2M    766.2M   0% /var
tmpfs                   768.4M         0    768.4M   0% /tmp

/dev/mmcblk0p1 511.7M 134.2M 377.6M 26% /flash
/dev/mmcblk0p2 13.9G 288.0M 13.6G 2% /storage

This is not your SD card?

Quote from loki7777

Can't access this file (repository.libreelec.tv-9.2.1.zip) on your server.

Sorry, the link has been link fixed. There is no SSL certificate for this subdomain on my server, so the HTTPS is not valid in the URL.

But this stupid Crome found it funny to add that idiot s to http. No comment...

Quote from loki7777

BTW That's my box mainboard in attachment - it shows tronsmart on sticker and 8gb but it is 16gb.

NCEFAT28-08G -> It is interesting because this is a 8GB eMMC on your PCB.

Okay, the manual workaround is here for the "repo bug after update":

(However, as a new installation, everything will work immediately, and there is no need for manual intervention.)

Quote from dtech

IMPORTANT!

If you installed it as an update and you have a problem installing addons, you will need to manually update the LE repository addon:

repository.libreelec.tv-9.2.1.zip

For v9.2.8.1 and earlier versions I also replaced the old repo, and the only package included is this:

After that you just need to update and point to the location of the new repo (S8X2):

Quote from loki7777

I wouldn't bother with that bug too much(tbh i downloaded only one add-on from repo and it is a skin;) - just add in first post that "users have to do a fresh install every time new build is released" and wait for LE to fix it.

This is a "catch-22" situation: If LE fix this bug, how do you install it if you don't reach the repo itself?

I'm trying to find a bridging solution...