Posts by qUE_ARM

    If the board/chipset is the same it may work, but the problem you have is the supporting peripheral chips like wired and wireless networking may be different, so you'll find those functions not working.

    The box I have was an Android box and has an MX logo on the top, but I'm using MX2 firmware.

    I'm not sure the boot process supports USB booting, SD booting is definitely supported, but like I said the modifications (based on work in this thread) I've made to get LibreElec-AML working do not touch the SD booting side and it'll likely still truncate the kernel binary load and then fail to boot.

    Afaik, none of the images on this thread modify the u-boot bootloader, so theoretically you'll be safe from bricking the box. It's only if you run an official MX/MX2 bootloader mod script it'll break u-boot (which I have done), but as long as you can access the "JTAG" serial console it is reversible. I would just stick to trying Libreelec images and seeing what boots.

    As long as you have the original firmware to roll back your box, it's worth trying images. Flashing the NAND (flash) isn't as destructive as I've heard several other places rant about. An SD will fail quicker than internal NAND, besides the NAND (flash) will get battered by any streaming you do anyway when it's used as cache by linux, so you have to accept it's wear either way.

    Greetings, I can’t apply the u-boot patch, can I somehow check whether it worked or not, is there another way to install the patch?

    Unfortunately there isn't a simple way to verify the patch has taken, it's a blind patch. The only way you can actually see the environment variables in u-boot is to solder to the jtag pads on the board and use a FTDI cable with a serial terminal utility like putty, at that point printenv lists the set environment at the prompt.

    TBH, if you have a working version of libreelec installed (i.e. 7.95), and the toothpick AV boot with SD inserted, arrives at the recovery, it means it's definitely booted from the SD and the patch should have applied.

    I should mention the next boot should a normal one, not another toothpick AV boot, otherwise you're just re-applying the patch.

    It's really important the environment is changed, it won't effect any older version from booting, but not applying it will prevent any newer builds working. It's a massive short sight of the stock firmware that OS kernel sizes wouldn't exceed 1MB.

    Little bit of detail on what is modified;

    The environment variable that is changed is 'nandboot'. Basically where it loads the kernel is changed to 'nand read boot \${loadaddr} 0 800000' in it's sub-script. As you can see 0x800000 = 8MB, where as that would've been 0x100000 before the patch.

    I would've added some kind of notice (text/screen) it's been applied if I could, but u-boot's capabilities are very very basic. So not possible.

    To re-iterate what needs to be done to patch, unpack aml_autoscript from aml_autoscript.zip to a blank SD and toothpick AV boot with the SD inserted in the STB.

    Edit: I should also note, this will only work for NAND booting, I've not messed about with the SD boot side as to be cautious not to mess that up.

    Thanks for your work. Unfortunately after applying this update using the .update folder method, my g18ref reboots into recovery.

    I was using the latest 9.0 devel, but the same thing happens when updating from LibreELEC-Amlogic_MX2.arm-8.0.2-update.zip

    The same thing also happens when following post #341 of reloading matricom_g18_1.2.zip, updating uboot, and loading LibreELEC-Amlogic_MX2.arm-7.95.3.zip, before updating to LibreELEC-Amlogic_MX2.arm-9.2.8.8-20230802.tar

    LibreELEC-Amlogic_MX2.arm-9.2.8.8-20230802.tar Doesn't seem to work for me. It extracts and installs fine, but wont boot into LibreElec, only recovery. Any ideas?

    I got it to boot by replacing KERNEL and KERNEL.md5 with ones from LibreELEC-Amlogic_MX2.arm-9.0-devel-20190424160004-aca1ab5.tar, but would prefer to use your kernel if possible

    Sounds like you need to apply the u-boot environment patch, the kernel load bit in the boot script will crop the binary being loaded into memory if the patch hasn't been applied. see this post; RE: [9.0.0] LibreELEC builds for MX2/G18

    Updated: 01/05/2023

    For those of us that have no choice but to use the older BBC iPlayer add-on, like in my case support for the Matricom MX2 box has been dropped post Kodi Leia. I have quick patched version 3.0.52 iPlayerWWW add-on to enable video listings again (I'm not sure if the audio side is broken I don't use it).

    I doubt this is any use to any of the main Kodi users as they'll all have cutting edge devices (and I CBA to sign up to their forum), which is why I've posted here and I'd thought I'd share.

    I am not affiliated with the official add-on maintainers and this does not bring all the new features which come with version 4.x. Also all credit goes to the maintainers for the fixes in the functions borrowed.

    This is simply a copy/replace of the functions ParseSingleJSON and ParseJSON in resources/lib/ipwww_video.py, in version 4 to 3.0.52, which appears to have gotten things rolling again.

    In Kodi; install from zip in the add-ons section. If you see no change you may need to uninstall the old add-on and install this one (note: uninstalling may remove your Kodi iPlayer favourites, so be mindful).

    Enjoy :)

    qUE

    LibreELEC-AML 9.2.8.8 (built 2nd March 2023) update for the Matricom G-Box MX/MX2 (AML8276-MX HD18 board)

    See post #341 for instructions on how to clean install, otherwise update as normal through copying to .update

    qUE_ARM
    January 23, 2023 at 7:29 PM

    Main fix I've added in this build is for the freezing on h264 (high) streams being interrupted by seeking or stop (which effects the Kodi BBC iPlayer add-on).

    Credit goes to dtech for maintaining and supporting this fork of LibreELEC.

    Update archive (copy to .update, as per instructions on first page);

    [link expired]

    Projects archive (for building LibreELEC-AML yourself, again see post #341);

    [link expired]


    Links will be solidified and updated once I've run it on my STB box for a while without issue, for now grab it while you can.

    qUE

    LibreELEC 9.2.8 didn't seem to fix the issue with certain streams crashing the Matricom MX set top box, so I decided to have a go at least finding a workaround and here it is.

    Extract this patch into the related Amlogic AM8726MX projects sub folder, i.e. projects/Amlogic_MX2.

    Clean the kodi folder from the build, i.e. PROJECT=Amlogic_MX2 ARCH=arm scripts/clean kodi

    Rebuild, i.e. PROJECT=Amlogic_MX2 ARCH=arm make amlpkg -j2

    This patch basically blocks h264 codec streams being processed by the amlogic hardware acceleration and causes kodi to fallback to software decoding. So expect HD content to struggle, but should be what's needed (for now) for things like BBC iPlayer.

    qUE

    This is intended for the Matricom G-Box MX/MX2 (HD18 board) boxes, trying this on other AML8276-MX systems YMMV.

    Clean factory restore

    Go to http://web.archive.org/web/2016010122…/i/MX2_Firmware and follow instructions for installing firmware 1.2

    This should clean up the u-boot environment incase it's not up to date.

    Install LibreELEC 7.95

    Download LibreELEC 7.95 found here in the first post, again extract to your SD and 'toothpick' AV port boot to install. Enable SSH.

    Patch U-Boot environment

    Download attachment aml_autoscript, extract to your SD and 'toothpick' AV port boot. Once the boot process arrives at the recovery 'reboot system now' screen just either select that option or power cycle the box.

    This is required to fix a bug in the U-Boot NAND booting to cope with up to 8MB Kernel binaries.

    Correct data partition disk label and copy update

    Download the LibreELEC 9.2.8 image archive found <updated> and copy to your SD, then put the SD in the MX set top box.

    (see post #344 for updated archive link; RE: [9.0.0] LibreELEC builds for MX2/G18)

    SSH into your MX set top box and use the commands;

    tune2fs -L LIBREELEC_DISK /dev/data

    cd /media/mmcblk*

    cp *.tar /storage/.update

    reboot

    Build LibreELEC-AML instructions

    This image of LibreELEC was built on a Wyse z90 with lubuntu 18.04.5 (64-bit). It takes around half a day to build and I think is a little bit quicker if you build on a drive other than the lubuntu system drive.

    Download the LibreELEC-AML_9.2.8_projects-Amlogic_MX2-20230123.tar.gz archive <updated> to your preferred EXT formatted build location.

    (see post #344 for updated archive link; RE: [9.0.0] LibreELEC builds for MX2/G18)

    In the terminal -

    Setup the build environment with the following commands;

    sudo apt-get update

    sudo apt-get install build-essential git

    sudo apt-get install gcc-multilib

    cd /media/<your preferred EXT formatted build location>

    git clone https://github.com/dtechsrv/LibreELEC-AML libreelec-AML

    cd libreelec-AML

    tar -xvf ../LibreELEC-AML_9.2.8_projects-Amlogic_MX2-20230123.tar.gz

    PROJECT=Amlogic_MX2 ARCH=arm make amlpkg -j2

    Ignore errors about the amlpkg, the update archive is in the target folder as a tar archive.


    Thanks to the LibreELEC team, Codesnake, KOPRajs, dtech and of course anyone else connected with this project I've failed to mention.

    - qUE

    As I see it, the problem here will be different. First, loading dhd is unnecessary if your device has Realtek wifi. The error also applies to this, the 8188eu module seems to be loaded, but cfg80211 is required for the wifi to work, but it crashes due to the incorrect dhd-config. The dhd is only required for Broadcom-based chips.

    Question #1: Did you use my Wetek Play project directory as a base? Because then you have to delete this file:

    LibreELEC-AML/projects/<YOURPROJECTNAME>/filesystem/usr/lib/modules-load.d/wireless.conf

    This will force load dhd even if it is not needed. And that might be the problem for you.

    Question #2: Which dtd file did you use in your project?

    Code: options
      # Kernel extra targets to build
        KERNEL_UBOOT_EXTRA_TARGET="<filename>.dtd"

    Deleting wireless.conf has worked afaics, thankyou dtech!

    Will try and collate everything in the next post :)

    The Realtek 8188* is a general USB chip, I also have an external one (TP-Link TL-WN722 v2).

    I use an external module for this in my builds, instead of the integrated module of the kernel.

    First, you need to check if it is enabled in your kernel configuration, because if it is, it should be disabled:

    Code: linux.arm.conf
    # CONFIG_RTL8188EU is not set

    Next, add RTL8188EU-aml to the ADDITIONAL_DRIVERS variable in the options file in your project directory.

    If that doesn't help either, then please send me a log file: journalctl | paste

    'is not set' was already in place, added ADDITIONAL_DRIVERS and rebuilt, but no change. Here is the journal;

    http://ix.io/4lVq

    Not sure if the NULL dereference at 'kernel: wifi_setup_dt' is causing an issue?

    If you think so, maybe I can help you with that.

    Hi dtech,

    I've got Libreelec-AML 9.2.8.7 to build and boot on the MX box, but I'm having an issue with the Realtek 8188ETV wireless.

    Libreelec doesn't allow me to enable the 'wireless active' option. I've SSH'd and lsusb, the device is present so I assume the drivers are working.

    Various places have mentioned Realtek wireless support is a bit of an issue of contention for the libreelec team, so I'm expecting some pain getting this working.

    Unfortunately, this is my first outing in compiling the linux kernel so I'm really a n00b when it comes to this. Is there any recommendations in tackling this issue?

    I can post dmesg dump if that would be any help.

    - qUE

    Hi @KOPRajs, I was wondering if you could look into an issue. I have a Matricom MX2 and with the 20190424 build, the fast forward (right arrow key) always causes the box to freeze. Has anyone also encountered this issue? I switched back to 8.0.2 and everything runs fine. Could you please take a look? Thanks.

    Try disabling the hardware acceleration in settings > player. Some streams seem to crash the hardware decoding, although disabling this can make HD streams struggle.