Thanx. I have also tried the 19.4 nightly via update, still the same problems. I don’t have a problem installing CE 19.x, I have the Widevine installation problem. Tried changing download location in InputStream Helper, tried downloading directly from it…always a freeze and a reboot.
Hello, yes I don’t see a /dev/adaptor/frontend0 too.
Mecool M8S plus DVB-T2 - AVL6762 + M803
I install 19.3 and I have to say the I2C does not work.
You can see that is nothing on the I2C BUS.
Where can be a isue?
CoreELEC:~ # i2cdetect 0
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0.
I will probe address range 0x08-0x77.
Continue? [Y/n] y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: – – – – – – – –
10: – – – – – – – – – – – – – – – –
20: – – – – – – – – – – – – – – – –
30: – – – – – – – – – – – – – – – –
40: – – – – – – – – – – – – – – – –
50: – – – – – – – – – – – – – – – –
60: – – – – – – – – – – – – – – – –
70: – – – – – – – –
CoreELEC:~ # i2cdetect 1
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-1.
I will probe address range 0x08-0x77.
Continue? [Y/n] y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: – – – – – – – –
10: – – – – – – – – – – – – – – – –
20: – – – – – – – – – – – – – – – –
30: – – – – – – – – – – – – – – – –
40: – – – – – – – – – – – – – – – –
50: – – – – – – – – – – – – – – – –
60: – – – – – – – – – – – – – – – –
70: – – – – – – – –
CoreELEC:~ # i2cdetect 2
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-2.
I will probe address range 0x08-0x77.
Continue? [Y/n] Y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: – – – – – – – –
10: – – – – – – – – – – – – – – – –
20: – – – – – – – – – – – – – – – –
30: – – – – – – – – – – – – – – – –
40: – – – – – – – – – – – – – – – –
50: – – – – – – – – – – – – – – – –
60: – – – – – – – – – – – – – – – –
70: – – – – – – – –
CoreELEC:~ # i2cdetect 3
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-3.
I will probe address range 0x08-0x77.
Continue? [Y/n] Y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: – – – – – – – –
10: – – – – – – – – – – – – – – – –
20: – – – – – – – – – – – – – – – –
30: – – – – – – – – – – – – – – – –
40: – – – – – – – – – – – – – – – –
50: – – – – – – – – – – – – – – – –
60: – – – – – – – – – – – – – – – –
70: – – – – – – – –
In version CoreElec 9.2.8 you can see this:
CoreELEC (official): 9.2.8 (Amlogic.arm)
M8S-CoreELEC:~ # i2cdetect 0
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0.
I will probe address range 0x03-0x77.
Continue? [Y/n] Y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: – – – – – – – – – – – – –
10: – – – – – – – – – – – – – – – –
20: – – – – – – – – – – – – – – – –
30: – – – – – – – – – – – – – – – –
40: – – – – – – – – – – – – – – – –
50: UU – – – – – – – – – – – – – – –
60: – – – – – – – – – – – – – – – –
70: – – – – – – – –
M8S-CoreELEC:~ # i2cdetect 1
Error: Could not open file `/dev/i2c-1' or `/dev/i2c/1’: No such file or directory
M8S-CoreELEC:~ # i2cdetect 2
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-2.
I will probe address range 0x03-0x77.
Continue? [Y/n] Y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f
10: 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f
20: 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f
30: – – – – – – – – 38 39 3a 3b 3c 3d 3e 3f
40: 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f
50: – – – – – – – – – – – – – – – –
60: 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f
70: 70 71 72 73 74 75 76 77
M8S-CoreELEC:~ # i2cdetect 3
Error: Could not open file `/dev/i2c-3' or `/dev/i2c/3’: No such file or directory
M8S-CoreELEC:~ #
[ 8.749121@0] kernel-overlays-setup: processing conf /storage/.cache/kernel-overlays/50-driver.dvb.dvb-latest.conf
[ 8.785757@0] kernel-overlays-setup: added modules from /usr/lib/kernel-overlays/driver.dvb.dvb-latest/lib/modules/3.14.29
[ 14.236016@2] dvb_meson dvb.50: Found i2c-2 adapter: aml_i2c_adap2
[ 14.236034@2] dvb_meson dvb.50: ts0: parallel
[ 14.236152@2] dvb_meson dvb.50: ts0_control: 0x0
[ 14.236197@2] dvb_meson dvb.50: GPIO fec_reset0: 217
[ 14.236209@2] dvb_meson dvb.50: GPIO power_ctrl0: 215
[ 14.236243@2] dvb_meson dvb.50: dev_name=avl6762
[ 15.452326@2] dvb_meson dvb.50: DVB demod detection for i2c-2 (aml_i2c_adap2)…avl6762
[ 16.672250@2] dvb_meson dvb.50: Checking for Availink AVL6762 DVB-T2/C demod …
[ 17.092931@2] i2c i2c-2: dvb_meson: found AVL6862 family_id=0x68624955
[ 19.974836@2] dvb_meson dvb.50: Total DVB modules found: 1
[ 19.976820@1] dvbdev: DVB: registering new adapter (dvb_meson)
[ 19.991079@0] dvb_meson dvb.50: DVB: registering adapter 0 frontend 0 (Availink AVL6762)…
[ 20.764496@0] dvb_meson dvb.50: DVB: adapter 0 frontend 0 frequency 0 out of range (47000000…858000000)
Bluetooth Problem
My device is ugoos am6b plus , system is CoreELEC 19.2-Matrix. I encounted one problem. The remote controller can pair with the CoreELEC system by bluetooth, most button of remote controller is valid ,but only the ‘play/pause’ button not work. I guess the remote.conf is error . Can someone provide the solution? Thank you very much!
My remote.conf file content is below.
work_mode = 0
repeat_enable = 1
repeat_delay = 130
repeat_peroid = 120
release_delay = 20
debug_enable = 1
custom_begin
factory_code = 0xff000001
key_begin
0x14 116 #power
0x13 46
0x03 103 #up
0x02 108 #down
0x0e 105 #left
0x1a 106 #right
0x07 28
0x58 114 #volume-
0x0b 115 #volume+
0x01 1
0x48 172
0x5c 164 #play/pause
key_end
custom_end
Please provide samples for the related files so we can check them and edit your post. Refer the type of file/codec but don’t use full release name file. That’s not accepted here.
Hi vpeter
I tried these from stable relase 19.3-Matrix:
gxl_p231_1g_m8s_dvb.dtb
gxl_p231_1g_dvb.dtb
If I try the night release 20211120 with
gxl_p231_1g_m8s_dvb.dtb
gxl_p231_1g_dvb.dtb
then I do not see any I2C device in /proc/device-tree/
And what works with 9.2.8?
Yes if I using this dtb gxl_p231_1g_m8s_dvb.dtb (40.6 KB)
Before I tried the dtb from AlexElec from: AE-AML/device-trees-amlogic-001_gxl_p231_1g_m8s_dvbt.patch at master · AlexELEC/AE-AML · GitHub
gxl_p231_1g_m8s_dvbt.dtb (41.1 KB)
because with this AlexElec working correctly.
@megaslx we’re here to help and not overcomplicate. Why can’t you just present your problem in a “cleaner” way?
Was/Is the version of android on your device 6.x? If so it sounds like a boot loader issue. I’ve had S905x boxes that would boot to CE 19.x but crash/reboot inexplicably.
The solution is to update to an Android 7.x or greater, either a general usage for S905x , ala Aidan’s Rom or ATVxperience or one of the other ROMS mentioned in the threads below:
https://discourse.coreelec.org/t/testers-wanted-gxl-1gb-ram-devices-amlogic-ng/15877/3
https://discourse.coreelec.org/t/s905x-1gb-android-6-and-coreelec-ng-boot-failure/14767
In a nutshell, do your reading as it’s all been covered in the linked threads. Please make sure you have a working ROM for your box before you try installing anything. That way you have something to fall back to if something goes wrong.
Mecool M8S plus DVB-T - AVL6762 + M803
Only DVB-T tuner does not work in CoreEelec 19.3, other all works.
In CoreElec 9.2.8 working DVB-T2 correctly.
[ 0.000000@0] CoreELEC dt-id: gxl_p231_1g_m8s_dvb
[ 15.032923@1] DVB: aml_dvb_probe: probe amlogic dvb driver
[ 15.032967@1] DVB: aml_dvb_probe: dmx rst ctl = ffffffc022d13e40
[ 15.032975@1] DVB: aml_dvb_probe: asyncfifo rst ctl = ffffffc022d13f00
[ 15.032982@1] DVB: aml_dvb_probe: ahbarb0 rst ctl = ffffffc022d13a00
[ 15.032990@1] DVB: aml_dvb_probe: uparsertop rst ctl = ffffffc022d13880
[ 15.033112@1] DVB: registering new adapter (amlogic-dvb)
[ 15.033118@1] DVB: aml_dvb_probe: Registered adpter: amlogic-dvb
[ 27.627465@1] amlogic-dvb dvb.50: DVB: registering adapter 0 frontend 0 (Availink avl6862)...
CoreELEC:~ # ls /dev/ |grep i2
i2c-0
i2c-2
CoreELEC:~ # ls /dev/dvb/adapter0/
demux0 demux2 dvr1 frontend0 net1
demux1 dvr0 dvr2 net0 net2
But the same configuration in CoreElec 19.3-Matrix does not working.
CoreELEC (official): 19.3-Matrix (Amlogic-ng.arm)
CoreELEC:~ # dmesg |grep dvb
[ 0.000000@0] CoreELEC dt-id: gxl_p231_1g_m8s_dvb
[ 6.993258@0] kernel-overlays-setup: processing conf /storage/.cache/kernel-overlays/50-driver.dvb.dvb-latest.conf
[ 7.136192@3] kernel-overlays-setup: added modules from /storage/.kodi/addons/driver.dvb.dvb-latest//kernel-overlay/lib/modules/4.9.113
[ 17.117416@2] dvb_meson dvb: Found i2c-1 adapter: Meson I2C adapter
[ 17.117428@2] dvb_meson dvb: ts0: parallel
[ 17.119337@2] dvb_meson dvb: ts0_control: 0x0
[ 17.119490@2] dvb_meson dvb: dev_name=avl6762
[ 18.342610@1] dvb_meson dvb: DVB demod detection for i2c-1 (Meson I2C adapter)...
[ 19.557801@3] dvb_meson dvb: Checking for Availink AVL6762 DVB-T2/C demod ...
[ 19.557984@3] i2c i2c-1: dvb_meson: i2c wr failed=-6 len=3
[ 19.558119@3] i2c i2c-1: dvb_meson: i2c rd failed=-6 len=4
[ 19.558266@3] i2c i2c-1: dvb_meson: i2c wr failed=-6 len=3
[ 19.558418@3] i2c i2c-1: dvb_meson: i2c rd failed=-6 len=4
[ 19.558426@3] i2c i2c-1: dvb_meson: attach failed reading id
[ 19.558434@3] dvb_meson dvb: Failed to find AVL6762 demod!
[ 19.558438@3] dvb_meson dvb: Total DVB modules found: 0
[ 19.568413@3] dvbdev: DVB: registering new adapter (dvb_meson)
CoreELEC:~ # ls /dev/ |grep i2
i2c-0
i2c-1
i2c-2
i2c-3
CoreELEC:~ # ls /dev/dvb/adapter0/
demux0 demux1 demux2 dvr0 dvr1 dvr2 net0 net1 net2
CoreELEC:~ #
sorry,the imax hdr media playback problem happends on android kodi too,so it’s kodi’s problem.but I make a few mins smaple file out of the original one so you can reproduce it. the link:Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
Can you try with this dtb? File on MEGA
In case something happen be sure to know how to recover. But I think this should not be needed.
Thanks. With this tdb DVB-T working correctly.
But not working NAND or eMMC for reading or writing optionds for booting.
I thik that could be a tdb issue too.
CoreELEC:~ # fw_printenv
Cannot parse config file '/etc/fw_env.config': Invalid argument
CoreELEC:~ # cat /etc/fw_env.config
# Configuration file for fw_(printenv/setenv) utility.
# Up to two entries are valid, in this case the redundant
# environment sector is assumed present.
# Notice, that the "Number of sectors" is not required on NOR and SPI-dataflash.
# Futhermore, if the Flash sector size is ommitted, this value is assumed to
# be the same as the Environment size, which is valid for NOR and SPI-dataflash
# NOR example
# MTD device name Device offset Env. size Flash sector size Number of sectors
#/dev/mtd1 0x0000 0x4000 0x4000
#/dev/mtd2 0x0000 0x4000 0x4000
# MTD SPI-dataflash example
# MTD device name Device offset Env. size Flash sector size Number of sectors
#/dev/mtd5 0x4200 0x4200
#/dev/mtd6 0x4200 0x4200
# NAND example
#/dev/mtd0 0x4000 0x4000 0x20000 2
# Block device example
#/dev/mmcblk0 0xc0000 0x20000
# VFAT example
#/boot/uboot.env 0x0000 0x4000
# Amlogic NAND
/dev/nand_env 0x000000 0x10000 0x10000
# Amlogic eMMC
/dev/env 0x000000 0x10000 0x10000
root@CoreELEC:~$ ls /dev/f*
/dev/fb0 /dev/firmware_vdec /dev/full
/dev/fb1 /dev/fsck.log /dev/fuse
/dev/fd:
0 1 2 3 8
root@CoreELEC:~$ ls /dev/na*
ls: /dev/na*: No such file or directory
1 Like
Good.
I’m not familiar with emmc/nand. Do you boot from SD card or emmc/nand?
I using booth mode.
For standard booting from internal flash, for testing using USB microSD.
In 9.2.8 fw_printenv working.
Can you reboot and post url from command
dmesg | pasteI can only assume that environment partition (env) does not exists. And that’s why you can’t edit boot environment.
Same here.
N2 running CE 19.3 on SD card
fw_printenv
Cannot parse config file ‘/etc/fw_env.config’: Invalid argument
file /etc/fw_env.config
/etc/fw_env.config: ASCII text
/etc/fw_env.config exists but the command fw_printenv is not working