Amlogic-no Discussion

Yes, it notifies about an “android update”. I know about frequent updates on nightlies, not a problem, I am using them since years with all ce versions.

I read about that case mod, but I don’t have temp problems till now, with the latest nightly.

Normally it runs about 65°C, with -ne, and a bit more with previous -no nightlies, but not 85…

I don’t know what the cause of the problem is on your board, a hardware/config conflict I assume. The custom dtb disabled the need for sdio voltage switching.

Yes mt7668 bt & wifi work on the Cube in the latest CE-NO nightly.

1 Like

@vpeter ping

i already reinstalled widevine, And i need help to rule out that the PVR addon itself is the issue. How can i test this? As already said, i can play the zattoo stream on other devices or the same device with the amlogic instead of amlogic-no version.

Hi

My Minix Neo U22-XJ boots into a white noise screen (static) with CoreELEC-Amlogic-no.aarch64-22.0-Piers_nightly_20250526-Generic.img.gz and using g12b_s922x_minix_u22xj.dtb.
I’ve tried two sd-cards. Any ideas how to diagnose?

NB this is the first time I’ver tried amlogi-no so apols if I’m missing something obvious.

Try older version from archive 2024, question is if your hardware works with older kernel . Less issues was in this older time.

https://archive.coreelec.org/Amlogic-no/CE-22/20241220/

Helped it ?

Maybe you need to use rev_a DTB.
On Minix there is no multidtb possible to use.
There are more than 30 u22j (max) online.

1 Like

Tx for the suggestion!
I’m showing my ignorance by not knowing how to use what’s in the tar file.
I couldn’t see a flashable image there so I just copied g12b_s922x_minix_u22xj.dtb from CoreELEC-Amlogic-no.aarch64-22.0-Piers_nightly_20241220\3rdparty\bootloader\device_trees into root of the original CoreELEC-Amlogic-no.aarch64-22.0-Piers_nightly_20250526-Generic.img.gz image sd-card - and it booted!

In detail, the Minix splash screen showed, then the familiar white noise screen briefly, then the Corelec ‘New Order’ logo with the partition resizing progress txt, then it rebooted again, and the setup process started.
I’ve no idea if what I’ve done is correct however but at least it boots. Happy to obtain logs etc. if that helps to fix the newer builds.

1 Like

I have also briefly white-green artefacts (screen noise but in green white and black color ) in boot time at ugoos am6plus with cpu s922xj. You must be now happy due to success booting. Nobody know a reason for this artefats at builts of CE22NO with newer kernel.

yes try put here all logs. Your bootloader is not encrypted than on my device from ugoos. Maybe is same reason which would be better identified through your device.

I checked coreelec:debuglogs [CoreELEC Wiki] but all the methods seem to need CE/Kodi to have booted, and of course it sticks at the static screen before reaching CE. How do I obtain any debug info?

Mine looks like this:

my booting of ce22NO looks like this:

The only ‘rev_a’ I could see in devicetree of CoreELEC-Amlogic-no.aarch64-22.0-Piers_nightly_20250526-Generic.img was g12b_s922x_minix_u22xj_max_rev_a.dtb and mine is not the Max model.

Hi there,

I just wanted to contribute my experience / issue / error with the newest NIGHTLY-version of Coreelec-NO (CoreELEC-Amlogic-no.aarch64-22.0-Piers_nightly_20250526-Generic).

I flashed it as a clean install on a sd card on my amlogic 905x2 device (that can run EmuELEC-NG and CoreELEC-NG without any problems), using “g12a_s905x2_4g.dtb” as DTB.img and after partitioning and creating the file systems and doing the reboot, the CoreELEC logo shows up for a while and then it crashes (with a kernel panic, I think, but nothing is visible, the HDMI connection is being lost).

I was able to connect my device via UART and get a log.

Perhaps someone is able to find out what the problem is and perhaps help me out or use that information to fix that particular problem in the next version… ?

Anyway, I hope this information is useful.

Thanks a lot for all your hard work, it’s highly appreciated!

CE-NO-UART.txt (25.7 KB)

Thank you very much for the log.
Can you add this line in your config.ini for a more detailed log please:
coreelec='quiet loglevel=9 nopkmute'

And I think you have a mt76 WiFi chip:
wlan_mt76x8_sdio.

So @YadaYada might take look about it.
G12A is a bit unusual about sdio as it share same bus for uSD and WiFi.

Have you time create log and upload here ?

https://wiki.coreelec.org/coreelec:debuglogs

@atirage21 If you tell me how to create a log, given that CE never displays (so I can’t even configure a network) then I’m happy to do it. I don’t have a UART adapter which I presume is something like this? AZDelivery UART-TTL USB Adapter 3.3V 5V CH340G Interface Converter Module, with 20cm Jumper Cable compatible with Arduino Including E-Book! : Amazon.co.uk: Computers & Accessories

Why you dont use this easy guide ? You must only upload url adress here from logging. Now you have booted last updated system with older dtb. It would be maybe usefully see logs from this case.

https://wiki.coreelec.org/coreelec:debuglogs

For your issue with dtb dont need maybe uart usb adapter. And how you will put on board without compatible pins on minix box? In past was special sdio debug board for this: CoreELEC Team SDIO Debug Board

I found something with support of sdio debug: Amazon.de …but only CE team know say if is usefully or not.

I read the guide but it didn’t answer my question, save for the UART adapter.