GTMedia GTC S905D

I installed the latest CoreElec on my GTC, I use the gxl_p231_2g_dvb.dtb.
To enable the display, install the OpenVFD service from the CoreElec repository and put this file in /storage/.config/vfd.conf. Configure the openVFD service with a Display Brightness of 2. My box is very bright at the default level 7.
I also made an custom keymap. Put the file gtc in /storage/.config/rc_keymaps/gtc
Rename /storage/.config/rc_maps.cfg.sample to /storage/.config/rc_maps.cfg and add

meson-ir        *       gtc

to /storage/.config/rc_maps.cfg

The tuners look detected, but tvheadend can’t see them (no frontend for adapter0 ?). It works fine with a AstroMeta RTL2832.

dmesg | grep dvb

[    5.509599@3] usb 1-1: Product: dvbt2
[    5.509612@3] usb 1-1: Manufacturer: astrometadvbt2
[   17.028095@2] kernel-overlays-setup: processing conf /storage/.cache/kernel-overlays/50-driver.dvb.dvb-latest.conf
[   17.085485@2] kernel-overlays-setup: added modules from /usr/lib/kernel-overlays/driver.dvb.dvb-latest/lib/modules/3.14.29
[   21.326825@0] DVB: aml_dvb_probe: probe amlogic dvb driver
[   21.326854@0] DVB: aml_dvb_probe: dmx rst ctl = ffffffc05e0e8600
[   21.326863@0] DVB: aml_dvb_probe: asyncfifo rst ctl = ffffffc05e0e8680
[   21.326870@0] DVB: aml_dvb_probe: ahbarb0 rst ctl = ffffffc05e0e8700
[   21.326878@0] DVB: aml_dvb_probe: uparsertop rst ctl = ffffffc05e0e8780
[   21.326980@0] dvbdev: DVB: registering new adapter (amlogic-dvb)
[   21.326986@0] DVB: aml_dvb_probe: Registered adpter: amlogic-dvb
[   21.376592@1] usb 1-1: dvb_usb_v2: found a 'Astrometa DVB-T2' in warm state
[   21.478782@3] usb 1-1: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
[   21.478811@3] dvbdev: DVB: registering new adapter (Astrometa DVB-T2)
[   21.479818@3] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
[   21.505521@2] dvbdev: dvb_create_media_entity: media entity 'Realtek RTL2832 (DVB-T)' registered.
[   21.507577@0] dvbdev: dvb_create_media_entity: media entity 'Panasonic MN88473' registered.
[   21.575754@2] rc rc1: lirc_dev: driver dvb_usb_rtl28xxu registered at minor = 1, raw IR receiver, no transmitter
[   21.575985@2] usb 1-1: dvb_usb_v2: schedule remote query interval to 200 msecs
[   21.586935@2] usb 1-1: dvb_usb_v2: 'Astrometa DVB-T2' successfully initialized and connected
[   21.587225@2] usbcore: registered new interface driver dvb_usb_rtl28xxu
[   27.649594@3] mn88473 5-0018: downloading firmware from file 'dvb-demod-mn88473-01.fw'

CoreELEC:~ # ls /dev/dvb/ -alR
/dev/dvb/:
total 0
drwxr-xr-x    4 root     root            80 Jun 22 13:11 .
drwxr-xr-x   14 root     root          4220 Jun 22 13:11 ..
drwxr-xr-x    2 root     root           220 Jun 22 13:11 adapter0
drwxr-xr-x    2 root     root           140 Jun 22 13:11 adapter1

