How to compile a personalized CoreELEC

Easy, read the log:
404 Not Found

2024-11-04 12:10:29 (1.97 MB/s) - '/home/zeus/CoreELEC/sources/json-c/json-c-0.17.tar.gz' saved [364482]

    e[1;31mWARNINGe[0m      Incorrect checksum calculated on downloaded file: got bca9a584a8da64d8dff50082a06f6cea26fb735f74924afc6d01ae6be7a75885 wanted fc1b9ed57f4cda51c52ec9b3b012f6973bd8d80fb70f363c5ca2754342389eb1

Wrong SHA, should be fixed with next nightly.

1 Like

Thank you very much

@Portisch , Just FYI, I was able to fix this issue on my git clone but I also noticed the same problem with wireguard-linux-compat package.mk which I also have fixed in my git clone also.

Thanks again for the help.

Also fixed now.

1 Like

Is there documentation of how CoreELEC process works from reading the media to sending the finalized signal to the output hdmi? Thank you.

Today I started getting this error (FAILURE: scripts/install cairo:target has failed!) - please see log. Never got it before. Did something change on the last week or so?

Thank you for your help.

235.log (12.6 KB)

You have some kind of DNS issues:

--2024-11-12 10:34:57--  https://cairographics.org/releases/cairo-1.18.0.tar.xz
Resolving cairographics.org (cairographics.org)... failed: Temporary failure in name resolution.
wget: unable to resolve host address 'cairographics.org'

Thank you, appreciate your help. Will check, probably my DNS got corrupted.

I have a small example patch:

diff --git a/arch/arm64/boot/dts/amlogic/g12a_s905x2_u212.dts b/arch/arm64/boot/dts/amlogic/g12a_s905x2_u212.dts
index affb81a4f..b6f8a6bdd 100644
--- a/arch/arm64/boot/dts/amlogic/g12a_s905x2_u212.dts
+++ b/arch/arm64/boot/dts/amlogic/g12a_s905x2_u212.dts
@@ -223,7 +223,7 @@

                sys_led {
                        label="sys_led";
-                       gpios=<&gpio_ao GPIOAO_11 GPIO_ACTIVE_LOW>;
+                       gpios=<&gpio_ao GPIOAO_11 GPIO_ACTIVE_HIGH>;
                        default-state ="on";
                };
        };

In which directory should I place it so that it gets included in the CE NO compilation?

projects/Amlogic-ce/packages/linux-drivers/amlogic/common_drivers/patches/common_drivers-010-dts-gpio.patch

Unfortunately it doesn’t apply and I don’t know why?

CLEAN      common_drivers
    *      Removing /home/moje/CoreELEC/build.CoreELEC-Amlogic-no.aarch64-22/build/common_drivers-1c3ae1eec3f4741bba36a9980304485ce4248b36 ...
    *      Removing /home/moje/CoreELEC/build.CoreELEC-Amlogic-no.aarch64-22/qa_checks/common_drivers-* ...
UNPACK      common_drivers
    APPLY PATCH (common)      projects/Amlogic-ce/packages/linux-drivers/amlogic/common_drivers/patches/common_drivers-010-dts-gpio.patch
patching file arch/arm64/boot/dts/amlogic/g12a_s905x2_u212.dts
Hunk #1 FAILED at 223.
1 out of 1 hunk FAILED -- saving rejects to file arch/arm64/boot/dts/amlogic/g12a_s905x2_u212.dts.rej
*********** FAILED COMMAND ***********
patch -d "${PKG_BUILD}" -p1 < ${i} >&${VERBOSE_OUT}
**************************************
*********** FAILED COMMAND ***********
${SCRIPTS}/unpack "${p}" "${PARENT_PKG}"
**************************************
*********** FAILED COMMAND ***********
${SCRIPTS}/unpack "${PKG_NAME}" "${PARENT_PKG}"
**************************************
FAILURE: scripts/build linux:host has failed!

The following log for this failure is available:
  /home/moje/CoreELEC/build.CoreELEC-Amlogic-no.aarch64-22/.threads/logs/61.log

>>> linux:host seq 61 >>>
[059/356] [FAIL] build   linux:host

The following log for this failure is available:
  /home/moje/CoreELEC/build.CoreELEC-Amlogic-no.aarch64-22/.threads/logs/61.log

Can I get more detailed logs?

Look there?

I found nothing there.

--- arch/arm64/boot/dts/amlogic/g12a_s905x2_u212.dts
+++ arch/arm64/boot/dts/amlogic/g12a_s905x2_u212.dts
@@ -223,7 +223,7 @@

                sys_led {
                        label="sys_led";
-                       gpios=<&gpio_ao GPIOAO_11 GPIO_ACTIVE_LOW>;
+                       gpios=<&gpio_ao GPIOAO_11 GPIO_ACTIVE_HIGH>;
                        default-state ="on";
                };
        };

That’s why I asked if it was possible to get detailed logs.

No? You are using 8 spaces instead of one tab character. Compare with original file how it should look.

you need to look in

build.CoreELEC-Amlogic-no.aarch64-22/build/linux-........./common_drivers/arch/arm64/bot/dts/amlogic

Thank you, that was it. I was copy pasting and the tab got lost. Thanks again!

1 Like