/dev/dvb/adapter0:
total 0
drwxr-xr-x    2 root     root           220 Jun 22 13:11 .
drwxr-xr-x    4 root     root            80 Jun 22 13:11 ..
crw-rw----    1 root     video     212,   0 Jan  1  2015 demux0
crw-rw----    1 root     video     212,   3 Jan  1  2015 demux1
crw-rw----    1 root     video     212,   6 Jan  1  2015 demux2
crw-rw----    1 root     video     212,   1 Jan  1  2015 dvr0
crw-rw----    1 root     video     212,   4 Jan  1  2015 dvr1
crw-rw----    1 root     video     212,   7 Jan  1  2015 dvr2
crw-rw----    1 root     video     212,   2 Jan  1  2015 net0
crw-rw----    1 root     video     212,   5 Jan  1  2015 net1
crw-rw----    1 root     video     212,   8 Jan  1  2015 net2

/dev/dvb/adapter1:
total 0
drwxr-xr-x    2 root     root           140 Jun 22 13:11 .
drwxr-xr-x    4 root     root            80 Jun 22 13:11 ..
crw-rw----    1 root     video     212,   9 Jan  1  2015 demux0
crw-rw----    1 root     video     212,  10 Jan  1  2015 dvr0
crw-rw----    1 root     video     212,  12 Jan  1  2015 frontend0
crw-rw----    1 root     video     212,  13 Jan  1  2015 frontend1
crw-rw----    1 root     video     212,  11 Jan  1  2015 net0

Hello,
Just to ask if CoreElec team going to support this device in the future and especially the drivers for internal tuners?
Thanks in advance.

I’m considering buying a new STB but I’m not sure what to get. Can you give me more information about the tuners? (internal/external), drivers and etc

I want to use DVB-S2 with TVHeadend.

Thank you!

None of our developers have access to this device so we can’t add support for the internal tuners.

Buy a device that is already supported like the Mecool KIII.

@anon88919003
What do you mean?
None of your developers team have physically this device, or you just have no acces to the driver’s code from the manufacturer?

If it is the first one, then we can help and donate it. For sure, there are people among us that are interested.

Can any of the developers join the discussion?

Hi,
I also have this device, I’ve already put apart the device to check the demodulator part number, but unfortunately it was erased.
This is what’s in the android dtb file:

banks@c11080b0 {
reg = <0x0 0xc88344b0 0x0 0x28 0x0 0xc88344e8 0x0 0x14 0x0 0xc8834520 0x0 0x14 0x0 0xc8834430 0x0 0x40>;
reg-names = “mux”, “pull”, “pull-enable”, “gpio”;
gpio-controller;
#gpio-cells = <0x2>;
linux,phandle = <0x9>;
phandle = <0x9>;
};

dvbfe {
compatible = “amlogic, dvbfe”;
dev_name = “dvbfe”;
dtv_demod0 = “cxd28xx”;
dtv_demod0_i2c_adap_id = <0x2>;
dtv_demod0_i2c_addr = <0x6c>;
dtv_demod0_reset_value = <0x0>;
dtv_demod0_reset_gpio = <0x9 0x49 0x0>;
fe0_dtv_demod = <0x0>;
fe0_ts = <0x0>;
fe0_dev = <0x0>;
};

Kernel config also contain references to the cxd28xx demodulator with this: CONFIG_AM_CXD28XX=y
On the other hand I found this on logcat:
4576 4576 D TVService_WINSAT05: valuefe = dtv_demod 0 driver Avl6211|dtv_demod 0 i2c_id 2|dtv_demod 0 i2c_addr 0xc0|dtv_demod 0 reset_gpio GPIOY_5|frontend 0 dtv_demod 0|frontend 0 ts 0|enable 0
Here are some photos of the device pcb: https://31l1jo.s.cld.pt
If any dev could help I can provide logs, I can also provide logs from uart.

Same as GTMedia GTT-2 (S905D)
openVFD and keymap works (add 0x310 KEY_MUTE)
DVB-T2 have same problem.

ls /dev/dvb/ -alR

/dev/dvb/:
total 0
drwxr-xr-x    3 root     root            60 Jan  1  2015 .
drwxr-xr-x   15 root     root          4040 Jan  1  2015 ..
drwxr-xr-x    2 root     root           220 Jan  1  2015 adapter0

/dev/dvb/adapter0:
total 0
drwxr-xr-x    2 root     root           220 Jan  1  2015 .
drwxr-xr-x    3 root     root            60 Jan  1  2015 ..
crw-rw----    1 root     video     212,   4 Jan  1  2015 demux0
crw-rw----    1 root     video     212,  20 Jan  1  2015 demux1
crw-rw----    1 root     video     212,  36 Jan  1  2015 demux2
crw-rw----    1 root     video     212,   5 Jan  1  2015 dvr0
crw-rw----    1 root     video     212,  21 Jan  1  2015 dvr1
crw-rw----    1 root     video     212,  37 Jan  1  2015 dvr2
crw-rw----    1 root     video     212,   7 Jan  1  2015 net0
crw-rw----    1 root     video     212,  23 Jan  1  2015 net1
crw-rw----    1 root     video     212,  39 Jan  1  2015 net2

dmesg | grep DVB

[   12.921847@2] DVB: aml_dvb_probe: probe amlogic dvb driver
[   12.921870@2] DVB: aml_dvb_probe: dmx rst ctl = ffffffc05e777540
[   12.921875@2] DVB: aml_dvb_probe: asyncfifo rst ctl = ffffffc05e7775c0
[   12.921880@2] DVB: aml_dvb_probe: ahbarb0 rst ctl = ffffffc05e777640
[   12.921885@2] DVB: aml_dvb_probe: uparsertop rst ctl = ffffffc05e7776c0
[   12.921979@2] DVB: registering new adapter (amlogic-dvb)
[   12.921981@2] DVB: aml_dvb_probe: Registered adpter: amlogic-dvb
[   13.218740@2] DVB FE: Init AVL6862 frontend 0
[   14.880187@2] DVB FE: avl6862_attach attach failed!!!

dmesg | grep i2c

[    0.083382@0] aml_i2c version: 20140813
[    0.083567@0] i2c-core: driver [pmu4] using legacy resume method
[    0.088504@0] aml-i2c c11087e0.i2c: add adapter aml_i2c_adap3(ffffffc01039a0e0)
[    0.299862@0] i2c-gpio i2c_gpio.39: using pins 172 (SDA) and 173 (SCL)
[    0.362506@1] i2c /dev entries driver
[   14.503643@2] i2c i2c-3: [aml_i2c_xfer] error ret = -5 (-EIO)
[   14.503656@2] i2c i2c-3: token 1, master_no(3) 100K addr 0x14
[   14.555250@2] i2c i2c-3: [aml_i2c_xfer] error ret = -5 (-EIO)
[   14.555264@2] i2c i2c-3: token 1, master_no(3) 100K addr 0x14
[   14.555303@2] i2c i2c-3: avl6862: i2c wr failed=-11 len=3
[   14.607385@2] i2c i2c-3: [aml_i2c_xfer] error ret = -5 (-EIO)
[   14.607398@2] i2c i2c-3: token 1, master_no(3) 100K addr 0x14
[   14.659734@2] i2c i2c-3: [aml_i2c_xfer] error ret = -5 (-EIO)
[   14.659747@2] i2c i2c-3: token 1, master_no(3) 100K addr 0x14
[   14.659754@2] i2c i2c-3: avl6862: i2c rd failed=-11 len=4
[   14.713873@2] i2c i2c-3: [aml_i2c_xfer] error ret = -5 (-EIO)
[   14.713886@2] i2c i2c-3: token 1, master_no(3) 100K addr 0x14
[   14.769207@2] i2c i2c-3: [aml_i2c_xfer] error ret = -5 (-EIO)
[   14.769220@2] i2c i2c-3: token 1, master_no(3) 100K addr 0x14
[   14.769227@2] i2c i2c-3: avl6862: i2c wr failed=-11 len=3
[   14.824743@2] i2c i2c-3: [aml_i2c_xfer] error ret = -5 (-EIO)
[   14.824755@2] i2c i2c-3: token 1, master_no(3) 100K addr 0x14
[   14.880147@2] i2c i2c-3: [aml_i2c_xfer] error ret = -5 (-EIO)
[   14.880160@2] i2c i2c-3: token 1, master_no(3) 100K addr 0x14
[   14.880167@2] i2c i2c-3: avl6862: i2c rd failed=-11 len=4
[   14.880172@2] i2c i2c-3: avl6862: attach failed reading id

lsmod

Module                  Size  Used by
avl6862               266301  0
8021q                  19039  0
8189es               1178409  0
cfg80211              374882  1 8189es
aml_fe                  7230  0
ir_lirc_codec           4996  0
lirc_dev               11232  1 ir_lirc_codec
ir_mce_kbd_decoder      4796  0
ir_sanyo_decoder        2899  0
ir_sony_decoder         2417  0
ir_jvc_decoder          2511  0
ir_rc6_decoder          3423  0
ir_rc5_decoder          2439  0
ir_nec_decoder          3367  0
meson_ir                4021  0
mali                  192665  5
aml                    82222  1 aml_fe
rc_core                17268  11 lirc_dev,meson_ir,ir_lirc_codec,ir_rc5_decoder,ir_nec_decoder,ir_sony_decoder,ir_mce_kbd_decoder,ir_jvc_decoder,ir_rc6_decoder,ir_sanyo_decoder
dvb_core               97191  2 aml,aml_fe
openvfd               144963  1
wifi_dummy               806  0
amlvideodri            12066  0
videobuf_res            5322  1 amlvideodri
videobuf_core          16549  2 amlvideodri,videobuf_res
videodev              131761  1 amlvideodri
dwc_otg               233217  0
fbcon                  38031  0
bitblit                 4468  1 fbcon
softcursor              1168  1 bitblit
font                    7327  1 fbcon

Can somebody help?

Did you already opened your device to find what demodulator chip is present?

No i didn’t. It’s not my device.
Can I find something when I boot into android?

Hi guys,
My neighbor also own this device. It works great with CoreELEC but the dvb drivers are missing. Will be nice if someone help us with this issue. I know that none of developers own this device but if you want guys we can help and donate one device to someone.
What do you think?

I did some testing on a android custom kernel but I can’t get anything.
Anyway I’ll describe how I flash the kernel, it may be useful to someone else.
First copy the boot.img to a usb flash drive, and connect it.
Then boot into u-boot and using an usb to uart adapter run the following commands:
usb start
usb_update boot boot.img
reset

GTMedia GTC S905D.

Extract you dtb.img original in OS Android, save and copy to sdcard and test…

dd if=/dev/dtb > /storage/emulated/0/Download/dtb.img

Or in usbstick see mounted: mount
/dev/fuse /storage/12A1-6017

dd if=/dev/dtb > /storage/12A1-6017/dtb.img

################################################################
root@wetekplay2:/ # dd if=/dev/dtb > /storage/12A1-6017/dtb.img
512+0 records in
512+0 records out
262144 bytes transferred in 1.447 secs (181163 bytes/sec)
root@wetekplay2:/ #
root@wetekplay2:/ # ls -al /storage/12A1-6017/dtb.img
-rwxrwx–x root sdcard_rw 262144 2019-04-19 22:21 dtb.img
################################################################

CoreElec don’t show tuners, but using UART log (Android), I see DVB part:

[ 3.562144@0] aml dvb init
[ 3.564294@0] DVB: probe amlogic dvb driver
[ 3.568295@0] DVB: dmx rst ctl = ffffffc0650e9340
[ 3.572963@0] DVB: asyncfifo rst ctl = ffffffc0650e93c0
[ 3.578175@0] DVB: ahbarb0 rst ctl = ffffffc0650e9440
[ 3.583131@0] DVB: uparsertop rst ctl = ffffffc0650e94c0
[ 3.588382@0] DVB: ts0: parallel
[ 3.591673@0] DVB: ts0_control: 0x0
[ 3.595023@0] DVB: registering new adapter (amlogic-dvb)
[ 3.600932@0] DVB: demux init
[ 3.603273@0] soft reset index = 0, pid = 8191
[ 3.608130@0] DVB: demux init
[ 3.611049@0] DVB: demux init
[ 3.613672@0] DVB: async fifo 0 buf size 481280, flush size 60160
[ 3.619646@0] DVB: async fifo 1 buf size 481280, flush size 60160
[ 3.626371@0] FE: cannot find resource “tuner0”
[ 3.630081@0] input input1: key 116 up
[ 3.633752@0] FE: cannot find resource “atv_demod0”
[ 3.638599@0] FE: cannot find resource “tuner1”
[ 3.643123@0] FE: cannot find resource “atv_demod1”
[ 3.647890@0] FE: cannot find resource “dtv_demod1”
[ 3.652755@0] amlogic-dvb dvb.51: DVB: registering adapter 0 frontend 0 ()…
[ 3.660332@0] Amlogic Demod DVB-T/C DebugIF Init
[ 3.664568@0] Amlogic Demod DVB-T/C DebugIF Init ok----------------

Here dtb (log Android)

  Amlogic multi-dtb tool
  Multi dtb detected
  Multi dtb tool version: v2 .
  Support 2 dtbs.
    aml_dt soc: gxl platform: p231 variant: 2g
    dtb 0 soc: gxl   plat: p231   vari: 1g
    dtb 1 soc: gxl   plat: p231   vari: 2g
  Find match dtb: 1

Here full Android log using UART:

https://www.mediafire.com/file/vykvrsvatpgjlr6/GTC_ANDROID_2019-07-04_13-32-38.log/file
https://mega.nz/#!mRUjWAZQ!e8dA9kQ2SW3kdoTbTBmp85wCO0nSIWTtwHUWg0qLs-4

Using OpenVision image test for K1pro (enigma2), show only Availink 6862 (DVB-T), no wifi, no RJ45

See the log please, @afl1

1 Like

I will love to have Coreelec in my GTMedia GTC. Any progress to it?

I hate the official ROM.

Hello all, first of all want to thanks to All coreelec team and all Open Source community for the great work in Linux development.
My question is related whit “GTMedia GTC S905D” and the Device Trees need to use.
Do I choose the most related chip the box use? ex: Beelink Mini MXIII S905 2G (Realtek WiFi) gxbb_p200_2G_1Gbit_RealtekWiFi?
Any one test it yet to this android box?
Is the tv tunners will work whit last coreeelec distro?

All the best for core team and thanks!

Hello my friend do you find some solution for the issue of the internal tuners ?

You can try several dtbs and see if the tuner is detected. For what I’ve read in the topic it seems it’s not the case. If you don’t own the box yet the solution is to buy a supported box or use external usb tuners.

Here are pictures of my box, maybe it is newer revision, decoder chip is visible.


1 Like

Sony D2856ER (CXD2856)
https://www.yoycart.com/Product/568530789547/

After Linux 4.13

ddbridge version 0.5, enhanced with additional frontend hardware support
Supports CineCTv6 PCIe bridges and DuoFlex C/T modules based on the STV0367/TDA18212 demodulator/tuner controllers
Supports the full range of CTv7 PCIe bridges and DuoFlex C/T modules (both: CT2, C2T2 and C2T2I) based on the **CXD28xx**/TDA18212 demodulator/tuner controllers
Supports the full range of MaxA8 Octotuner cards (all CT2, C2T2 and C2T2I variants, the cards are basically quad CTv7 boards, equipped with the **CXD28xx**/TDA18212 chips)

https://git.linuxtv.org/media_tree.git/commit/?id=42b6515fd55d5c4dbeb8183ad18b289182e80456