PDA

Archiv verlassen und diese Seite im Standarddesign anzeigen : Audioniek Images: download



Audioniek
31.03.2019, 16:49
Hello everybody,

Below are the flash images of January 2024. Compared to the last batch of images of June 2022, these have been built from the branch release-8.3 of the OpenPLi-git, rather than the develop branch and represent the very last OpenPLi release not using Python 3. Apart from that, the following has been changed:

OpenPLi: commit 2d6416e (June 25th, 2023, release-8.3 branch)

Other packages:


alsa-lib -> 1.2.9, alsa-util -> 1.2.9
busybox -> 1.36.1
ethtool -> 6.2
expat -> 2.50
ffmpeg 2.X.X -> 2.8.22
hdparm -> 9.65
jpeg-turbo -> 2.1.4
libcurl -> 8.2.0
libfribidi -> 1.0.12
libjpeg-turbo-2 -> 2.1.5.1
libpng -> 1.6.39
libpsl -> 0.21.2
minidnla -> 1.3.2
ncurses -> 6.1
openssh -> 9.3p2.1
pugixml -> 1a9a41b
sysvinit -> 3.08
util-linux -> 2.38.1
util-linux -> 2.39.2
zdata -> 2022g
zlib -> 1.3

Note: several packages have jumped more than one version level.

Installation instructions are here in posting #20 (http://www.hdmedia-universe.com/board/showthread.php?11200-Audioniek-Images-general-info/page2),


June 2022 images are also here (http://www.hdmedia-universe.com/board/showthread.php?11200-Audioniek-Images-general-info/page2), in posting #19.

Links for flash images:
16655
16656
16657
16658
16659
16660
16661
16662
16663
16664
16665

January 2024 USB images are in the next post below.

Remaining backup USB images of June 2022:
16666
16667
16668
16669
16670

Update 30-01-2024
Two plugins (OpenWebIF and Networkbrowser report a problem. I will try a fix this in the coming days.

Important Notice
For the time being, this will be the last of the regular releases of the images presented here. If ever, the next batch will appear when I have got Python 3 running on SH4 to my satisfaction.

Have fun,

Audioniek.

Audioniek
31.03.2019, 16:52
Here are the USB images of January 2024:
16671
16673
16672
16674
16675
16676
16677
16678
16679
16682
16683
16684
16685
16686

Note: ufs922 USB has not been provided, as it has not been tested, and adds little compared to the "flash" version. Let me know if you want it built.


Regards,

Audioniek.

Schaagi
01.04.2019, 12:05
Hi Audioniek

Thank you for your new images. I've tested the USB version for the UFS 912 receiver.
After starting, the VFD-Display shows LOAD 9, then FW missing and stops at Load 6.

Best regards
Schaagi

ainouna
01.04.2019, 12:49
thank you Audioniek
but
hs7429 Flash

boot OF---

- - - Aktualisiert - - -


hs7429 FLASH
error
'0▒(Re)start USB...
Front USB: scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
Rear USB: scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
(Re)start USB...
Front USB: scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
Rear USB: scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
stopping USB..


NAND read: device 0 offset 0x500000, size 0x300000

Reading data from 0x7ff800 -- 100% complete.
3145728 bytes read: OK
INIT: version 2.88 booting
Fortis HS7429 Enigma2
[rcS] Init frontpanel
[rcS] LOAD 10
[mountvirtfs] Mount /dev in tmpfs
[mountvirtfs] Copying device nodes to /dev
[rcS] Starting automounter
Starting automounter: /media/usb.
[rcS] Starting DEBUG Interface
[mountall] Mounting local filesystems...
mount: mounting LABEL=RECORD on /hdd failed: No such file or directory
Cleaning /tmp.
Hostname: hs7429.
[rcS] Starting telnetd with autologin
[rcS] Init stmfb (LOAD 9)
[rcS] Loading modules
[rcS] Load audio firmware (LOAD 8)
[rcS] Load video firmware (LOAD 7)
[rcS] Init embx (LOAD 6)
[rcS] Init AVS (LOAD 5)
[rcS] Init player 191 (LOAD 4)
[rcS] Init frontend
[rcS] Init CI & cardreader
[rcS] Full feature pti
[rcS] Init player2 (LOAD 3)
[rcS] Init HDMI-CEC
[rcS] Init remote control (LOAD 2)
[evremote2] Model: 'hs7429'
[evremote2] vBoxType: 8 (hs7429)
[evremote2] Input device name: "TDT RC event driver"
[evremote2] Remote selected: Fortis RemoteControl
[evremote2] RemoteControl Map:
Keyname Keyword KeyCode
--------------------------------------
MENU - 04 - 139
RED - 4B - 398
GREEN - 4A - 399
YELLOW - 49 - 400
BLUE - 48 - 401
EXIT - 1C - 102
TEXT - 0D - 388
EPG - 08 - 365
REWIND - 58 - 168
FASTFORWARD - 5C - 208
PLAY - 55 - 207
PAUSE - 07 - 119
RECORD - 56 - 167
STOP - 54 - 128
STANDBY - 0A - 116
MUTE - 0C - 113
CHANNELUP - 5E - 104
CHANNELDOWN - 5F - 109
VOLUMEUP - 4E - 115
VOLUMEDOWN - 4F - 114
INFO - 06 - 358
OK - 1F - 352
UP - 00 - 103
RIGHT - 02 - 106
DOWN - 01 - 108
LEFT - 03 - 105
RECALL - 09 - 138
ZOOM - 53 - 372
VFORMAT - 0E - 371
RESOLUTION - 0F - 375
TVRADIO - 1A - 373
SLEEP - 1E - 409
OPEN - 40 - 394
FAV - 41 - 364
CHECK - 42 - 353
UPUP - 43 - 414
DOWNDOWN - 44 - 415
NEXT - 4C - 407
LAST - 50 - 412
PIP - 51 - 357
SWAP - 52 - 354
LIST - 0B - 370
0BUTTON - 10 - 11
1BUTTON - 11 - 2
2BUTTON - 12 - 3
3BUTTON - 13 - 4
4BUTTON - 14 - 5
5BUTTON - 15 - 6
6BUTTON - 16 - 7
7BUTTON - 17 - 8
8BUTTON - 18 - 9
9BUTTON - 19 - 10
--------------------------------------
[evremote2] Frontpanel Map:
Keyname Keyword KeyCode
--------------------------------------
STANDBY - 00 - 116
OK - 06 - 352
MENU - 05 - 139
VOLUMEUP - 03 - 115
VOLUMEDOWN - 04 - 114
CHANNELUP - 01 - 104
CHANNELDOWN - 02 - 109
--------------------------------------
[evremote2] Supports Long KeyPress: yes
[evremote2 fortis] Period = 10, delay = 140
[evremote2] Using period = 10 delay = 140
[showiframe] showSinglePic /boot/bootlogo.mvi
Deconfiguring network interfaces... [showiframe] VIDEO_SELECT_SOURCE MEMORY (Success)
[showiframe] VIDEO_PLAY (Success)
[showiframe] VIDEO_CONTINUE: (Success)
[showiframe] VIDEO_CLEAR_BUFFER: (Invalid argument)
ifdown: interface eth1 not configured
ifdown: interface wlan0 not configured
done.
[rcS] Starting DHCP
Starting DHCP client: udhcpcudhcpc: started, v1.30.1
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending select for 192.168.1.7
udhcpc: lease of 192.168.1.7 obtained, lease time 259200
route: SIOCDELRT: No such process
adding dns 192.168.1.1
.
Setting up IP spoofing protection: rp_filter.
Configuring network interfaces... udhcpc: started, v1.30.1
udhcpc: sending discover
udhcpc: sending select for 192.168.1.7
udhcpc: lease of 192.168.1.7 obtained, lease time 259200
route: SIOCDELRT: No such process
adding dns 192.168.1.1
ip: SIOCGIFFLAGS: No such device
ip: SIOCGIFFLAGS: No such device
done.
[rcS] Init WLAN: None.
[rcS] Do extras (LOAD 1)
[rcS] No inadyn
[rcS] No OpenSSH
[rcS] Set internet time
ntpd: setting time to 2019-04-01 12:44:05.348272 (offset +607430625.263514s)
Current system time: 12:44:05 01-04-2019 (local)
Front panel time set to: 12:44:05 01-04-2019 (local)
Note: /proc/stb/fp/rtc_offset set to: +7200 seconds.
[rcS] Init portmap & ftp
Starting portmap daemon....
Starting FTP server: vsftpd.
[rcS] Loading E2
[rcS] Entering e2 main loop
PYTHONPATH: /usr/lib/enigma2/python
DVB_API_VERSION 5 DVB_API_VERSION_MINOR 3
ENIGMA_DEBUG_LVL=4
[Avahi] Not running yet, cannot browse for type _e2stream._tcp.
[eInit] + (1) Background File Eraser
[eInit] + (5) Tuxtxt
[eInit] + (8) graphics acceleration manager
STMFB accel interface available

[eInit] + (9) GFBDC
[fb] 16384k total video memory
8284k usable video memory
[gFBDC] resolution: 1280x720x32 stride=5120, 4684kB available for acceleration surfaces.
[eInit] + (9) gLCD
[eFbLCD] /dev/fb1: No such device
[eFbLCD] framebuffer /dev/fb1 not available
[eDboxLCD] No oled0 or lcd0 device found!
[eLCD] (32x32x8) buffer 0x6f0948 1024 bytes, stride 32
[gLCDDC] resolution: 32x32x8 stride=32
[eInit] + (9) Font Render Class
[FONT] initializing lib...
[FONT] loading fonts...
[FONT] Intializing font cache, using max. 4MB...
[eInit] + (10) gRC
[gRC] thread created successfully
[eInit] + (15) eWindowStyleManager
[eInit] + (20) DVB-CI UI
[eInit] + (20) UHF Modulator
[eRFmod] couldnt open /dev/rfmod0: No such file or directory
[eInit] + (20) RC Input layer
[eInit] + (20) misc options
[eInit] + (20) AVSwitch Driver
[eAVSwitch] failed to open /dev/dbox/fp0 to monitor vcr scart slow blanking changed: No such file or directory
[eInit] + (21) input device driver
[eInputDeviceInit] adding device /dev/input/event0
[eRCInputEventDriver] devicename=TDT RC event driver
[eRCInputEventDriver] devicename=TDT RC event driver
[eRCInputEventDriver] devicename=TDT RC event driver
[eRCDeviceInputDev] device "TDT RC event driver" is a remotecontrol
[eInputDeviceInit] adding device /dev/input/event1
[eRCInputEventDriver] devicename=TDT RC event driver
[eRCInputEventDriver] devicename=TDT RC event driver
[eRCInputEventDriver] devicename=TDT RC event driver
[eRCDeviceInputDev] device "TDT RC event driver" is a remotecontrol
[eInputDeviceInit] adding device /dev/input/event2
[eRCInputEventDriver] cannot open /dev/input/event2: No such device
[eRCDeviceInputDev] device "" is a remotecontrol
[eInputDeviceInit] adding device /dev/input/event3
[eRCInputEventDriver] cannot open /dev/input/event3: No such device
[eRCDeviceInputDev] device "" is a remotecontrol
[eInputDeviceInit] Found 4 input devices.
[eInit] + (22) Hdmi CEC driver
[eHdmiCEC] detected physical address change: 1000 --> 5D0E
[eHdmiCEC] send message 84 5D 0E 2A
[eInit] + (30) eActionMap
[eInit] + (35) CI Slots
[CI] scanning for common interfaces..
[CI] Slot 0: reset requested
[CI] Slot 1: reset requested
[CI] Slot: 0 setSource: A
[CI] Slot: 1 setSource: A
[CI] done, found 2 common interface slots
[CI] Streaming CI routing interface not advertised, assuming DVR method
[CI] Streaming CI finish interface not advertised, assuming "tuner" method
[eInit] + (35) CA handler
[eInit] + (40) eServiceCenter
[eServiceCenter] settings instance.
[eInit] + (41) eServiceFactoryDVD
[eInit] + (41) eServiceFactoryWebTS
[eInit] + (41) eServiceFactoryTS
[eInit] + (41) eServiceFactoryHDMI
[eInit] + (41) eServiceFactoryM2TS
[eInit] + (41) eServiceFactoryFS
[eInit] + (41) eServiceFactoryDVB
[eInit] + (41) Encoders
[eInit] + (41) Stream server
[eServerSocket] ERROR on bind: Address already in use
[eServerSocket] ERROR on bind: Address already in use
[Avahi] Not running yet, cannot register type _e2stream._tcp.
[eInit] reached rl 70
[eDVBDB] ---- opening lame channel db
[eDVBDB] reading services (version 4)
[eDVBDB] loaded 403 channels/transponders and 5981 services
eDVBSatelliteEquipmentControl::clear()
[eDVBResourceManager] scanning for frontends..
[eDVBFrontend0] opening frontend
[eDVBFrontend0] opening frontend
[eDVBFrontend0] frontend 0 has DVB API 503
[eDVBFrontend0] close frontend
[eDVBAdapterLinux] get demux 0
[eDVBAdapterLinux] get demux 1
[eDVBResourceManager] found 1 adapter, 1 frontends(1 sim) and 2 demux
[eDVBLocalTimeHandler] Use valid Linux Time :) (RTC?)
[eEPGCache] Initialized EPGCache (wait for setCacheFile call now)
[MAIN] Loading spinners...
[MAIN] found 12 spinners.
[MAIN] executing main
[setIoPrio] best-effort level 3 ok
[CamControl] No softcam link? /etc/init.d/softcam
[eDVBFrontend] Failed to open /dev/dbox/fp0
[Misc_Options] 12Vdetect cannot open /proc/stb/misc/12V_output: No such file or directory
[HardwareInfo] Scanning hardware info
Traceback (most recent call last):
File "/usr/lib/enigma2/python/mytest.py", line 22, in <module>
import Components.SetupDevices
File "/usr/lib/enigma2/python/Components/SetupDevices.py", line 1, in <module>
File "/usr/lib/enigma2/python/Components/config.py", line 4, in <module>
File "/usr/lib/enigma2/python/Components/Harddisk.py", line 4, in <module>
File "/usr/lib/enigma2/python/Components/SystemInfo.py", line 42, in <module>
File "/usr/lib/enigma2/python/Tools/HardwareInfo.py", line 38, in __init__
IOError: [Errno 2] No such file or directory: '/usr/local/share/enigma2/hw_info/hw_info.cfg'
[eDVBDB] ---- saving lame channel db
[eDVBDB] saved 403 channels and 5981 services!
[showiframe] end
[showiframe] VIDEO_SELECT_SOURCE DEMUX (Invalid argument)
[eDVBResourceManager] release cached channel (timer timeout)
[eDVBLocalTimeHandler] set RTC to previous valid time
[eInit] - (41) eServiceFactoryDVD
[eInit] - (41) eServiceFactoryWebTS
[eInit] - (41) eServiceFactoryTS
[eInit] - (41) eServiceFactoryHDMI
[eInit] - (41) eServiceFactoryM2TS
[eInit] - (41) eServiceFactoryFS
[eInit] - (41) eServiceFactoryDVB
[eInit] - (41) Encoders
[eInit] - (41) Stream server
[eInit] - (40) eServiceCenter
[eServiceCenter] clear instance
[eInit] - (35) CI Slots
[eInit] - (35) CA handler
[eInit] - (30) eActionMap
[eInit] - (22) Hdmi CEC driver
[eInit] - (21) input device driver
[eInit] - (20) DVB-CI UI
[eInit] - (20) UHF Modulator
[eInit] - (20) RC Input layer
[eInit] - (20) misc options
[eInit] - (20) AVSwitch Driver
[eInit] - (15) eWindowStyleManager
[eInit] - (10) gRC
[gRC] waiting for gRC thread shutdown
[gRC] thread has finished
[eInit] - (9) GFBDC
[eInit] - (9) gLCD
[eInit] - (9) Font Render Class
[eInit] - (8) graphics acceleration manager
[eInit] - (5) Tuxtxt
[eInit] - (1) Background File Eraser
[eInit] reached rl -1
[rcS] e2 ended <- return value: 0
[rcS] E2 ERROR
INIT: Sending processes the TERM signal
Sending all processes the TERM signal...done.

Audioniek
01.04.2019, 23:03
@Schaagi: has been fixed; link refreshed.
@ainouma: will look at this tomorrow (2/4).

Regards,

Audioniek.

Schaagi
02.04.2019, 11:12
Hi Audioniek
New image for UFS 912, USB version from April 1st tested:
LOAD 9 - 2
LOADING ENIGMA2
UFS ENIGMA2
E2 error
REBOOT

Regards Schaagi

ainouna
02.04.2019, 11:56
thank you Audioniek
hs7429 USB
boot OF

samkooke
02.04.2019, 18:53
good evening Audioniek problem for hs7119 i have a same problem for the compilation E2Error thanks.

Audioniek
02.04.2019, 19:55
Hello everybody,

It looks like all images suffer from the problem first reported in post #4. If have meanwhile fixed it and will be building new images starting tomorrow.

It is possible to fix it by hand. To achieve this, do the following:


Download the zip-file below and extract it. You get a file HardwareInfo.py;
Start the receiver with a serial connection ready. Press Ctrl-C as soon as E2 tries to start. You should be at a command prompt in the serial programme;
At the end of the rcS output you can see the IP-number assigned;
Open an ftp-rpgram like FileZilla and connect to the receiver;
In the directory /usr/lib/enigma2/python/Tools remove the file HardwareInfo.pyo;
Into the same directory, copy the file HardwareInfo just extracted;
Restart the receiver. E2 should now run and show the startwizard.

When you use an USB image from a .tar.gz, you can try and remove HardwareInfo.pyo from the archive and replace it with the unpacked file.

Regards,

Audioniek.

Download link: 15364

ainouna
03.04.2019, 11:38
HI Audioniek.
It took me a long time,
but it's finally done!
thank you Audioniek.:)

Schaagi
03.04.2019, 15:30
I've deleted the Hardwareinfo.pyo in the existing image and copied the new Hardwareinfo.py
at the same place.
Now it works, thank you.

Schaagi

ainouna
07.04.2019, 12:25
HI Audioniek.
It took me a long time,
but it's finally done!
thank you Audioniek.

fullbackup plugins
to keep enigma2
please .....:)

dreamce
11.04.2019, 16:46
spark_Audioniek_enigma2_gst-epl3_flash_P217_CDK-rev1165.zip (http://www.hdmedia-universe.com/board/attachment.php?attachmentid=15374&d=1554744314)
Does not read external USB memory files

atlas35
16.04.2019, 22:19
spark_Audioniek_enigma2_gst-epl3_flash_P217_CDK-rev1165.zip (http://www.hdmedia-universe.com/board/attachment.php?attachmentid=15374&d=1554744314)
Does not read external USB memory files

hs7110 or hs7810a Does not read external USB memory files

Many thanks for your work @Audionik master...

azote
01.05.2019, 17:30
Hi audionek .
Usb install your dev image uan boot ok, but remote do not work. Therefore, I have not been able to prove anything else about the operation of the system
thanks for your work

jaro44
22.05.2019, 08:23
hi audioniek,
I have built an image for cuberevo3000hd and there is a problem with the micom driver after your changes:

INIT: version 2.88 booting


[rcS] Start
CubeRevo 3000HD Enigma2
[rcS] Init frontpanel
insmod: can't insert '/lib/modules/cuberevo_micom.ko': unknown symbol in module, or unknown parameter
/etc/init.d/rcS: line 21: can't create /dev/vfd: No such device or address
[rcS] LOAD 10
[mountvirtfs] Mount /dev in tmpfs
[mountvirtfs] Copying device nodes to /dev
cp: can't stat '/dev/initctl': Input/output error
[rcS] Starting DEBUG Interface
[mountall] Mounting local filesystems...
mount: mounting LABEL=RECORD on /hdd failed: No such file or directory
mkdir: can't create directory '/var/lib/urandom': Input/output error
Cleaning /tmp /var/run /var/lock.
Hostname: cuberevo_3000hd.
[rcS] Starting telnetd with autologin
[rcS] Init stmfb (LOAD 9)
/etc/init.d/rcS: line 46: can't create /dev/vfd: No such device or address
offset key len data
-------------------------------------


EDIT:
I changed patches kernel config and setup for 3000hd from mini2, built from scratch and now it works.
3000hd is the same tuner as mini2 only with another avs (mini2 has 6412 and 3000hd has 6418) - please change it in rcS

sidjobs
02.06.2019, 04:11
dear Audioniek
i have a atevio 700 and actualy i use this image M43851_atevio700_v1-90_nightly_UPDATEUSB_g985.ird " internal" also i have a comunication problem with AAF Recovery tool
so i need your opinion if i can use your image octagon1008_Audioniek_enigma2_gst-epl3_USB_CDK-rev1201 internal IRD and i change only the ID to Octagon with resseler changer?
thanqs in advance i appreciate that.

Audioniek
02.06.2019, 12:27
You confuse two things: there is a difference between a flash image that run in the flash memory on your receiver and a USB-image, that run on a USB stick connected to the receiver. A flash file has the extension .ird in this case, a USB image consists of a .tar.gz you have to unpack and install on the stick to be used.

The short answer is therefore: no, unfortunately you cannot. The long answer is this: try and get AAF recovery to work. Then you can in install the TDT Maxiboot loader and run a USB image.

Regards,

Audioniek.

tanaka
14.06.2019, 01:51
hs7420 rev. 1201 is not loading, even root.img can't be opened or extracted with 7zip (Header error), Please check.

Audioniek
14.06.2019, 17:50
I can download and extract the file you mention without problems. Try another extractor or try to download it another time.

Regards,

Audioniek.

tanaka
15.06.2019, 20:10
extracting the zip is ok, but extracting "root.img" is showing the header error even after downloading today again.

I mean the header corruption is in "root.img" itself.

Audioniek
17.06.2019, 19:01
Hello tanaka,

I have rebuilt the hs7420 and updated the link in post #1. I can open both the .zip file and the root.img in it with 7zip. Please note I cannot test the hs7420: it is the only Fortis box I do not have access to.

Regards,

Audioniek.

tanaka
19.06.2019, 12:23
Hello tanaka,

I have rebuilt the hs7420 and updated the link in post #1. I can open both the .zip file and the root.img in it with 7zip. Please note I cannot test the hs7420: it is the only Fortis box I do not have access to.

Regards,

Audioniek.


Thanks Audioniek for your effort, It works now.

I have one issue for now, my wifi usb is not detected (RT5370), Anyway to fix as I can't even use DCC-E2?

ainouna
17.08.2019, 15:46
Thanks Audioniek for your effort
hs7429_Audioniek_enigma2_gst-epl3_USB_P217_CDK-rev1251
boot OFF

sadaghiani
22.08.2019, 09:28
hs7429_Audioniek_enigma2_gst-epl3_USB_P217_CDK-rev1251



FrTs
'0(Re)start USB...
Front USB: scanning bus for devices... 3 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
system volume information/
3756854 uimage
268435456 root.img


2 file(s), 1 dir(s)


reading uImage
.................................................. .................................................. .................................................. .................................................. .................................................. .................................................. .................................................. ................
ret=> 3756854



----------------------------------------------------------
Bpanther survey results
https://forum.mbremer.de/viewtopic.php?f=21&t=2883
For them, it is a problem with the kernel settings

Drielander
30.09.2019, 17:21
Da ich zwei Töpfe besitze, habe ich einen heute mit dem aktuellen Image tf7700_Audioniek_enigma2_gst-epl3_flash_P217_CDK-rev1251 versorgt.
So sehr ich das/mein letzes HDMU-Image schätze, so ist das hier doch etwas moderner.

Und wieder bin ich über ein paar "Stufen" gestolpert:
- "Untertitel für Gehörlose" sollte ausgeschaltet sein
- größeres EPD, das sich nicht nur auf den gewählten Kanal beschränkt und den für die nächsten Tage anzeigt, sondern das von HDMU bkannte große EPG, das alle Kanäle (auf mehrere Seiten verteilt) in einer Übersicht anzeigt.

Wer kann mir da ad-hoc weiter helfen?

Gruß

Drielander
30.09.2019, 21:31
Nachtrag:

Die "Untertitel für Gehörlose" sind inzwischen abgestellt - bzgl. EPG bin ich noch nicht weiter.
Auch beim Ton habe ich einige Probleme: bei einigen Kanälen wird der Ton nur kurz nach Anwahl, gar nicht oder nur durch vor/zurück wiedergegeben.
Dazu stellte ich eben bei einem Kanal (One HD) fest, dass die Originalsprache des Fims kam. Will ich die Tonspuren 1-4 mit einer bestimmten Auswahl Sprachen belegen, finde ich bei Tonspur 1 kein Deutsch, obwohl es zwischen französisch & griechisch liegen sollte - so zumindest bei den anderen Tonspuren.

Drielander
04.10.2019, 18:10
Leider bin ich noch nicht weiter gekommen.
Nachdem ich (hoffentlich) die Untertitel für Hörgeschädigte halbwegs abgestellt habe, nervt noch die Audiodescription (Kommentar für Sehbehinderte), die bei einigen Kanälen aktiv ist. Wie schalte ich die wo ab?
Ich bin die Menüs rauf und runter abgegangen, aber wie ich ein großes EPG einstelle, habe ich noch immer nicht gefunden.
Gibt es nirgendwo eine Konfigurationsanleitung für OpenPli?

sadaghiani
15.10.2019, 21:21
7429
The usb file is incomplete and reads like a flash file

Audioniek
19.10.2019, 17:52
I have downloaded the file and it is perfectly OK. It indeed looks like a flash file, but it is not. The uImage in the file is a special one, that loads and mounts the file rootfs.img from the USB stick. Fortis flash files have the extension .ird.

Regards,

Audioniek.

sadaghiani
22.10.2019, 20:40
hs7429
The uImage file loads and mounts same .ird And shows on the recive display rd then shows error

setifstar
25.10.2019, 17:35
Hi Audioniek

Thank you for your new images. I've tested the USB version ( hs7819_Audioniek_enigma2_gst-epl3_USB_P217_CDK-rev1280.zip (http://www.hdmedia-universe.com/board/attachment.php?attachmentid=15608&d=1571043151))for the hs7819 (http://www.hdmedia-universe.com/board/attachment.php?attachmentid=15583&d=1571041823) receiver.
After starting, the VFD-Display shows Boot and the receiver not started.

Audioniek
26.10.2019, 13:31
@sadaghiani: I have replaced the image file with a tested new one. You were right: the file was not OK.

@setifstar: I will have a look.

Regards,

Audioniek.

sadaghiani
27.10.2019, 09:44
7429
err 0x70
-------------------
transcend 8g
jetflash 350
-------------------
The kernel settings (uimage) seem to be incorrect

Audioniek
27.10.2019, 20:37
@setifstar:If the display stays at boot, the USB kernel starts but cannot read rootfs.img. In my experience it is very hard to find a USB stick that works 100% of the time. Usually I have more success after several power ups: sooner or later the kernel does not switch off the USB power and the whole lot starts up. Use older USB sticks of 512 MByte to 2Gbyte in capacity to get the best results.

@sadaghiani: If have tested the flash version and it flashes perfectly, it also starts up the way it is intended. My gut feeling says you are trying to flash the USB uImage into flash memory: this will not fit and indeed yield a correct Err 0x70. Please read the installation instructions carefully.

Regards,

Audioniek.

sadaghiani
27.10.2019, 20:50
I mean the usb version Which has this error
I haven't tested the Flash version yet

Audioniek
28.10.2019, 12:55
I understand now. Probably your USB stick is not recognized and/or USB boot is switched off. The receiver will then boot from flash, but that is corrupt for some reason, leading to Err 0x70 (Kernel File system error).

The sequence of displays on the front panel should be:

L 7.36 or L 7.37
SCAN USB (check for an USB stick with uImage on it)
R 0 (if found read and start uImage from USB)
BOOT (uImage is started and tries to mount rootfs.img)
.... (E2 mesages)

If SCAN USB does not appear, USB boot is off.

Regards,

Audioniek.

sadaghiani
28.10.2019, 14:19
L 7.36 or L 7.37 ok
SCAN USB ok
R 0 ok
BOOT fault - stop on boot
...................................
transcend 2g

sadaghiani
28.10.2019, 18:17
HS 7429
-------------------------
I installed the flash version
Congratulations on this project
And thank you
-------------------------
So far everything looks great

setifstar
29.10.2019, 18:37
HS 7819
-------------------------
When I want installed the flash version :Error 20 or en :20 on front vfd

sadaghiani
30.10.2019, 16:20
HS 7429 Flash version
-----------------------------------------
Very smooth image without problems
------------------------
Please add functional plugins such as:
-PIP
-control panel similar pkteam image
-emulator
& ......
----------------------
overscan wizard crash
keyboard map incomplete : Some keys don't work like that Recall key

ainouna
08.11.2019, 13:54
octagon -1008g+se+= hs7429
With Original Firmware
120 mb free
and with audioniek flash
30 mb free
why:confused:

sadaghiani
04.12.2019, 16:43
Neutrino Tangos HS 7429 flash version
-------------------------------------------
https://mega.nz/#!PioVgQZB!PIv0-7rFHg0GlorSrWis_TMtv-GJ1E7b70LLrBE4j8I
-----------------------------------------
Very very smooth image without problems

ainouna
05.12.2019, 12:49
thank you sadaghiani
but it only opens the clear chains

svn
06.12.2019, 12:20
Where USB images for December?

sadaghiani
06.12.2019, 15:46
neutrino tangos rev1331 HS 7429
------------------------------------------------------------------------------------------
https://mega.nz/#!mz4CnIDK!RBUQaKxJ2jJDruhp_D9BtfZHPxtL5zaEf16H7b9 irn4
------------------------------------------------------------------------------------------
scroling vfd is inactive
lua plugin same neutrino and ard meditek didnt work

Audioniek
06.12.2019, 15:50
@svn: The December USB images will be built and posted during the coming weekend.

Regards,

Audioniek.

zozman
07.12.2019, 20:35
hs7429

flash version : stuck on boot

zozman
08.12.2019, 22:41
hs7429

usb version : stuck on boot

setifstar
09.12.2019, 14:52
Fortis hs 7819
hs7819_Audioniek_enigma2_gst-epl3_flash_P217_CDK-rev1328.zip (http://www.hdmedia-universe.com/board/attachment.php?attachmentid=15655&d=1575447146)
================================================== ======
L7.27
Scan
Ld
Load
Ld 10-9-8-7-6-5-4-3-2-1
Ld E2
Err

chaban
11.12.2019, 07:33
HS-7420
BOOT PROBLEM...

ret=> 3535748
## main.c Error: "hwnfconf" not defined

--={ Load Enigma2 from USB }=--


[init] Wait until /dev/sda exists
[init] Time out on wait for /dev/sda, exiting...


BusyBox(2019-12-08 13:28:39 CET) built-in shell (ash)


sh: can't access tty; job control turned off

Audioniek
11.12.2019, 12:25
@setifstar:

You are correct. Will look into it and upload corrected image. May take a few days though, as I am very busy at the moment. Thank you for the feedback.

Regards,

Audioniek.

chaban
18.12.2019, 12:23
USB IMAGE HS-7810... it is OK on HS-7420.....

setifstar
02.02.2020, 18:11
HI Audioniek,
First observation after installation,
Image '' (http://www.hdmedia-universe.com/board/attachment.php?attachmentid=15704&d=1580591431)hs7819_Audioniek_enigma2_gst-epl3_flash_P217_CDK-rev1347'' (http://www.hdmedia-universe.com/board/attachment.php?attachmentid=15704&d=1580591431)works correctly.

BLUE BUTTON DOES NOT WORK FOR FAVORITES LIST

Congratulations

ainouna
03.02.2020, 11:00
Hi Audioniek
starting problem
ret=> 3757377
--={ Load Enigma2 from USB }=--
[init] Wait until /dev/sda exists
[init] Time out on wait for /dev/sda, exiting...
BusyBox(2020-01-31 2143 CET) built-in shell (ash)
sh: can't access tty; job control turned off
/ #
Regards
ainouna

Audioniek
03.02.2020, 14:38
Hello ainouna,

What I have found in the past that the USB stick used to boot E2 from USB on HS7XXX is extremely critical. That is probably the cause. In addition, the problem is complicated by the fact that the power supply to the stick is switched off at a critical point in he boot process, and not always switched back on. This is a problem in the bootloader I have not had time for to address, hampered by the fact I do not have the added code of the USB loader 6.X6/6.X7 and the 3rd generation variants (7.XX). I have experimented with delays and switching the supply back on, but have not found a solution yet. Even a suitable stick may need several attempts so persistence is maybe the best approach for the moment.

Regards,

Audioniek.

- - - Aktualisiert - - -


BLUE BUTTON DOES NOT WORK FOR FAVORITES LIST

Assuming you mean the blue key in the channel list display: I will check. The FAV key should access the favourites list directly though (at least it is intended to),

Regards,

Audioniek.

setifstar
05.02.2020, 19:15
Image Audioniek and emu oscam:


when the image freezes, the video returns but not the sound.
You have to zap on another channel to get the sound again.

setifstar
06.02.2020, 18:00
Image Audioniek and emu oscam:

When you turn off the receiver and then restart it, oscam does not start automatically, it must be done manually for it to work.

Audioniek
08.02.2020, 17:22
setifstar: please note that I do not support scrambled stuff, for the simple reason there so many variants and versions in softcams as well as scrambling methods, I simply cannot test it. Sorry.

Regards,

Audioniek.

samkooke
09.02.2020, 16:54
hello Audioniek i can't compile for hs7429 i get this error message.

Start build of driver-symlink.
cp: cannot stat '/home/samkooke/Bureau/x/buildsystem/driver/stgfb/stmfb/linux/drivers/video/stmfb.h': No such file or directory
make: *** [make/driver.mk:10: driver-symlink] Error 1

mrspeccy
18.02.2020, 08:09
Hi Audioniek,

I just installed atevio7500_Audioniek_enigma2_gst-epl3_USB_CDK-rev1347.tar.gz on my Octagon 1028 and it looks good at first glance. However, I have a problem with the SAT tuner (Availink avl2108): no matter which settings I choose in tuner regarding voltage (13V/18V/polarization), only horizontally polarized channels appear - scans for channels with vertical polarization does not yield any results. The same holds for rev1331 from December.

I did not find any logs - what can I do to investigate this error further?

A HDMU image from late 2017 works fine and does find the channels with vertical polarization.

Best,

mrspeccy
24.02.2020, 08:27
Hi Audioniek,

I just installed atevio7500_Audioniek_enigma2_gst-epl3_USB_CDK-rev1347.tar.gz on my Octagon 1028 and it looks good at first glance. However, I have a problem with the SAT tuner (Availink avl2108): no matter which settings I choose in tuner regarding voltage (13V/18V/polarization), only horizontally polarized channels appear - scans for channels with vertical polarization does not yield any results. The same holds for rev1331 from December.


I did not make any progress on this except that I found the following link from this board that mentions a "tuner 12V bug":

http://www.hdmedia-universe.com/board/showthread.php?11026-SH4-Stand-der-Dinge&p=120927&viewfull=1#post120927

Could this be related? If I understand correctly, 12 V is the voltage used to select vertically polarized channels. Does anyone know how this bug was fixed?

mrspeccy
26.02.2020, 20:36
I did not make any progress on this except that I found the following link from this board that mentions a "tuner 12V bug":

http://www.hdmedia-universe.com/board/showthread.php?11026-SH4-Stand-der-Dinge&p=120927&viewfull=1#post120927

Could this be related? If I understand correctly, 12 V is the voltage used to select vertically polarized channels. Does anyone know how this bug was fixed?

After building a DEBUG version using Audioniek's build system (Enigma 2 from Jan. 28), I called dmesg and found that the kernel log was filled with errors of the kind

avl2108: ERROR: Could not get lock status!

like 10s of these messages in a row. Any ideas?

chaban
27.02.2020, 09:44
hs7420_Audioniek_enigma2_gst-epl3_USB_P217_CDK-rev1280
hs7420_Audioniek_enigma2_gst-epl3_USB_P217_CDK-rev1331
hs7420_Audioniek_enigma2_gst-epl3_USB_P217_CDK-rev1347 (http://www.hdmedia-universe.com/board/attachment.php?attachmentid=15718&d=1580592100)

Tested On hs-7420.....boot problem

start enigma2
10..9..8..7..6..5..4..3..2..1..0
ERROR

ret=> 3535808## main.c Error: "hwnfconf" not defined


--={ Load Enigma2 from USB }=--


[init] Wait until /dev/sda exists
[init] Time out on wait for /dev/sda, exiting...




BusyBox(2020-01-31 19:17:29 CET) built-in shell (ash)


sh: can't access tty; job control turned off

samkooke
29.02.2020, 12:22
hello Audioniek the last image is beautiful but it lacks exteplayer3 can you put it in the next image or now on IPK thanks.

kader_73
31.03.2020, 14:36
salam ,


Image Audioniek and emu oscam:
when the image freezes, the video returns but not the sound.
You have to zap on another channel to get the sound again.

in the rcS file check the player2 arguments


When you turn off the receiver and then restart it, oscam does not start automatically, it must be done manually for it to work.

for that you can use GSU (Glass System Utility )

regards

Sheypooor
09.04.2020, 23:09
hs7420_Audioniek_enigma2_gst-epl3_USB_P217_CDK-rev1280
hs7420_Audioniek_enigma2_gst-epl3_USB_P217_CDK-rev1331
hs7420_Audioniek_enigma2_gst-epl3_USB_P217_CDK-rev1347 (http://www.hdmedia-universe.com/board/attachment.php?attachmentid=15718&d=1580592100)

Tested On hs-7420.....boot problem

start enigma2
10..9..8..7..6..5..4..3..2..1..0
ERROR

ret=> 3535808## main.c Error: "hwnfconf" not defined


--={ Load Enigma2 from USB }=--


[init] Wait until /dev/sda exists
[init] Time out on wait for /dev/sda, exiting...




BusyBox(2020-01-31 19:17:29 CET) built-in shell (ash)


sh: can't access tty; job control turned off






Hi
Can this file be used for hs 7420a hardware?
And has anyone been able to install this file on the device?
Do any of your friends have a file for this receiver model?
Thank you for giving it to me

Audioniek
10.04.2020, 12:07
@Sheypooor: Yes you can. Just follow the installation instructions (here (http://www.hdmedia-universe.com/board/showthread.php?11200-Audioniek-Images-general-info/page2), posting 20). You may have to install a different boot loader.

@chaban: Although I do not have a HS7420 to test with, the image is built in exactly the same way as with the very similar HS7110 and HS7810A, which I can and have tested. Please note that boot from USB is VERY critical on these receivers; you may have to try several USB sticks to find one that works. Older ones (capacity < 1Gbyte) usually work best. I my household out of more than 20 sticks, only one works reliable, and one requires several restarts to boot. The problem is in the bootloader. As I do not have the source code of it, I cannot fix this.

Regards,

Audioniek.

mrspeccy
26.04.2020, 11:03
Hi Audioniek,

I just installed atevio7500_Audioniek_enigma2_gst-epl3_USB_CDK-rev1347.tar.gz on my Octagon 1028 and it looks good at first glance. However, I have a problem with the SAT tuner (Availink avl2108): no matter which settings I choose in tuner regarding voltage (13V/18V/polarization), only horizontally polarized channels appear - scans for channels with vertical polarization does not yield any results. The same holds for rev1331 from December.

I did not find any logs - what can I do to investigate this error further?

A HDMU image from late 2017 works fine and does find the channels with vertical polarization.

Best,

Hi Audoniek,

with the updated image atevio7500_Audioniek_enigma2_gst-epl3_USB_CDK-rev1364.zip from late March
the problem still persists: the tuner can't find any vertically polarized channels. The tuner is a Sony CXD2820R.

How can we approach this problem?

mrspeccy
28.04.2020, 10:15
Hi Audoniek,

with the updated image atevio7500_Audioniek_enigma2_gst-epl3_USB_CDK-rev1364.zip from late March
the problem still persists: the tuner can't find any vertically polarized channels. The tuner is a Sony CXD2820R.

How can we approach this problem?

Sorry, the DVB-S tuner is an Availink AVM2108, see the output below. Sorry for coming with another report, but I also have challenges with the DVB-T/T2 tuner, which is a Samsung CXD2820. It is only recognized as a DVB-T (not T2) tuner (see below as well ) so that I cannot tune in to any channels that use the DVB-T2 standard. This problem is also present on the latest HDMU image 16228 enigma2 Git 581.

How can I force the system to treat Tuner 1 as a DVB-T2 instead of DVB-T tuner?

Regards,

mrspeccy

Output of cat /proc/bus/nim_sockets

NIM Socket 0:
Type: DVB-S2
Name: Availink AVL2108 DVB-S2
Frontend_Device: 0
NIM Socket 1:
Type: DVB-T
Name: Samsung CXD2820 DVB-T/T2
Frontend_Device: 1

Audioniek
28.04.2020, 16:33
I already spotted that the Sony CXD2820 is a DVB-T tuner. The problem is the driver. For the this Fortis model two different DVB-T tuners were sold. The early model does not support DVB-T2. It has a Sony CXD2820 tuer and a Samsung 5SH1432 demodulator. Both the driver and the datasheet for the latter are confidential and for that reason are not part of the image I can offer. As far as I know a driver can be found in Bpanthers' Neutrino images, but this will not solve your problem, as only the later DVB-T tuner supports DVB-T2. At present I do not know which chips it is based on.

In the past I have started work on a driver for the older model, but my tuner module broke down while working on the driver. These tuner modules are hard to find, as the majority of the receivers were sold and used with 2x DVB-S(2) as tuners and this receiver model is slowly coming of age and re-/disgarded as obsolete, although it is my favourite Fortis model.

Regards,

Audioniek.

mrspeccy
28.04.2020, 17:01
I already spotted that the Sony CXD2820 is a DVB-T tuner. The problem is the driver. For the this Fortis model two different DVB-T tuners were sold. The early model does not support DVB-T2. It has a Sony CXD2820 tuer and a Samsung 5SH1432 demodulator. Both the driver and the datasheet for the latter are confidential and for that reason are not part of the image I can offer. As far as I know a driver can be found in Bpanthers' Neutrino images, but this will not solve your problem, as only the later DVB-T tuner supports DVB-T2. At present I do not know which chips it is based on.

In the past I have started work on a driver for the older model, but my tuner module broke down while working on the driver. These tuner modules are hard to find, as the majority of the receivers were sold and used with 2x DVB-S(2) as tuners and this receiver model is slowly coming of age and re-/disgarded as obsolete, although it is my favourite Fortis model.

Regards,

Audioniek.

Hi Audieniek,

thank you for your fast reply. I just tried the original Octagon 1028P software from 2017 and found that it allows me to tune in to DVB-T2 channels! So I seems I have the "newer" variant of the Sony CXD2820 tuner - sometimes this is possibly referred to by CXD2820R (https://www.linuxtv.org/wiki/index.php/Sony_CXD2820). The latter link also refers to open source Linux drivers but I'm not sure it helps. Do you have a link to Bpanther's Neutrino images?

(The situation is that I am located in Denmark where more and more channels are moved from the DVB-T to the DVB-T2 standard, so this is why I'm interested in receiving the DVB-T2 channels. In the worst case, I have to move back to the original Octagon software or buy a new receiver.)

The other issue I mentioned is that with your build of the atevio7500 image, the DVB-S tuner does not allow me to tune in to vertically polarized channels on Astra 19E - which works with the latest HDMU image, though. I know I am demanding a lot, but can you reproduce this issue with your DVB-S tuners on the Octagon/Fortis?

pop1234
28.04.2020, 17:54
hello mrspeccy (http://www.hdmedia-universe.com/board/member.php?22153-mrspeccy) & Audioniek (http://www.hdmedia-universe.com/board/member.php?1349-Audioniek)

https://git.linuxtv.org/media_tree.git/commit/?id=27cfc85e3dae187a470f7aa54123689a487970f2

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

Audioniek
30.04.2020, 10:34
Do you have a link to Bpanther's Neutrino images?
Bpanthers Neutrino images are here (https://forum.mbremer.de/viewforum.php?f=13). You to register to be able to download them.


The situation is that I am located in Denmark where more and more channels are moved from the DVB-T to the DVB-T2 standard
Same here. The Dutch provider KPN has been so kind to abolish DVB-T too soon, rendering millions of usable receivers worthless,


I know I am demanding a lot, but can you reproduce this issue with your DVB-S tuners on the Octagon/Fortis?
On my Rebox RE-8500's (I have several), all DVB-S(2) channels tune fine, so I cannot repoduce the problem.

Regards,

Audioniek.

- - - Aktualisiert - - -


hello mrspeccy (http://www.hdmedia-universe.com/board/member.php?22153-mrspeccy) & Audioniek (http://www.hdmedia-universe.com/board/member.php?1349-Audioniek)

Thank you, but as said above, The Sony CDX2820(R) is not the problem, the elusive Samsung 5SH1432 is...

I will try and check if my RE-8500's can receive DVB-T2 with the newer tuner.

Regards,

Audioniek.

Audioniek
30.04.2020, 11:47
Identifying the plugin tuners for the Fortis HS8200.

This done easiest by the back plate writing. The DVB-S(2) is course easily identifyable by its F-connectors as the others have IEC connectors. It is also the only plugin tuner having a heatsink.

As far as I know, of the DVB-C tuner only one variant was available. Its backplate has the texts CABLE IN and CABLE OUT. The tuner module was made by Samsung has a sticker on it with the number DNQS44PP1010A.

The old and new DVB-T plugin tuners look exactly the same, and can only be distinguished on the outside by the sticker on the tuner module.


Old (DVB-T only): DNOD44SQH102A.
New (DVB-T and DVB-T2): DNOQ44QCH106A.


To complicate things further, the DVB-C, DVB-T and DVB-T(2) tuners are all built on the same PCB, only the components differ.

Regards,

Audioniek.

mrspeccy
30.04.2020, 13:42
The old and new DVB-T tuner look exactly the same, and can only be distiguished on the outside by the sticker on the tuner number.


Old (DVB-T only): DNOD44SQH102A.
New (DVB-T and DVB-T2): DNOQ44QCH106A.




Hi Audioniek,

thank you for your great support. First of all, for the DVB-T(2) issue: On my tuner it says DNOQ44QCH106A, so it seems DVB-T2 ready. This is confirmed by the original Octagon software, which indeed does tune in to channels in the new DVB-T2 standard. Unfortunately, this works with neither HDMU, Audioniek nor Bpanther's Neutrino images, which all return "no channels found" on the DVB-T2 frequencies. In the end, all these images seem to rely on the same driver from the Duckbox project (stored in the cdx2820.ko kernel module), so I guess this driver is the issue. Even though the source code (e.g. "cdx2820.c") refers explicitly to DVB-T2, the corresponding implementation seems buggy or is not active. The driver posted above by pop1234 seems to be different from the Duckbox project, and it is not obvious to me how to migrate it to sources relying on Duckbox.

Please correct me if I'm wrong.

Now for the DVB-S(2) issue: Thank you, Audioniek, for your extensive tests. I really don't understand what is going on. I can tune in to vertically polarized Astra 1E channels (e.g. KiKa HD) with the original Octagon, the latest HDMU from 2017 and Bpanther's image from 2020. It does not work with your precompiled atevio7500 Enigma 2 image and compiling it manually did not solve the issue either. I will try whether I can overwrite the avl2108.ko module from your builds with versions from other images.

Edit: Just to make sure it did not get lost in the noise:

I did not make any progress on this except that I found the following link from this board that mentions a "tuner 12V bug":

http://www.hdmedia-universe.com/board/showthread.php?11026-SH4-Stand-der-Dinge&p=120927&viewfull=1#post120927

Could this be related? If I understand correctly, 12 V is the voltage used to select vertically polarized channels. Does anyone know how this bug was fixed?

After building a DEBUG version using Audioniek's build system (Enigma 2 from Jan. 28), I called dmesg and found that the kernel log was filled with errors of the kind

avl2108: ERROR: Could not get lock status!

like 10s of these messages in a row. Any ideas?

pop1234
30.04.2020, 13:47
@Audioniek
http://www.tbsdtv.com/download/document/common/tbs-linux-drivers_v150728.zip
cxd2820r_c.c
cxd2820r_core.c
cxd2820r_priv.h
cxd2820r_t2.c <--- T2 !
cxd2820r_t.c

Audioniek
03.05.2020, 13:57
I have studied some things somewhat further and opened up the tuner modules in my possession. This revealed the following:

DVB-S(2): AVL2108 demodulator and STV6306 tuner (works)
DVB-T: S5H1432 demodulator and MXL5007T tuner (old, DVB-T only, tuner module number DNOD44QSH102A,work on factory firmware, not on E2, no driver available)
DVB-T(2): CXD2820R demodulator and TDA18212 tuner (new, tuner module number DNOQ44QCH106A, works on factory software, not on E2)
DVB-C: TDA10024 demodulator and MXL201 tuner (tuner module number DNQS44CPP101A, not tested by me)

If you have look at the driver code things match up regarding DVB-S(2) and DVB-C. The drivers are indeed for the chips mentioned.

With DVB-T(2) it is a completely different story. As mentioned before the DVB-T only module (...102A) is not supported, due to the missing driver. With the DVB-T2 module, there is a surprise. The driver is for the combination CDX2820R plus TDA18272, not the TDA18212 I found in my module. I looked three times with a magnifying glass, and I did not misread the number, as a 1 and a 7 can be mixed up easily in small print. The TDA18212 also exists and seems to be an earlier member of the NXP DVB-T2 compatible tuner chips of which the TDA18272, TDA18273 and the TDA18292 also are members. A quick hunt on the net did yield a brief product description, but no detailed data sheets. Most promising was the site of Antti Palosaari (http://palosaari.fi/) who has drivers for most of them

This is quite revealing, assuming that the TDA18212 and TDA18272 are not compatible with each other. Frontends are made around the demodulator, the part that is actually visible in hardware. The tuner is controlled through the demodulator, in many cases through a so called I2C gate. This explains that the CDX2820R/TDA18212 module is recognized as a frontend, because the TDA2820R is detected (and reported) correctly. The tuner however is different from that assumed by the current driver and hence: no reception and the lock errors found in the logs.

This leads to two possibilities. The first is that the chip number TDA18212 was misread as TDA18272, and the driver was built for the latter. If so, this driver could never have worked on the module I have (...106A). The second possiblity is that there are modules around with the TDA18212, but also with the TDA18272. Technically it is possible this can work if you drive the TDA18272 as a TDA18212 in case the '7' is a superset of the '1'; both ICs have the same housing and are mechanically compatible.

The fix? I have to study a driver for the TDA18212 and figure out the differences with the TDA18212 and intgrate that in the current driver. This however is time consuming and I am very busy with two other projects. To pull this off one would also need the full datasheets (not the 10 page product briefs) of the two devices.

Also see Samsung-S5H1432-demodulator-help-wanted (http://www.hdmedia-universe.com/board/showthread.php?11229-Samsung-S5H1432-demodulator-help-wanted)

Regards,

Audioniek.

- - - Aktualisiert - - -

The 12V tuner bug...

is not a bug. For reasons that are beyond my comprehension, somebody mixed the LNB voltages up with the 12V output that can be found on only one SH4 receiver I know of: the ABcom IPbox 9900HD. The two (12V out and LNB power) have nothing to do with each other, but there are STV090X tuner drivers around that do strange and unjust things with the LNB power driver and the 12V output (which does not exist on almost all models), the latter can be controlled through procfs.

A long time ago I removed all 12V output related stuff from the frontend drivers, so this "bug" does not exist in my images.

In addition, in my images the entry /proc/stb/misc/12V_output is missing as the corresponding hardware is simply not there (I do not offer an image for the IPbox 9900HD as I do not have one and therefore cannot test things). E2 tests for this entry and reports that something is missing if it is not found (which is not true, the message is wrong). Regarding the previous, on SH4 this is all normal, and you should not bother about this "bug".

Regards,

Audioniek.

mrspeccy
03.05.2020, 19:17
I have studied some things somewhat further and opened up the tuner modules in my possession. This revealed the following:

DVB-T(2): CXD2820R demodulator and TDA18212 tuner (new, tuner module number DNOQ44QCH106A, works on factory software, not on E2)

With the DVB-T2 module, there is a surprise. The driver is for the combination CDX2820R plus TDA18272, not the TDA18212 I found in my module. I looked three times with a magnifying glass, and I did not misread the number, as a 1 and a 7 can be mixed up easily in small print. The TDA18212 also exists and seems to be an earlier member of the NXP DVB-T2 compatible tuner chips of which the TDA18272, TDA18273 and the TDA18292 also are members. A quick hunt on the net did yield a brief product description, but no detailed data sheets.


Hi Audioniek,

impressive research. I can add that the DNOQ44QCH106A indeed works with E2, including your image; however, only DVB-T channels are found while channels in the DVB-T2 standard cannot be found. With the stock firmware, both types are found. I also made some tests. With your E2 firmware (the same holds for HDMU from 2017), I tried the following


cat /proc/bus/nim_sockets
NIM Socket 0:
Type: DVB-S2
Name: Availink AVL2108 DVB-S2
Frontend_Device: 0
NIM Socket 1:
Type: DVB-T
Name: Samsung CXD2820 DVB-T/T2
Frontend_Device: 1


That is, the tuner is recognized as DVB-T only, not DVB-T2, so it seems plausible that the channel search does not even attempt to tune in to channels in DVB-T2 format. On the positive side, it seems that the tda28278 driver (mind the 7) is compatible with the tda18218 to some extent, when it comes to DVB-T type channels.

I hacked the file driver/player2/linux/drivers/media/dvb/stm/dvb/e2_proc/e2_proc_info.c to force the type of the tuner to DVB-T2 (confirmed by nim_sockets). As a result, the Enigma2 menu mentioned DVB-T/T2 in the headline of the channel search while it previously only showed DVB-T there. Unfortunately, this time no channels were found at all - neither DVB-T nor DVB-T2 ones. Maybe the tuner crashed this time due to the wrong driver being used.

One thing I find curious: the build system includes the file driver/frontends/pace7241/tda18218.c (and related headers). However, I am not sure to what extent these files are useful.

mrspeccy
05.05.2020, 11:11
DVB-T2 works (kind of) with TDA28218/CDX2820!


The driver for the TDA28278 finally works on my box. However, it seems that I could not tune in to DVB-T2 channels before due to a timing issue. For example, in the source file cdx2820.c there are lines such as


msleep(30); /* fixme: think on this */


and similarly for the tda18272.c. I increased these pauses to 300 milliseconds and, after recompiling the related modules, I could receive DVB-T2 channels that I selected manually in E2. It is not stable yet, though; a full channel search sometimes misses some DVB-T2 channels. I will play around with these pauses/timeouts a bit. I also think that the issue with my DVB-S2 tuner that fails to select vertically polarized channels is a timing issue. This could explain that it works on Audioniek's hardware - mine is compatible but production tolerances for the hardware could make a difference. Will look into that later.

Finally, I found this URL: https://patchwork.kernel.org/patch/3757251/ It indicates that TDA28278 is a superset of TDA28218; as far as I understand it just includes some additional modulations that E2 may not use anyway.

pop1234
05.05.2020, 12:56
you can take a look here (Patch) that might help you
https://github.com/oe-alliance/oe-alliance-core/tree/5a2ff4d7c3629ecd10d6777e6041138f272a380d/meta-brands/meta-ini/recipes-linux/linux-ini-hde2-3.14.2

mrspeccy
09.05.2020, 19:47
Hi Audioniek,

I am now proposing two patches that makes DVB-T2 work on my Octagon 1028 with CXD2820 tuner - with some reservations explained below. The issue addressed by the first patch is that the tuner is erroneously identified as DVB-T only. The second patch increases the timeout when tuning in to a channel to 1,8 sec.; experiments have shown that tuning in DVB-T2 channels can well take over a second with my tuner. I experimented quite heavily with different timeouts and found that the 1,8 sec (60 cycles of 30 milliseconds) is a good compromise.

The first patch comes here:



--- a/player2/linux/drivers/media/dvb/stm/dvb/e2_proc/e2_proc_bus.c
+++ b/player2/linux/drivers/media/dvb/stm/dvb/e2_proc/e2_proc_bus.c
@@ -136,6 +136,9 @@ int proc_bus_nim_sockets_read(char *page, char **start, off_t off, int count,
p.u.data = SYS_DVBC_ANNEX_AC;
if (fe->ops.get_property(fe, &p) == 0)
pMode = "DVB-C";
+
+ if (strcmp(fe->ops.info.name,"Sony CXD2820 DVB-T/T2") == 0)
+ pType = "DVB-T2";
}
break;
}


and the second here:


--- driver/frontends/multituner/frontends/cxd2820_tda18272/cxd2820.c
+++ driver/frontends/multituner/frontends/cxd2820_tda18272/cxd2820.c
@@ -1547,7 +1547,7 @@ static int cxd2820_set_frontend_dvbt2(struct dvb_frontend *fe, struct dvb_fronte
printk("%s: 4. Demod set failed (%d)\n", __func__, res);
return res;
}
- cnt = 7;
+ cnt = 60;
do
{
fe_status_t status = 0;
@@ -1649,7 +1649,7 @@ static int cxd2820_set_frontend_dvbt2(struct dvb_frontend *fe, struct dvb_fronte
printk("%s: 6. Demod set failed (%d)\n", __func__, res);
return res;
}
- cnt = 7;
+ cnt = 60;

do
{


Now for the reservations mentioned above: With these patches done in Audioniek's driver git (pull from today, May 9), I compiled the kernel modules cxd2820.ko and stmdvb.ko and put them into the /lib/modules directory of my HDMU image (HDMU_17209_E2_at7500_217_git_610_nodebug_mix_USB. tar.gz) that I still prefer to use because of an unrelated issue that I experience with the DVB-S tuner under Audioniek's images. Having the HDMU image patched in this way works perfectly - a full channel search finds all 24 DVB-T and all 24 DVB-T2 channels that are broadcasted here in Copenhagen at the moment and I can tune in to all of them without any problem.

However: I cannot get the modification of the DVB-T driver to work with Audioniek's build system at all. I build an Enigma2 image (debug build) with the latest Audioniek git version (May 9) and the automated channel search on that image would return 0 channels due to timeouts, see the following log:


cxd2820_set_frontend_dvbt2: waiting for lock 3 ...
[cxd2820] cxd2820_i2c_read: index 0xff10 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x10 b: 0x15
[cxd2820] cxd2820_read_status_dvbt: < res 0, status 0
cxd2820_set_frontend_dvbt2: waiting for lock 2 ...
[cxd2820] cxd2820_i2c_read: index 0xff10 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x10 b: 0x11
[cxd2820] cxd2820_read_status_dvbt: < res 0, status 0
cxd2820_set_frontend_dvbt2: waiting for lock 1 ...
cxd2820_set_frontend_dvbt2(0): timeout tuning DVB-T :(


As I said, I do not get these timeouts with the modiefied driver copied into HDMU and can find 48 DVB-T/DVB-T2 channels.

I also tried two specific channel searches. With channel 40, which broadcasts DVB-T, this returns 0 instead of the 6 available stations on that channel. The log says:


dvbt2: waiting for lock 1 ...
cxd2820_set_frontend_dvbt2(0): Timeout tuning DVB-T2 now trying DVB-T...
[cxd2820] cxd2820_i2c_write_bulk: >
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x00 0x00
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0xfe 0x01
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x85 0x00
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x88 0x01
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x81 0x00
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x80 0x00
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x00 0x20
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x69 0x00
[cxd2820] cxd2820_i2c_write_bulk: < res 0
[cxd2820] cxd2820_i2c_write_bulk: >
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x00 0x27
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x48 0x06
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x00 0x00
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0xcb 0x08
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x89 0x55
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x8b 0xba
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x00 0x20
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0xcb 0x08
[cxd2820] cxd2820_i2c_write_bulk: < res 0
[cxd2820] cxd2820_i2c_write_bulk: >
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x00 0x00
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0xd3 0x00
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x00 0x04
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x10 0x00
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x00 0x00
[cxd2820] cxd2820_i2c_write(): n: 3 b: 0x80 0x00 0x03
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x85 0x07
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x88 0x02
[cxd2820] cxd2820_i2c_write_bulk: < res 0
[cxd2820] cxd2820_i2c_write_bulk: >
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x00 0x00
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x70 0x38
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x00 0x20
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x70 0x38
[cxd2820] cxd2820_i2c_write_bulk: < res 0
[tda18272] tda18272_i2c_write_bulk: >
[cxd2820] cxd2820_i2cgw_readwrite >
[cxd2820] cxd2820_i2cgw_readwrite(): n: 4 b: 0x09 0xc0 0x15 0x53
[cxd2820] cxd2820_i2cgw_readwrite < res 1
[cxd2820] cxd2820_i2cgw_readwrite >
[cxd2820] cxd2820_i2cgw_readwrite(): n: 4 b: 0x09 0xc0 0x13 0x22
[cxd2820] cxd2820_i2cgw_readwrite < res 1
[cxd2820] cxd2820_i2cgw_readwrite >
[cxd2820] cxd2820_i2cgw_readwrite(): n: 4 b: 0x09 0xc0 0x23 0x01
[cxd2820] cxd2820_i2cgw_readwrite < res 1
[cxd2820] cxd2820_i2cgw_readwrite >
[cxd2820] cxd2820_i2cgw_readwrite(): n: 4 b: 0x09 0xc0 0x0f 0xbc
[cxd2820] cxd2820_i2cgw_readwrite < res 1
[cxd2820] cxd2820_i2cgw_readwrite >
[cxd2820] cxd2820_i2cgw_readwrite(): n: 4 b: 0x09 0xc0 0x06 0x00
[cxd2820] cxd2820_i2cgw_readwrite < res 1
[tda18272] tda18272_i2c_write_bulk: < res 0
[cxd2820] cxd2820_i2cgw_readwrite >
[cxd2820] cxd2820_i2cgw_readwrite(): n: 8 b: 0x09 0xc0 0x16 0x09 0x8d 0x50 0xc1 0x01
[cxd2820] cxd2820_i2cgw_readwrite < res 1
[tda18272] tda18272_wait_irq: >
[tda18272] tda18272_i2c_read: index 0x08 1
[cxd2820] cxd2820_i2cgw_readwrite >
[cxd2820] cxd2820_i2cgw_readwrite(): n: 3 b: 0x09 0xc0 0x08
[cxd2820] cxd2820_i2cgw_readwrite < res 1
[cxd2820] cxd2820_i2cgw_readwrite >
[cxd2820] cxd2820_i2cgw_readwrite read
[cxd2820] cxd2820_i2cgw_readwrite: writing 0x09 0xc1
[cxd2820] cxd2820_i2cgw_readwrite(): n: 1 b: 0xbf
[cxd2820] cxd2820_i2cgw_readwrite < res 2
[tda18272] tda18272_i2c_read(): n: 1 r: 0x08 b: 0xbf
[tda18272] tda18272_wait_irq: < res 0
[tda18272] tda18272_i2c_read: index 0x07 1
[cxd2820] cxd2820_i2cgw_readwrite >
[cxd2820] cxd2820_i2cgw_readwrite(): n: 3 b: 0x09 0xc0 0x07
[cxd2820] cxd2820_i2cgw_readwrite < res 1
[cxd2820] cxd2820_i2cgw_readwrite >
[cxd2820] cxd2820_i2cgw_readwrite read
[cxd2820] cxd2820_i2cgw_readwrite: writing 0x09 0xc1
[cxd2820] cxd2820_i2cgw_readwrite(): n: 1 b: 0x37
[cxd2820] cxd2820_i2cgw_readwrite < res 2
[tda18272] tda18272_i2c_read(): n: 1 r: 0x07 b: 0x37
[tda18272] tda18272_set_params_dvbt: < 0
[cxd2820] cxd2820_i2c_write_bulk: >
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x00 0x00
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0xd3 0x00
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x00 0x04
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x10 0x00
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x00 0x00
[cxd2820] cxd2820_i2c_write(): n: 3 b: 0x80 0x00 0x03
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x85 0x07
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x88 0x02
[cxd2820] cxd2820_i2c_write_bulk: < res 0
[cxd2820] cxd2820_i2c_write_bulk: >
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x00 0x00
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0xa5 0x00
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x82 0xb6
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0xc2 0x11
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x00 0x01
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x6a 0x50
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x00 0x04
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x27 0x41
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x00 0x00
[cxd2820] cxd2820_i2c_write(): n: 6 b: 0x9f 0x11 0xf0 0x00 0x00 0x00
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x9f 0x11
[cxd2820] cxd2820_i2c_write(): n: 4 b: 0xb6 0x19 0xe9 0x85
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0xd7 0x03
[cxd2820] cxd2820_i2c_write(): n: 3 b: 0xd9 0x01 0xe0
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x00 0x00
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0xff 0x18
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x00 0x00
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0xfe 0x01
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x00 0x00
[cxd2820] cxd2820_i2c_write_bulk: < res 0
[cxd2820] cxd2820_i2c_write_bulk: >
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x00 0x04
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x10 0x00
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x00 0x00
[cxd2820] cxd2820_i2c_write_bulk: < res 0
[cxd2820] cxd2820_i2c_read: index 0xff10 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x10 b: 0x01
[cxd2820] cxd2820_read_status_dvbt: < res 0, status 0
cxd2820_set_frontend_dvbt2: waiting for lock 60 ...
[cxd2820] cxd2820_i2c_read: index 0xff10 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x10 b: 0x05
[cxd2820] cxd2820_i2c_read: index 0xff73 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x73
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x73 b: 0xc0
[cxd2820] cxd2820_read_status_dvbt: < res 0, status 15
cxd2820_set_frontend_dvbt2: waiting for lock 59 ...
[cxd2820] cxd2820_i2c_read: index 0xff10 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x10 b: 0x06
[cxd2820] cxd2820_i2c_read: index 0xff73 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x73
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x73 b: 0xe8
[cxd2820] cxd2820_read_status_dvbt: < res 0, status 31
[cxd2820] cxd2820_set_frontend_dvbt2(0,58): Tuner successfully set (DVB-T)!
[cxd2820] cxd2820_i2c_read: index 0xff10 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x10 b: 0x06
[cxd2820] cxd2820_i2c_read: index 0xff73 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x73
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x73 b: 0xe8
[cxd2820] cxd2820_read_status_dvbt: < res 0, status 31
[cxd2820] cxd2820_get_frontend_dvbt2 >
[tda18272] tda18272_get_frequency: >
[tda18272] tda18272_get_frequency: < res 0, frequ 626000000
[cxd2820] cxd2820_i2c_read: index 0x204c 4
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x4c
[cxd2820] cxd2820_i2c_read(): n: 4 r: 0x204c b: 0x00 0x00 0x00 0x00
[cxd2820] cxd2820_i2c_read: index 0x204c 4
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x4c
[cxd2820] cxd2820_i2c_read(): n: 4 r: 0x204c b: 0x00 0x00 0x00 0x00
[cxd2820] cxd2820_i2c_read: index 0x221b 32
[cxd2820] cxd2820_i2c_read: w: 0x00 0x22
[cxd2820] cxd2820_i2c_read: w: 0x1b
[cxd2820] cxd2820_i2c_read(): n: 32 r: 0x221b b: 0x00 0x00 0x00 0x00 0x00 0x3e 0x01 0x04 0x09 0x00 0x07 0x0f 0x0e 0x03 0x03 0x02 0x3d 0xf7 0x02 0xaf 0x57 0x0e 0x8b 0xed 0xe7 0xcb 0x9a 0xdf 0xb7 0xfe 0x03 0x45
[cxd2820] cxd2820_i2c_read: index 0x2254 16
[cxd2820] cxd2820_i2c_read: w: 0x00 0x22
[cxd2820] cxd2820_i2c_read: w: 0x54
[cxd2820] cxd2820_i2c_read(): n: 16 r: 0x2254 b: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[cxd2820] cxd2820_i2c_read: index 0x2052 5
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x52
[cxd2820] cxd2820_i2c_read(): n: 5 r: 0x2052 b: 0x11 0xf0 0x00 0x00 0x00
[cxd2820] cxd2820_i2c_read: index 0x227f 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x22
[cxd2820] cxd2820_i2c_read: w: 0x7f
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x227f b: 0x90
[cxd2820] cxd2820_get_frontend_dvbt2 < res 0
[cxd2820] cxd2820_i2c_read: index 0xff10 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x10 b: 0x06
[cxd2820] cxd2820_i2c_read: index 0xff73 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x73
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x73 b: 0x28
[cxd2820] cxd2820_read_status_dvbt: < res 0, status 31
[cxd2820] cxd2820_i2c_read: index 0xff10 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x10 b: 0x06
[cxd2820] cxd2820_i2c_read: index 0xff73 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x73
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x73 b: 0x28
[cxd2820] cxd2820_read_status_dvbt: < res 0, status 31
reset_tsm: 1 numRunningFeeds: 0 => calling stm_tsm_init(1)
[TSM] reinit stream routing...
[TSM] skip stpio stuff in reinit
Routing streams through cimax
ret slothandle = 20000
pti_hal_slot_set_pid: 0 20000 0
pti_hal_slot_set_pid ok (pid 0, tc = 0)
[cxd2820] cxd2820_i2c_read: index 0xff10 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x10 b: 0x06
[cxd2820] cxd2820_i2c_read: index 0xff73 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x73
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x73 b: 0x28
[cxd2820] cxd2820_read_status_dvbt: < res 0, status 31
pti_hal_slot_clear_pid slot = 0, tc = 0, num = 1
[cxd2820] cxd2820_i2c_read: index 0xff10 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x10 b: 0x06
pti_hal_slot_free 20000
[cxd2820] cxd2820_i2c_read: index 0xff73 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x73
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x73 b: 0x28
[cxd2820] cxd2820_read_status_dvbt: < res 0, status 31
[cxd2820] cxd2820_i2c_read: index 0xff10 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x10 b: 0x06
[cxd2820] cxd2820_i2c_read: index 0xff73 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x73
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x73 b: 0x28
[cxd2820] cxd2820_read_status_dvbt: < res 0, status 31
[cxd2820] cxd2820_i2c_read: index 0xff10 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x10 b: 0x06
[cxd2820] cxd2820_i2c_read: index 0xff73 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x73
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x73 b: 0x28
[cxd2820] cxd2820_read_status_dvbt: < res 0, status 31
[cxd2820] cxd2820_i2c_read: index 0xff10 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x10 b: 0x06
[cxd2820] cxd2820_i2c_read: index 0xff73 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x73
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x73 b: 0x28
[cxd2820] cxd2820_read_status_dvbt: < res 0, status 31
[cxd2820] cxd2820_i2c_read: index 0xff10 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x10 b: 0x06
[cxd2820] cxd2820_i2c_read: index 0xff73 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x73
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x73 b: 0x28
[cxd2820] cxd2820_read_status_dvbt: < res 0, status 31
[cxd2820] cxd2820_i2c_read: index 0xff10 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x10 b: 0x06
[cxd2820] cxd2820_i2c_read: index 0xff73 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x73
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x73 b: 0x28
[cxd2820] cxd2820_read_status_dvbt: < res 0, status 31
[cxd2820] cxd2820_i2c_read: index 0xff10 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x10 b: 0x06
[cxd2820] cxd2820_i2c_read: index 0xff73 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x73
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x73 b: 0x28
[cxd2820] cxd2820_read_status_dvbt: < res 0, status 31
[cxd2820] cxd2820_i2c_read: index 0xff10 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x10 b: 0x06
[cxd2820] cxd2820_i2c_read: index 0xff73 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x73
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x73 b: 0x28
[cxd2820] cxd2820_read_status_dvbt: < res 0, status 31
[cxd2820] cxd2820_i2c_read: index 0xff10 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x10 b: 0x06
[cxd2820] cxd2820_i2c_read: index 0xff73 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x73
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x73 b: 0x28
[cxd2820] cxd2820_read_status_dvbt: < res 0, status 31
[cxd2820] cxd2820_i2c_read: index 0xff10 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x10 b: 0x06
[cxd2820] cxd2820_i2c_read: index 0xff73 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x00
[cxd2820] cxd2820_i2c_read: w: 0x73
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x73 b: 0x28
[cxd2820] cxd2820_read_status_dvbt: < res 0, status 31
[tda18272] tda18272_sleep: >
[tda18272] tda18272_i2c_write_bulk: >
[cxd2820] cxd2820_i2cgw_readwrite >
[cxd2820] cxd2820_i2cgw_readwrite(): n: 4 b: 0x09 0xc0 0x5f 0xe0
[cxd2820] cxd2820_i2cgw_readwrite < res 1
[cxd2820] cxd2820_i2cgw_readwrite >
[cxd2820] cxd2820_i2cgw_readwrite(): n: 4 b: 0x09 0xc0 0x06 0x08
[cxd2820] cxd2820_i2cgw_readwrite < res 1
[tda18272] tda18272_i2c_write_bulk: < res 0
[tda18272] tda18272_sleep: < res 0
[cxd2820] cxd2820_sleep()
[cxd2820] cxd2820_i2c_write_bulk: >
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x00 0x00
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0xfe 0x01
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x85 0x00
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x88 0x01
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x81 0x00
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x80 0x00
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x00 0x20
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x69 0x00
[cxd2820] cxd2820_i2c_write_bulk: < res 0
[nuvoton] NUVOTONdev_ioctl Set icon 4 to 0 (mode 1)
[nuvoton] Set icon ICON_TIMER (number 4) to 0
[nuvoton] NUVOTONdev_ioctl Set icon 9 to 0 (mode 1)
[nuvoton] Set icon ICON_MUTE (number 9) to 0
[nuvoton] NUVOTONdev_ioctl Set icon 24 to 0 (mode 1)


As one can see, the tuner reports success in tuning in to the channel, but for some reason nothing is found in Enigma2.

The same experiment was done for channel 42, which with HDMU returns 15 channels in DVB-T2 format. With Audioniek's system, no stations are found. The log reports again a success but this is not really true:


ad: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x01
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 0
cxd2820_set_frontend_dvbt2: waiting for lock 60 ...
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x02
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 0
cxd2820_set_frontend_dvbt2: waiting for lock 59 ...
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x02
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 0
cxd2820_set_frontend_dvbt2: waiting for lock 58 ...
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x03
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 3
cxd2820_set_frontend_dvbt2: waiting for lock 57 ...
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x03
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 3
cxd2820_set_frontend_dvbt2: waiting for lock 56 ...
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x03
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 3
cxd2820_set_frontend_dvbt2: waiting for lock 55 ...
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x04
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 7
cxd2820_set_frontend_dvbt2: waiting for lock 54 ...
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x04
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 7
cxd2820_set_frontend_dvbt2: waiting for lock 53 ...
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x04
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 7
cxd2820_set_frontend_dvbt2: waiting for lock 52 ...
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x04
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 7
cxd2820_set_frontend_dvbt2: waiting for lock 51 ...
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x04
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 7
cxd2820_set_frontend_dvbt2: waiting for lock 50 ...
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x04
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 7
cxd2820_set_frontend_dvbt2: waiting for lock 49 ...
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x04
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 7
cxd2820_set_frontend_dvbt2: waiting for lock 48 ...
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x05
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 15
cxd2820_set_frontend_dvbt2: waiting for lock 47 ...
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x05
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 15
cxd2820_set_frontend_dvbt2: waiting for lock 46 ...
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x05
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 15
cxd2820_set_frontend_dvbt2: waiting for lock 45 ...
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x05
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 15
cxd2820_set_frontend_dvbt2: waiting for lock 44 ...
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x05
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 15
cxd2820_set_frontend_dvbt2: waiting for lock 43 ...
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x06
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 15
cxd2820_set_frontend_dvbt2: waiting for lock 42 ...
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x06
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 15
cxd2820_set_frontend_dvbt2: waiting for lock 41 ...
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x06
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 15
cxd2820_set_frontend_dvbt2: waiting for lock 40 ...
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x06
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 15
cxd2820_set_frontend_dvbt2: waiting for lock 39 ...
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x06
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 15
cxd2820_set_frontend_dvbt2: waiting for lock 38 ...
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x06
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 15
cxd2820_set_frontend_dvbt2: waiting for lock 37 ...
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x26
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 31
[cxd2820] cxd2820_set_frontend_dvbt2(0,36): Tuner successfully set (DVB-T2)!
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x26
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 31
[cxd2820] cxd2820_get_frontend_dvbt2 >
[tda18272] tda18272_get_frequency: >
[tda18272] tda18272_get_frequency: < res 0, frequ 642000000
[cxd2820] cxd2820_i2c_read: index 0x204c 4
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x4c
[cxd2820] cxd2820_i2c_read(): n: 4 r: 0x204c b: 0x10 0x11 0xcd 0xea
[cxd2820] cxd2820_i2c_read: index 0x204c 4
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x4c
[cxd2820] cxd2820_i2c_read(): n: 4 r: 0x204c b: 0x10 0x11 0xcd 0x55
[cxd2820] cxd2820_i2c_read: index 0x221b 32
[cxd2820] cxd2820_i2c_read: w: 0x00 0x22
[cxd2820] cxd2820_i2c_read: w: 0x1b
[cxd2820] cxd2820_i2c_read(): n: 32 r: 0x221b b: 0x05 0x00 0x00 0x00 0x00 0x00 0x01 0x00 0x0a 0x00 0x02 0x00 0x03 0x00 0x00 0x00 0x00 0xfa 0x00 0x01 0x3e 0x01 0x00 0x00 0x00 0x32 0x68 0x00 0x05 0x02 0x00 0x3b
[cxd2820] cxd2820_i2c_read: index 0x2254 16
[cxd2820] cxd2820_i2c_read: w: 0x00 0x22
[cxd2820] cxd2820_i2c_read: w: 0x54
[cxd2820] cxd2820_i2c_read(): n: 16 r: 0x2254 b: 0x00 0x01 0x03 0x00 0x00 0x00 0x00 0x01 0x03 0x01 0x01 0x00 0xbb 0x01 0x03 0x00
[cxd2820] cxd2820_i2c_read: index 0x2052 5
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x52
[cxd2820] cxd2820_i2c_read(): n: 5 r: 0x2052 b: 0x91 0xf0 0x03 0x09 0x29
[cxd2820] cxd2820_i2c_read: index 0x227f 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x22
[cxd2820] cxd2820_i2c_read: w: 0x7f
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x227f b: 0x01
[cxd2820] cxd2820_get_frontend_dvbt2 < res 0
reset_tsm: 1 numRunningFeeds: 0 => calling stm_tsm_init(1)
[TSM] reinit stream routing...
[TSM] skip stpio stuff in reinit
Routing streams through cimax
ret slothandle = 20000
pti_hal_slot_set_pid: 0 20000 0
pti_hal_slot_set_pid ok (pid 0, tc = 0)
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x26
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 31
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x26
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 31
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x26
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 31
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x26
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 31
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x26
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 31
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x26
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 31
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x26
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 31
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x26
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 31
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x26
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 31
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x26
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 31
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x26
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 31
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x26
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 31
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x26
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 31
pti_hal_slot_clear_pid slot = 0, tc = 0, num = 1
pti_hal_slot_free 20000
reset_tsm: 1 numRunningFeeds: 0 => calling stm_tsm_init(1)
[TSM] reinit stream routing...
[TSM] skip stpio stuff in reinit
Routing streams through cimax
ret slothandle = 20000
pti_hal_slot_set_pid: 0 20000 17
pti_hal_slot_set_pid ok (pid 17, tc = 0)
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x26
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 31
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x26
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 31
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x26
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 31
pti_hal_slot_clear_pid slot = 0, tc = 0, num = 1
pti_hal_slot_free 20000
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x26
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 31
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x26
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 31
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x26
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 31
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x26
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 31
[cxd2820] cxd2820_i2c_read: index 0x2010 1
[cxd2820] cxd2820_i2c_read: w: 0x00 0x20
[cxd2820] cxd2820_i2c_read: w: 0x10
[cxd2820] cxd2820_i2c_read(): n: 1 r: 0x2010 b: 0x26
[cxd2820] cxd2820_read_status_dvbt2: < res 0, status 31
[tda18272] tda18272_sleep: >
[tda18272] tda18272_i2c_write_bulk: >
[cxd2820] cxd2820_i2cgw_readwrite >
[cxd2820] cxd2820_i2cgw_readwrite(): n: 4 b: 0x09 0xc0 0x5f 0xe0
[cxd2820] cxd2820_i2cgw_readwrite < res 1
[cxd2820] cxd2820_i2cgw_readwrite >
[cxd2820] cxd2820_i2cgw_readwrite(): n: 4 b: 0x09 0xc0 0x06 0x08
[cxd2820] cxd2820_i2cgw_readwrite < res 1
[tda18272] tda18272_i2c_write_bulk: < res 0
[tda18272] tda18272_sleep: < res 0
[cxd2820] cxd2820_sleep()
[cxd2820] cxd2820_i2c_write_bulk: >
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x00 0x00
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0xfe 0x01
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x85 0x00
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x88 0x01
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x81 0x00
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x80 0x00
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x00 0x20
[cxd2820] cxd2820_i2c_write(): n: 2 b: 0x69 0x00
[cxd2820] cxd2820_i2c_write_bulk: < res 0
[nuvoton] NUVOTONdev_ioctl Set icon 4 to 0 (mode 1)
[nuvoton] Set icon ICON_TIMER (number 4) to 0
[nuvoton] NUVOTONdev_ioctl Set icon 9 to 0 (mode 1)
[nuvoton] Set icon ICON_MUTE (number 9) to 0
[nuvoton] NUVOTONdev_ioctl Set icon 24 to 0 (mode 1)


This is really weird. I would really like to use Audioniek's Enigma2 image but can't do it with my driver patch.

Audioniek
10.05.2020, 16:20
The changes in wait time have been put in, and I also have tried to fix the T2 recognition.

Regards,

Audioniek.

mrspeccy
13.05.2020, 07:47
The changes in wait time have been put in, and I also have tried to fix the T2 recognition.

Regards,

Audioniek.

Hi Audioniek,

thank you. The tuner is recognized as T2 now but the problem described above unfortunately persists: I can use the kernel module cxd2820.ko built from your git repository in my old HDMU image without any issues - so a working solution but a hack that allows me to tune in to both DVB-T and DVB-T2 chnnels. However, when I use your image with the patch in its total, the channel scan does not yield any results. As I wrote earlier, the logs do not reveal any reason to me. Can it be that there is a timeout in the channel scan method of Enigma 2 that is conflicting with the more generous timeout for the tuner?

Best,

mrspeccy

pop1234
13.05.2020, 13:29
look this ,you can help you
https://github.com/Duckbox-Developers/linux-sh4-2.6.32.71/tree/master/drivers/media/dvb/frontends

https://github.com/torvalds/linux/blob/master/drivers/media/dvb-frontends/cxd2880

i think you need file

and this patch for cxd2880r (https://github.com/oe-alliance/oe-alliance-core/blob/5a2ff4d7c3629ecd10d6777e6041138f272a380d/meta-brands/meta-ini/recipes-linux/linux-ini-hde2-3.14.2/cxd2820r-output-full-range-SNR.patch)

sadaghiani
13.05.2020, 20:32
look this ,you can help you
https://github.com/Duckbox-Developers/linux-sh4-2.6.32.71/tree/master/drivers/media/dvb/frontends

https://github.com/torvalds/linux/blob/master/drivers/media/dvb-frontends/cxd2880

i think you need file

and this patch for cxd2880r (https://github.com/oe-alliance/oe-alliance-core/blob/5a2ff4d7c3629ecd10d6777e6041138f272a380d/meta-brands/meta-ini/recipes-linux/linux-ini-hde2-3.14.2/cxd2820r-output-full-range-SNR.patch)

Can this link be used to update all tuners, especially these tuners?
STV090x Multistandard
Conextant cx24116 DVB-S2
Or is there another link that is more up to date

Audioniek
14.05.2020, 00:05
Hello pop1234 and sadaghiani,

I do not understand why you want to change things. As far as I know most frontend drivers are working OK (and most cases have done so for years), as with hundreds of downloads of my images nobody reports problems, apart from those reported by mr. speccy, which I can reproduce on my test receivers.

The last feedback of mrspeccy is that the frontend driver works OK with an HDMU image. This proves to me that that driver is basically OK. Please bear in mind that the last HDMU images are now more than 1.5 years old for SH4 boxes, and E2 still changes by the day. At the moment I am very busy with two other projects, but when more time becomes available. I will look into at least mrspeccy's problem.

Regards,

Audioniek.

pop1234
14.05.2020, 00:12
hello Audioniek (http://www.hdmedia-universe.com/board/member.php?1349-Audioniek)
i just wanted help
i have no problem just the last mistake that occurred during construction
http://www.hdmedia-universe.com/board/showthread.php?8015-fehler-beim-bauen-mit-Audioniek-git&p=123407&viewfull=1#post123407

thx

sadaghiani
14.05.2020, 06:46
hello Audioniek

I'm looking for a solution that has been around for years, and that's it
Lock the device when playing HD channels, which is a weak signal and requires the power switch to be turned on and off.

marto
20.05.2020, 10:01
Hello! I'm trying to install cuberevo_Audioniek_enigma2_gst-epl3_USB_CDK-rev1364.zip on IPbox9000HD. Installation is completed successfully, but after boot, the image is stuck on the language selection screen. Unfortunately, none of the RC buttons are working, neither those on the receiver, so I can't proceed further. Any help in this matter will be highly appreciated. Thanks in advance!

uniqad
20.05.2020, 21:50
All the images based on OpenPLi for all models of Cuberevo have the same compilation error! Just replace by means of telnet the evremote file with appropriate for your box model...

marto
21.05.2020, 08:51
Hi! I tried again by replacing the evremote2 file with the same from PKT and HDMU images which where working in their respective images, but unfortunately again not working with this image. RC and the buttons on the receiver are still not working. It looks like something else is required in order to make the RC operational?
I've replaced the evremote2 file via ftp after the image was already installed. Is that correct, or i have to put the new evremote2 into the .tar.gz image before installation?

uniqad
21.05.2020, 20:35
When get the screen for language choice, just login by means of telnet and try to install with opkg install this ipk (https://runigma.com.ua/feeds/openpli-homebuild/cuberevo_mini/evremote2_1.1%2Bgit683%2B1a7fd94-r0_cuberevo_mini.ipk). Of course use init 4 and init 3 commands first and last!

Audioniek
21.05.2020, 23:34
Hello! I'm trying to install cuberevo_Audioniek_enigma2_gst-epl3_USB_CDK-rev1364.zip on IPbox9000HD

I will look into this tomorrow (22/5) as I have finally found a testbox for this model. Please note that in my git evremote2 has been extensively rewritten to get rid of the loads of compiler warnings in other versions. Replacing (portions of) the code with that of other gits will probably not work.

Regards,

Audioniek.

marto
22.05.2020, 08:55
When get the screen for language choice, just login by means of telnet and try to install with opkg install this ipk (https://runigma.com.ua/feeds/openpli-homebuild/cuberevo_mini/evremote2_1.1%2Bgit683%2B1a7fd94-r0_cuberevo_mini.ipk). Of course use init 4 and init 3 commands first and last!
Hi! I've tried the above, but I'm getting "bad architecture file" error message and can't install. Furthermore I see that
it's for cuberevo_mini which Is a different receiver. Not sure if the remotes are the same...

@Audioniek
I'll wait for your fix.
Thanks in advance!

uniqad
22.05.2020, 14:26
it's for cuberevo_mini which Is a different receiver. Not sure if the remotes are the same
Its are the same! This method works on images from other developers, but Audioniek allready said why it's not work in this case.

Audioniek
23.05.2020, 20:48
I have had a look and surprise, surprise: the ABcom remote sends other codes as the CubeRevo one with which I developed. I can reproduce your problem, and will start work on a fix. Will keep you posted on progress.


UPDATE (24/5): FIXED. Cause was not the changed remote control codes, but the wrong driver for the frontpanel. Everything now tests OK and evremote2 is unchanged as it was OK. The changed RC codes are handled by the front processor apparently.

In the 2nd post the download link has been updated.

Regards,

Audioniek.

marto
24.05.2020, 17:05
All is OK now. Many thanks for your efforts and support in solving this issue!

marto
25.05.2020, 11:50
I’ve spent some time testing this image and found few issues so far…
In channel selection screen the left/right arrows are changing the user bouquets, but they are supposed to work as page up/page down, same as on every other image including OpenPLi. Same applies to “P/Pg” button in this screen. It’s just changing the bouquets… So, if I want to select channel at the bottom of the current bouquet, I have to scroll down through every channel in the list in order to reach it.
There is no option to choose channel by direct dialing with number buttons on the RC higher than 9. You can select channels from 1 to 9, but not 10 for example. It’s allowing to type just one digit.
When you watch channel, the left/right arrows on the RC behave as volume control nevertheless it’s not selected in the User interface settings! By default, in enigma2 they should be set for changing channels up/down.
When you put receiver in standby mode, the last viewed channel name remains on the front display instead of showing the clock. There is no option to switch on the cooling fan only when the receiver is running (auto mode). I believe this is all because of buggy CuberevoVFD plugin.
There are lot of missing options in the Hotkey selection menu such as “Softcam Setup”. Some buttons can’t be assigned at all.
In general, I believe most of the issues can be easily fixed. Thanks in advance! Keep on testing.

PS: In addition when the receiver is for long time in standby mode, it's not possible to start it... Only option is to use the power switch.
During watching a sat channel for a long time, more than an hour, sometimes the spinner shows up. Channel is not freezing and you can continue watching while the spinner is rotating, but is obstructing receiver to respond on further commands via the RC which is forcing you to restart from the power switch.
Same happens during watching IPTV channel, but much earlier. On a FHD channel after 5-10min the spinner shows up and stays permanent. On the other side there is no freez of the channel, you can continue watching for hours after that. Unfortunatelly at the end you have to restart the receiver via power switch in order to reboot and continue normal operation...

harryhase
25.05.2020, 16:08
i have an (two) unexpected problem: Version: hs7420_Audioniek_enigma2_gst-epl3_USB_P217_CDK-rev1364.zip // Octagon 1008Pse+ //BL: 6.37 (from other vendor)

1) Image is not booting when no serial communication is connected. - okay, that we can look later

2) after first boot and configure a while, it will never start again. And that i realy don't understand why. I saw it running was very impressed.
(i copied the same files, tries diffrent sticks, nothing, every time the same error)



[init] Wait until /dev/sda exists
[init] Time out on wait for /dev/sda, exiting...




BusyBox(2020-04-06 17:08:22 CEST) built-in shell (ash)


sh: can't access tty; job control turned off
/ #



Where i have to look, or what i have to change?

Audioniek
27.05.2020, 00:47
@marto: I can confirm the things you have observed; I have noticed them too. Apparently something inside Enigma2 dies, after which the spinner appears (when on), or it becomes impossible to return from standby. That the decoding of a transmitter continues is normal, as this is done in hardware. In both cases you lose the possiblity to control the receiver with the remote control or the frontpanel keys. As both functions are realised in the driver for the frontprocessor, it may be a solution to switch back to the original ipbox driver, although this needs fixing (that was the original problem and reason for my rewrite attempt). Unfortunately I do not have the time at moment to address this problem in depth.

@harryhase: you are experiencing a problem that I can not solve at the moment. There is nothing wrong with the image and also nothing wrong with what you are doing. The problem is the bootloader. The USB capable bootloaders for all HS7xxx models all share the same problem: after finding the USB stick to boot from they switch off the power supply to the stick, causing /dev/sda not to be made and the bootloop ending in a time out. This means the bootprocess is extermely stick dependent (I have only one stick out of more than 35 that sometimes works). In the past I have looked for a workaround for several times now and have not found one, other than fixing the bootloader, of which I do not have the source code.

I can have a look if somebody can get me the source code of the USB enabled bootloader, or at least the code to read/flash an .ird file.

Regards,

Audioniek.

marto
27.05.2020, 07:52
Hi, Audioniek and thanks for confirming the issues! Perhaps you can use the frontprocessor driver from "PKT Hyperion 5.5 CUBEREVO", which is a very stable image, but outdated already, or even from the latest HDMU images for this box...

harryhase
28.05.2020, 23:47
@Audioniek: Did you ever tried booting with active usb hub, that maybe works?
maybe we can ask nit or gost4711 if they have the source code, the titanit has a own bootloader

tanaka
29.05.2020, 17:56
@harryhase: you are experiencing a problem that I can not solve at the moment. There is nothing wrong with the image and also nothing wrong with what you are doing. The problem is the bootloader. The USB capable bootloaders for all HS7xxx models all share the same problem: after finding the USB stick to boot from they switch off the power supply to the stick, causing /dev/sda not to be made and the bootloop ending in a time out. This means the bootprocess is extermely stick dependent (I have only one stick out of more than 35 that sometimes works). In the past I have looked for a workaround for several times now and have not found one, other than fixing the bootloader, of which I do not have the source code.

I can have a look if somebody can get me the source code of the USB enabled bootloader, or at least the code to read/flash an .ird file.

Regards,

Audioniek.

but why didn’t we face the same issue with PKT image and your old images (Non Openpli) with the same bootloader?

Asking only to understand the difference.

Audioniek
01.06.2020, 05:53
@tanaka:

Good point. Apparently the PKT people have found a solution outside the bootloader I have not thought of yet. I will look into the problem again. If anyone has a suggestion for a solution within the image, I am glad to here it.

Regards,

Audioniek.

harryhase
04.06.2020, 15:51
okay, i see what we need to get it to boot; A kind of usb-reset or refresh of the usb devices. it is not a problem of the bootloader, because a part of the image is already running bevor it stop.

1) take a usb hub with at minimum 2 ports
2) let the device boot until you see the message of #100 in the terminal
3) pull off the usb-stick and
4) wait a second
5) plug the usb-stick into the other port
6) the device continuses the booting and the image starts


edit: not working every time, but now i can see the problem, if the usb-stick is not lightning, than it does not work, if it lights it works. i seems like the usb driver are not correct, so that it is not every time correct initialized

edit2: if i change the uImage (from PKT) then it all the time starts booting (okay, not starting, because not the right initialisation, but they have solved this issue)

aness
04.06.2020, 22:16
Thanks Audioniek (http://www.hdmedia-universe.com/board/member.php?1349-Audioniek) great work we wait to usb cubrevo images

kyk65
12.07.2020, 13:35
Hi Audioniek Cuberevo Mini II Micom front panel driver version V1.08Audioniek initializing
[cuberevo_micom] 1. = 0x08
[cuberevo_micom] 3. = 0x06
[cuberevo_micom] 5. = 0x02
[cuberevo_micom] Pos. response received (0xeb)
[cuberevo_micom] Command processed - remaining jiffies 119
[cuberevo_micom] 7. = 0x08
[cuberevo_micom] 9. = 0x06
[cuberevo_micom] 11. = 0x02
[cuberevo_micom] Pos. response received (0xeb)
[cuberevo_micom] Command processed - remaining jiffies 119
[cuberevo_micom] 13. = 0x08
[cuberevo_micom] 15. = 0x06
[cuberevo_micom] 17. = 0x02
[cuberevo_micom] Pos. response received (0xeb)
[cuberevo_micom] Command processed - remaining jiffies 120
[cuberevo_micom] Frontpanel version: 02.06.2008
[cuberevo_micom] Probe: Micom front panel real time clock
micom-rtc micom-rtc: rtc core: registered micom as rtc0
[cuberevo_micom] Unknown IOCTL 0x5401.
[cuberevo_micom] micomWriteString UTF8 text: [LOAD], len = 4
[cuberevo_micom] micomWriteString Non-UTF8 text: [LOAD], len = 4
[cuberevo_micom] Text: LOAD (len = 14)
[cuberevo_micom] close minor 0

ainouna
13.07.2020, 15:13
Hello everyone
for test
enigma2 external flash for hs 7429
https://www.mediafire.com/file/mp51u27c5x9agkb/hs7429_enigma2_USB-2-rev1419.zip/file

thank you audioniek for
your great work

Regards
ainouna (https://www.mediafire.com/file/mp51u27c5x9agkb/hs7429_enigma2_USB-2-rev1419.zip/file)
(https://www.mediafire.com/file/mp51u27c5x9agkb/hs7429_enigma2_USB-2-rev1419.zip/file)
(https://www.mediafire.com/file/mp51u27c5x9agkb/hs7429_enigma2_USB-2-rev1419.zip/file)

mountaineer
29.07.2020, 17:09
Thank you again for your hard work. I posted back a while about 1028 or at7500 having issues with a particular signal and posted a file for it. I have narrowed it down to 1 particular type of signal...DVB S2 30000 SR 5/6 FEC...does not matter if channel is MPEG 2 or 4 ... the tuner has trouble locking that signal...S2 8psk 30000 SR 5/6 FEC......thank you for looking at that.

Audioniek
03.08.2020, 14:22
Thanks for your effort. This will narrow things down quite a bit. I will try and find such a signal and see what by testbox does. I also have a question for you: have you tried watching the same signal with the factory firmware, and if so, do the same problems occur then as well? If not, there is potentially a driver problem, else it may be a limitation of the current hardware, as the symbol rate is rather high.

Regards,

Audioniek.

mountaineer
05.08.2020, 03:07
Plays perfect regular firmware, Thank you!


Regular Fw plays SR up to 31250 just fine...all FEC

HDMU/PKTEAM images play 30000 SR 8/9 FW and 31250 SR fine....just not 30000 5/6 FEC.....Must just be the 5/6 FEC at a higher SR

Hazel
13.08.2020, 14:15
Hallo Audioniek, danke für die großartige Arbeit. Mein alter Octagon SF1008se läuft jetzt super mit der "enigma2_gst-epl3_USB_CDK-rev1453.tar" von August. Die Untertitel konnte ich ausblenden und nach 3 Tagen läuft nun auch oscam tadellos. Jetzt macht es wieder Spaß, schöne moderne Oberfläche und dreamboxedit funktioniert mit diesem Image auch wieder. Einfach nur Top.

chaban
14.08.2020, 10:31
Hello Audioniek (http://www.hdmedia-universe.com/board/member.php?1349-Audioniek) ..

I tested the last compile of HS 7420...and we have problem

log file

http://www.mediafire.com/file/29k84c36ur2q2xu/Log+HS-7420+USB_P217_CDK-rev1453+.rar/file

pop1234
14.08.2020, 12:27
Hello Audioniek (http://www.hdmedia-universe.com/board/member.php?1349-Audioniek) ..

I tested the last compile of HS 7420...and we have problem

log file

http://www.mediafire.com/file/29k84c36ur2q2xu/Log+HS-7420+USB_P217_CDK-rev1453+.rar/file

try this

sudo ldconfig -v

chaban
14.08.2020, 16:20
Where i can put this command....? POP1234

pop1234
14.08.2020, 16:41
in terminal

chaban
14.08.2020, 16:49
Yes...but this is USB version ...!

Drielander
15.08.2020, 17:32
Hallo Audioniek,

heute wollte ich einen meiner TF7700 mit der Version tf7700_Audioniek_enigma2_gst-epl3_flash_P217_CDK-rev1453 aktualisieren, aber das gelang nicht: nach dem UBoot kommt Linux und da bleibt die Prozedur stehen (zwei verschiedene USB2.0-Sticks getestet).
Nutze ich die vorherige Version tf7700_Audioniek_enigma2_gst-epl3_flash_P217_CDK-rev1251, startet der Stick die Installationsprozedur.
Irgendeine Idee, was ich da machen kann?

Audioniek
15.08.2020, 20:50
Hallo Drielander,

Sie machen nichts falsch: es fehlt ein Datei. Ich werde mich bemuehen Morgen ein bessere .zip zu Posten.

Gruesse,

Audioniek.

Drielander
15.08.2020, 21:23
.... es fehlt ein Datei.

Ich dachte mir sowas in der Art, wobei beide Zip die sieben Dateien enthalten. ;)

Ich habe zwar immer noch nicht die Probleme mit den diversen Ton-Einstellungen "original/1. Fremdsprache" etc. gelöst und auch sonst gibt es Bedien-Schwierigkeiten (wie schalte ich z. Bsp.Timeshift ab?), aber mir gefällt das OpenPli-Design richtig gut. :)

Gruß

Audioniek
15.08.2020, 22:02
Inzwischen steht ein bessere Version da. Ich mal rumsehen das Timeshift abzustellen. Auch im Keymap sind noch Fehler drin, woran ich schon arbeite, weil die heutige Keymap sehr veraltet ist.

Gruesse,

Audioniek.

Drielander
15.08.2020, 22:45
Inzwischen steht ein bessere Version da......

... und diese bessere Version habe ich direkt installiert: funktionierte einwandfrei - besten Dank! :)
Ja - diverse Übersetzungswechsel passieren schon noch: obwohl Deutsch angewählt, kommt ab und an doch noch english durch. ;) Das sind aber kleinere und nicht so wichtige Probleme, die man später lösen kann - die gute Bedienbarkeit hat meiner Meinung nach höhere Priorität.

Grüße

Drielander
16.08.2020, 13:42
@Audioniek

ich habe ein größeres Problem: die Zeit des im TF770 gezeigten Programms differiert zur Echtzeit um genau zwei Stunden. Liegt das am Timeshift? Ich möchte die Ereignisse gerne in Echtzeit sehen und nicht um 2 Std. verschoben, sodass ich jetzt wieder auf das HDMU-Image zurückflashen muss.

Audioniek
20.08.2020, 05:08
Wahrscheinlich liegt das am falsch eingestellten Zeitzone. Im Erstassi funkzioniert bei mir Generic und CET OK. Die vorgegebe Wert Europe/Amsterdam gibt das gemeldete Resultat da Enigma2 dann mit GMT ohne Sommerzeit arbeitet. Intern in OpenPLi ist die Verwaltung des Zeitzones im Moment nicht in Ordung seit man "Geolocation" eingefuehrt hat.
Die Zeitzone laesst sich auch spaeter noch im Image korrigieren.

Das alles seht auf meine "Todo-Liste"

Gruesse,

Audioniek.

Drielander
20.08.2020, 07:38
Guten Morgen @Audioniek,

das klingt doch schon mal gut. Das versuche ich zu testen.

Leider gab es gestern bei mir beim Möbel-Umräumen einen Zwischenfall mit genau dem zweiten TF7700, auf dem OpenPli läuft. Ein Regalbrett im Sideboard, auf dem der TF7700 stand, hing etwas schief (hatte ich nicht gesehen) und als ich das Sideboard verschob, rutschte der Receiver vom Brett und fiel aus 70cm Höhe herunter mit der Front auf den Boden. Äußerlich keine Schäden sichtbar, aber er geht nicht mehr an. :mad: Bin ich selber schuld - ich hätte den Topf vor den Verschieben herausnehmen müssen.

Drielander
20.08.2020, 14:07
..... Generic und CET OK. ........

Das hat schon mal bestens funktioniert - ich habe dazu die HDD aus dem beschädigten TF7700 in den intakten TF7700 montiert. Besten Dank für den Tipp.


.. Das alles seht auf meine "Todo-Liste"

Wäre super, wenn Du die schon geschilderte Problematik mit den "Untertiteln für Gehörgeschädigte" in die LIste aufnehmen könntest, denn das trübt das Vergnügen mit OpenPli erheblich. Offenbar sind da diese UT schon als Default eingestellt. Hier mal ein paar Beispiele.

15903 15904 15905 15903

Da ich nicht weiß, wo ich was verstellen muss, lass ich es lieber. Nachher wird es noch schlimmer.

Drielander
08.09.2020, 12:38
@Audioniek

Gibt es neue Erkenntnisse bzgl. der Untertitel-Sache?
Wäre schön, was zu hören, denn inzwischen ist mein TF77xx-Gerätepark um ein paar TF7750 größer geworden. Es besteht also Bedarf für ein Untertitel-freies OpenPli.

Gruß

Audioniek
15.09.2020, 16:55
Es besteht also Bedarf für ein Untertitel-freies OpenPli.

Hallo Drielander,

Bisschen Geduld bitte, sieh mal hier (http://www.hdmedia-universe.com/board/showthread.php?11806-evremote2-keynames-and-key-assignments&p=123502#post123502).

MfG,

Audioniek.

Drielander
15.09.2020, 18:18
Hallo Audioniek,

Danke für Deine Antwort.

Ich bin aber nach langem Suchen, Lesen, Probieren mit meinem TF7750 inzwischen Untertitel-frei. :)
Beim Kommentar-Ton für Sehbehinderte/Blinde muss ich noch genauer prüfen. Ich beobachte das weiter und werde, wenn es auf Dauer funktioniert, kurz Hinweise mit Bildern einstellen.

Allerdings habe ich noch zwei andere Probleme, deren Lösung ich noch kein Stück näher gekommen bin: teilweise Tonausfall bei Senderwechsel, den ich durch Vor-Zurückzappen zumindest für den Moment beheben kann, der aber nicht immer auftritt und auch nicht immer bei den selben Sendern. Das Phänomen wandert - keine Regelmäßigkeit.
Dazu Total-Tonausfall beim Sender WDR3, aber nur bei bestimmten Sendungen des WDR3. Im Moment, in dem WDR3 angewählt wird, hört man für nicht mal eine Sekunde den Ton, der aber sofort weggeht. Was da genau passiert, kann ich nicht sagen.

Danke aber, dass Du beim Thema OpenPli für TF77xx dran bleibst und so eine etwas moderne Oberfläche ermöglichst!:sm49:

Gruß

Audioniek
02.10.2020, 15:24
Hallo Drielander,

Der Tonausfall beim Zappen habe ich auch beobachtet und auch bei andere Boxen. Es ist also nicht ein Topf-Problem sondern ein Problem im allgemeinen Image. Auch die Loesung ist die gleiche: mal hin- und herzappen, und der Ton ist wieder da. Ich habe leider keine Ahnung wo ich dass suchen muss. Danke fuer die Bestaetigung des Problemes.

Ich habe in die heutigen Images (October 2020) erneut ein Versuch gemacht die Senderliste Deutsch aus zu bessern. Die Untertitel sollten nun alle abgeschaltet sein. Falls nicht, dann sollte das Beseitigen einfacher sein da die voellige von OpenPLi erwarte Funktionalitaet mit den Farb-Tasten wieder einwandfrei functionierte am Testbox. Ebenfalls habe ich die Einstellungen der Tonkanaele nachgelaufen. Jetzt ist der Ton Dolby AC-3 (wenn verfuegbar) oder MPEG-Deutsch ohne zusatzliche Sachen wie Beschreibung oder Original-Ton.

Gruessen,

Audioniek.

Hazel
03.10.2020, 08:55
Guten Morgen Audioniek,

ich habe für meinen Octagon 1008 jetzt die Oktober Software auf USB gespielt. Alles läuft für die alte Box super, nur bekomme ich die Untertitel nicht weg (bei der August Software schon). Hast du eine Lösung, finde nichts zum ausschalten der Untertitel. Danke auf jeden Fall, dass Du dir die Arbeit machst.

Audioniek
03.10.2020, 23:49
Hallo Hazel,

Untertitel ändern/ausschalten soll wie folgt funktionieren müssen::

1. Gewünschtes Programm anwählen;
2. Auf Farbtaste gelb drücken;
3. Im Tonkanalauswahlfenster nochmals Farbtaste gelb drücken;
4. Ausschalten: mit Kreuz angezeigte Untertitel anwählen und OK drücken;
5. Ändern: Gewünschte Untertitel anwählen und OK drücken;
6. Mit wiederholten Exit-taste wieder heraus.

Gruesse,

Audioniek.

Drielander
04.10.2020, 14:45
Hallo Audieniek,

zunächst herzlichen Dank, dass Du dran bleibst und u. A. auch den Topf mit Images versorgst. :)

Das Thema "Untertitel" hatte ich ja bereits schon so "gelöst", indem ich an den entsprechenden Stellen auf Disabled gestellt hatte. Damit war generell unabhängig vom Programm kein Untertitel mehr vorhanden. Noch besser natürlich, wenn es direkt als Default gesetzt ist.
Das Thema "Tonausfall" geht bei meinen Töpfen aber etwas weiter: das Vor-/Zurückzappen hilft zwar an allen Stellen (da nicht immer an gleicher Stelle wiederkehrend), aber der Tonausfall mit gaaanz kurzem Tonschnipsel am Anfang wie beim WDR3 entsteht exakt nur dort. Da hilft kein Vor/Zurück.

Grüße
Drielander

Drielander
04.10.2020, 19:52
@Audioniek

Ich habe vorhin das letzte Image geflasht. Leider musste ich feststellen, dass nach wie vor die Untertitel angezeigt werden.

15966

Wie schon beim Vor-Image habe ich an dieser Stelle die Schieber "Untertitel für Gehörgeschädigte erlauben" und "Bevorzuge gespeicherten Untertitel des Senders" auf rot/no gesetzt

15967

... und nach einem GUI-Neustart waren sie weg.

WDR3 hat mehrheitlich immer noch keinen TON.

Drielander
04.10.2020, 20:57
@Audioniek

... und nach einem GUI-Neustart waren sie weg.

.

Leider nicht ganz - da war ich zu optimistisch, wie ich eben feststellen musste.
Irgendwie funktioniert das nicht mehr so wie beim vorletzten Image.

Audioniek
05.10.2020, 14:29
Hallo Drielander,

Irgendwie bekomme ich den Eindruck dass die Kanalliste nach ein Neu-installation zurückgesetzt wird, da ich die gemeldete Probleme nicht reproduzieren kann. Die Kanalliste enthält per Programm die Settings für Audiokanal und Untertitel. Wenn also eine alte Kanalliste zurückgesetzt wird, kommen auch die alte Einstellungen wieder zurück.

Ich wird mich nochmals darum kümmern. Wenn alle Programme eingestellt sind wie gewünscht, die Box in Deep Standby schicken, und dann wieder hochfahren. Direkt danach die vollständige Kanalliste per ftp downloaden (also fast alle Dateien aus /etc/enigma2) und diese Liste benutzen beim zurücksetzen.

Grüsse,

Audioniek.

Drielander
05.10.2020, 15:26
Hallo Audioniek,

ich habe meine Kanalliste (noch vom HDMU-Image stammend) mit dem SatChannelListEditor über LAN zurückgeschrieben, da sie leider in den Settings nicht gesichert & zurückgeschrieben wird. Für mich gehören Kanallisten zu den Settings dazu.

Ich werde jetzt mal nach dem Flashen keine Kanalliste auf den Topf hochladen, sondern die vorhandene Liste so belassen und erstmal schauen, wie es sich mit den Untertiteln verhält.
Allerdings verstehe ich nicht, wieso die Untertitel von den einzelnen Programmen abhängig sind. Es sollte doch möglich sein, eine generelle Abschaltung aller Untertitel zu erreichen.

Grüße
Drielander

Drielander
05.10.2020, 19:27
Hallo Audioniek,

ich habe gerade den Topf neu geflasht, keine Settings & keine Senderliste übernommen, sondern diese neu am PC mit dem SatChannelListEditor erstellt und dann auf den Topf hochgeladen. Auch an der Konfiguration habe ich nichts geändert.
Ergebnis: alle Dialog-Untertitel für Hörbehinderte plus Ton-/Musik-/Geräusch-Beschreibung werden nach wie vor angezeigt.

15968 15969

Beim WDR gab es bislang keinen Tonausfall - das werde ich weiter beobachten.


Grüße
Drielander

Drielander
06.10.2020, 12:53
Hallo Audioniek,

nachdem das gestern nicht den gewünschten Erfolg brachte, habe ich nochmal neu aufgesetzt. Die Untertitel waren da, wo gesendet wurde, natürlich zu sehen.
Dann bin ich an die Stelle gegangen, wo ich bislang immer gestellt habe:

15970

Es ist keine Einstellung unter "Audio-Video/Untertitel-Einstellungen", sondern eine unter "Audio-Video/Automatische Tonauswahl", wo ich die markierte Stelle "Untertitel für Gehörgeschädigte erlauben" auf nein/rot gesetzt habe und noch zusätzlich "Bevorzuge Untertitel des gespeicherten Senders". Das wirkt beim Topf auf alle Programm-Einstellungen - es ist bislang kein UT zu sehen und ich hoffe, das bleibt auch so - auch, was den Beschreibungskommentar für Blinde anbetrifft. ;)

Hier ein kleines Resümee:

....
Der Tonausfall beim Zappen habe ich auch beobachtet und auch bei andere Boxen. Es ist also nicht ein Topf-Problem sondern ein Problem im allgemeinen Image. Auch die Loesung ist die gleiche: mal hin- und herzappen, und der Ton ist wieder da. Ich habe leider keine Ahnung wo ich dass suchen muss.

Da muss ich damit leben - der Vorteil Deines OpenPli-Image für meinen alten Topf überwiegt für mich. ;)


....Ich habe in die heutigen Images (October 2020) erneut ein Versuch gemacht die Senderliste Deutsch aus zu bessern. Die Untertitel sollten nun alle abgeschaltet sein. Falls nicht, dann sollte das Beseitigen einfacher sein da die voellige von OpenPLi erwarte Funktionalitaet mit den Farb-Tasten wieder einwandfrei functionierte am Testbox. Ebenfalls habe ich die Einstellungen der Tonkanaele nachgelaufen. Jetzt ist der Ton Dolby AC-3 (wenn verfuegbar) oder MPEG-Deutsch ohne zusatzliche Sachen wie Beschreibung oder Original-Ton. .....

Wie ich schon schrieb, war das beim Topf nicht der Fall, aber die zwei (oder vielleicht auch nur der obere) auf rot gesetzt brachte den gewünschten Erfolg.
Bei den Farbtasten kommt man mit GELB + GELB + BLAU ins UT-Menü, aber die beiden wichtigen/richtigen Schalter werden dort nicht angezeigt, weil sich die Einstellung unter "Automatische Tonauswahl" befindet.

Eine Veränderung gegenüber dem vorletzten Image meine ich festgestellt zu haben: drücke ich die INFO-Taste, kam früher für ein paar Sekunden bislang nur unten das erweitere Info als PullUp-Menü.
Beim jetzigen Image zeigt sich ganz kurz diese Info, springt aber direkt weiter in die komplette Beschreibung mit kleinem Bild links - das Ganze aber als Vollbild.

Vielleicht kannst Du bei Gelegenheit da mal schauen.

Grotjes naar Ridderkerk
Drielander

ha-me
06.10.2020, 20:04
hello Audioniek,
thanks for your hard work.
i have two questions: what password at dcc, and why cannot be installed mediaportal/e2iplayer/ect?
(python dependencies are missing displayed) is this correct?

regards ha-me

Audioniek
06.10.2020, 23:16
... sondern diese neu am PC mit dem SatChannelListEditor erstellt und dann auf den Topf hochgeladen.

Dass ist das gleiche als Kanallist zuruecksetzen. Wahrscheinlich enthealt die mit SatChannelListEditor erstellte List entweder keine Settings fuer Untertitel oder die falsche. Um das alles im Griff zu bekommen, erst mal eine Frage:
Ohne etwas zu machen, also frisch nach dem Flashen: sind im Favouriten Deutsch die Untertitel weg? Wenn Ja dann ist dies alles ein Kanallisten-Problem und kein Image-Problem.

Gruesse,

Audioniek.

Audioniek
06.10.2020, 23:54
Bei den Farbtasten kommt man mit GELB + GELB + BLAU ins UT-Menü, aber die beiden wichtigen/richtigen Schalter werden dort nicht angezeigt, weil sich die Einstellung unter "Automatische Tonauswahl" befindet.

GELB + GELB + BLAU? Da stimmt etwas nicht.

Die Untertitelwahl findet gar nicht im angegebenen Menü Audio-Video/Untertitel-Einstellungen statt, sondern durch drücken von GELB (Audiowahl) gefolgt durch GELB (Untertitelwahl), während die ein zu stellende Sender geschaut wird, also nicht nach drucken der Taste MENU oder vom Senderliste aus.
In das dann angezeigte Fenster werden die ausgestrahlte Untertitel angezeigt und gibt es kein Möglichkeit für BLAU (nur GELB -> Audiowahl). Wenn einer Untertitel eingeschaltet ist, befindet sich ein Kreuz am Ende. Zum ausschalten diese Untertitel anwählen und OK drücken damit das Kreuz verschwindet. Dann mit EXIT zurück nach Fernseh-Schauen. Das Fenster für Audiowahl (Nach dem ersten GELB, oder nach GELB im Untertitelfenster) arbeitet auf gleichen Weise. Dies bei allen Sender machen deren Audio- oder Untertitel-Einstellung geändert werden muss. Wenn E2 danach normal herunter gefahren wird, werden die Einstellungen im Kanalliste gespeichert und beim nächsten Einschalten wieder hervor geholt.

Das Menü für Audio-Video/Untertitel-Einstellungen stellt nur das Verhalten ein wenn nichts im Kanalliste eingestellt wurde, oder die Kanalliste ein Einstellung enthält die nicht gültig ist. Dieses Menü ist nicht gedacht um mit nur wenige Handlungen die ganze Kanalliste mit Beziehung zur Audio oder Untertitel zu bearbeiten sondern näher zu bestimmen was beim Zappen mit Audio und Untertitel gemacht werden soll, ausgehend von die vorher gemachte Einstellungen dafuer (mit nur GELB...).

Groeten uit Ridderkerk,

Audioniek.

JamesBond
07.10.2020, 12:53
Hi Audioniek (http://www.hdmedia-universe.com/board/member.php?1349-Audioniek), very good and stable image.

In my cuberevo mini every time I choose reboot from the menu gets stuck with the "Your receiver is rebooting" forever, only cutting power or pressing the front panel power + ok button solves it.
Also I can't download/install any plugins or new packages, the list download is always empty.
Another problem is that CAM CI modules are not working. There isn't menu for them and they are not detected.

Just as curiosity since I'm doing some changes and developing, can you tell me what makes the channel names showing on the VFD? How really it works?
Also how to fix the remote not typing numbers sometimes but works navigating the menus?

Thanks. :sm46:

Audioniek
08.10.2020, 23:35
In my cuberevo mini every time I choose reboot from the menu gets stuck with the "Your receiver is rebooting" forever, only cutting power or pressing the front panel power + ok button solves it.

I will flash the latest image into my mini2 and have a look at it.


Also I can't download/install any plugins or new packages, the list download is always empty.

This is correct: see here (http://www.hdmedia-universe.com/board/showthread.php?11200-Audioniek-Images-general-info). Please remember I am a single person with limited resources and time, not a whole team. Another reason is that I cannot test every plugin potentially available. There is however a plan to at least include a version of OSCAM in the image as standard, as some models covered do not have CI slots.
Regarding plugins, you can of course try and set another feed (caution: HDMU plugins do not work) and use those.


Another problem is that CAM CI modules are not working. There isn't menu for them and they are not detected.

I consider this a serious high priority error that should be fixed on the short term. Something to do this weekend perhaps.


Just as curiosity since I'm doing some changes and developing, can you tell me what makes the channel names showing on the VFD? How really it works?

The channel names on the VFD are shown using the plugin VFD-Icons in /user/lib/enigma2/python/Plugins/SystemPlugins. This standard plugin is on Cuberevo's enhanced by a second plugin in /user/lib/enigma2/python/Plugins/Extensions called CuberevoVFD. As these written in Python they are relatively easy to read, understand and change. Lease note that for space reasons only the compiled .pyo is present in the image. You can either uncompyle it, or if you have a build environment yourself look in either X/build_source/enigma2/lib/python/Plugins/SystemPlugins or .../Extension to find the .py.

The two plugins also handle the showing of the icons on the front panel display.


Also how to fix the remote not typing numbers sometimes but works navigating the menus?

This is regulated in the keymaps. The definitive one is located in /usr/local/share, and it original is in the build environment at X/root/root_enigma2/usr/local/share/enigma2/keymap_cube.xml.
I have recently put in a lot of work to make the keymap fully functional again as they were quite old and some things did not work at all with the current E2. I tried to leave the original keymap used by OpenPLi intact a much as possible, and only to add in the extra's required by the remote control involved. The additions are all commented and eletios commented out. More info on this can be found here (http://www.hdmedia-universe.com/board/showthread.php?11806-evremote2-keynames-and-key-assignments).
If you want to experiment with keymap.xml a word of caution: a broken one is fatal and makes E2 abort very early in its startup. As a check I usally first load it in a browser that either shows it when OK or in case of Firefox points out the offending line.

Regards,

Audioniek.

JamesBond
09.10.2020, 01:11
Thanks for the information.
My image tests are missing the plugin VFD-Icons so I copy from your image, but still no go and I have no channel names on the VFD, this needs some sort of running service? Something that need to start on boot?

Regarding the remote keys I also copy your keymap.xml but also no improvements, any menu that uses key numbers to input like an IP address doesn't work. All the rest like navigation on the menus, pressing ok, color bottoms for the special menus, etc. are working.

Drielander
12.10.2020, 10:28
.....Ohne etwas zu machen, also frisch nach dem Flashen: sind im Favouriten Deutsch die Untertitel weg? Wenn Ja dann ist dies alles ein Kanallisten-Problem und kein Image-Problem.

Genau das mache ich jetzt mal und setze komplett neu auf. Ich habe nämlich gestern doch noch zwei Sender mit Untertitel für Schwerhörige bei Pro 7 & Kabel 1 als auch Kommentar für Handlungsbeschreibung (Blinde) bei einem anderen Sender entdeckt.
Da ich nur meine Kanallisten aus der HDMU-Zeit habe, wäre ein Tipp für eine Kanallisten-Neuerstellung hilfreich. Allerdings habe ich in den Default-Listen viele Programmlücken entdeckt - die HD-Versionen der Kanäle sind gar nicht gelistet. Man müsste die erst zusammensuchen.
Aber jetzt teste ich mal, um Deine Frage beantworten zu können.

Drielander
12.10.2020, 11:46
Und schon ist das Ergebnis da: die Untertitel (hier für Taube) sind nicht weg, womit die Ursache - wenn ich Dich richtig verstanden haben - nach Deiner Auslegung im Image zu suchen ist.

15971

Wieso plötzlich das Netzwerk, das bei allen Töpfen bislang prima funktioniert, nach den neuen Flash von heute bei diesem Topf nicht mehr geht, muss ich noch herausfinden.

Drielander
12.10.2020, 13:04
.....In das dann angezeigte Fenster werden die ausgestrahlte Untertitel angezeigt und gibt es kein Möglichkeit für BLAU (nur GELB -> Audiowahl). Wenn einer Untertitel eingeschaltet ist, befindet sich ein Kreuz am Ende. Zum ausschalten diese Untertitel anwählen und OK drücken damit das Kreuz verschwindet. Dann mit EXIT zurück nach Fernseh-Schauen. Das Fenster für Audiowahl (Nach dem ersten GELB, oder nach GELB im Untertitelfenster) arbeitet auf gleichen Weise. Dies bei allen Sender machen deren Audio- oder Untertitel-Einstellung geändert werden muss. Wenn E2 danach normal herunter gefahren wird, werden die Einstellungen im Kanalliste gespeichert und beim nächsten Einschalten wieder hervor geholt.
...

Mit Deinen obigen Erklärungen, die mir zeigten, dass ich an verkehrter Stelle schraubte, habe ich es bei zwei Sendern geschafft, die Untertitel abzuschalten. Schon mal ein Anfang. :)
Ich hatte schon mehrmals vergeblich eine Bedienanleitung für OpenPli gesucht.

Audioniek
14.10.2020, 14:46
Schon mal ein Anfang. :)

Gratuliere.


Ich hatte schon mehrmals vergeblich eine Bedienanleitung für OpenPli gesucht.

So weit ich weiß gibt es keine. Ich finde das auch ein Fehler; man muss manchmal in die Code schauen wie Sachen gemacht werden müssen

Ein Kanalliste ist immer ein Geschmackssache. Ich liefere ein Kanalliste mit die als Startpunkt gedacht ist. Die Liste ist ein Variante von der Liste die ich persönlich täglich verwende.

Das erzeugen einer völlig neue geht am einfachsten mit einen Kanallisten-editor, z.B. Dreamboxedit. Nach erstellen der Verbindung mit den Receiver, die heutige Kanalliste herunterladen im Programm. Dann alle Bouquets löschen, gefolgt durch das löschen alle Sender, bis auf einer (nur Das Erste HD z.B.). Die fast minimale Liste zurück nach den Receiver schicken.

Man kann natürlich auch ein beliebige Kanalliste als Anfangspunkt nehmen.

Am Receiver die Tuner setup ändern damit sie die Außenanlage entspricht. Dann ein Scan der wichtigsten Satellit machen mit Netzwerkscan eingeschaltet, damit evt. fehlende Transponder gefunden werden. Nach den Scan die Kanalliste wieder im Editor laden. Die Scanresultaten befinden sich in das Bouquet LastScanned. Im Editor die gewünschten Bouquets für die eingescannte Satellit definieren und die im jeden Bouquet gewünschten Sender von LastScanned kopieren. Auch die Reihenfolge im Editor korrigieren. Wenn alles für diesen Satellit nach wünsch ist, die Kanalliste wieder im Receiver laden. Dies alles für jede verfügbare Satellit wiederholen, bis alle gewünschte Bouquets da sind.

Bemerkung: wenn dies nicht von Editor aus gemacht wird, muss am Receiver ein Enigma2 Neustart gemacht werden nach jeder download von neuen Daten, damit die neue Daten im Flash geschrieben und permanent gespeichert werden.

Als Abschluss die Untertitel und Tonkanäle per Programm einstellen (GELB, usw). Wenn alles endlich nach wünsch ist die fertige Kanalliste sicherstellen für Verwendung beim nächsten Update.

Ich hoffe dies hilft etwas.

Groeten uit Ridderkerk,

Audioniek.

Drielander
14.10.2020, 15:29
Hallo Audioniek,

so langsam verstehe ich die Bedienung von OpenPli etwas besser - Deine Anleitung hat sehr geholfen.
Ich habe gestern noch ein paar Tests mit den drei letzten Images gemacht und dabei festgestellt, dass sie auf die FB-Tasten unterschiedlich reagieren. Beim letzten Image komme ich mit GELB-GELB zu den UT-Einstellungen - das funktioniert inzwischen gut.
Bei den zwei Images davor allerdings bekomme ich beim ersten GELB bereits ein ganz anderes Bild:

15972

Grund, weshalb ich zurückgehen wollte, war folgender (schon mal erwähnt): Drücke ich beim letzten Image die Info-Taste, dann sollte kurz das bisher übliche Bild kommen, was nach 5 Sekunden automatisch verschwindet,

15973

Hier leider nicht: das normel Info-Bild kommt für max. 2 Sekunden, springt aber sofort in einen anderen Modus und bleibt dann so stehen:

15974

Das ist ja fast schon die Inhaltsbeschreibung. Ich muss dann über Return zurückgehen. Lässt sich das wieder so machen, dass nur die kleine Info aufpoppt, wie es bei den Vor-Images war?

Groeten uit Drielanden
Drielander

Audioniek
16.10.2020, 12:41
Wie im Änderungen-Übersicht genannt, ist mit den neuen Keymap die Bedienung auf einigen Stellen verändert und mehr in Übereinstimmung mit das von OpenPLi gedachte Design. Es gibt beim Topf ein Anzahl von Kompromisse da relativ viel von OpenPLi erwartete Tasten auf die Fernbedienung fehlen.

Ich werde mich beim Topf nochmal herum sehen ob noch Sachen optimiert werden können.

Gruesse,

Audioniek.

Drielander
20.10.2020, 09:59
Hallo Audioniek,

ich finde die OpenPli-ähnlichen Keymap prima, wobei ich relativ wenig mit Funktionstasten mache. Aber die Bedienung der UT via gelb/gelb passt. ;)

Genereller Punkt: der Topf ist Hardware-mäßig (CPU, RAM, ..) schon ab Werk nicht der "Rennwagen", aber manchmal habe ich das Gefühl, als wäre er mit OpenPli überfordert. Es gibt einige Warte-Kreisel im Normalbetrieb und auch Freezer, aus denen ich nur via Stecker ziehen & Neustart rauskomme. Sowas passiert mit dem HDMU-Image eher nicht.

Was die Kanalliste angeht, habe ich aus Openpli heraus eine komplett neue Liste erstellt (keine alten HDMU-Liste mit irgendwelchen früheren Einstellungen mehr), diese dann im SatChannelListEditor in die richtige Reihenfolge gebracht und separat auf dem PC abgelegt. Danach die UT-Einstellungen vorgenommen, im Topf durch Restart hinterlegt und ein Backup am PC gespeichert. Kanallisten sind jetzt nach Image-Version getrennt gespeichert. ;)

Grüße
Drielander

Audioniek
21.10.2020, 16:21
Genereller Punkt: der Topf ist Hardware-mäßig (CPU, RAM, ..) schon ab Werk nicht der "Rennwagen", aber manchmal habe ich das Gefühl, als wäre er mit OpenPli überfordert. Es gibt einige Warte-Kreisel im Normalbetrieb und auch Freezer, aus denen ich nur via Stecker ziehen & Neustart rauskomme. Sowas passiert mit dem HDMU-Image eher nicht.

Da haben Sie natürlich völlig recht. Der Topf ist inzwischen fast 12 her entwickelt worden, und niemals für Enigma2 gedacht. Außerdem verwendet Enigma2 relativ viel interpretierte Python Code die real time übersetzt werden muss. Das alles macht dass der Topf eigenltich nicht optimal ist für diese Anwendung.

Was auch nicht hilft, ist das OpenPLi die Unterstützung von Resource-armen Boxen wie der Topf schon eine Weile her eingestellt hat und deswegen davon ausgeht das es "moderne" Mengen an Speicher und CPU-Power gibt.

Die letzte HDMU Images sind inzwischen zwei oder mehrere Jahren alt, und basieren sich auf genau so alte OpenPLi Versionen.

Aus diesen Gründen bevorzuge ich darum Neutrino auf alte Boxen, manchmal auch weil das Alles dann noch im Flash Speicher passt (leider nicht beim Topf). Neutrino ist ganz in C(++) geschrieben und da ist die Performance kein Thema.

Gratuliere mit die gelungene Kanalliste.

Grüße,

Audioniek.

Drielander
21.10.2020, 16:42
....Aus diesen Gründen bevorzuge ich darum Neutrino auf alte Boxen, manchmal auch weil das Alles dann noch im Flash Speicher passt (leider nicht beim Topf). Neutrino ist ganz in C(++) geschrieben und da ist die Performance kein Thema. .....

Neutrino habe ich irgendwie noch schwach als "Rennpferd" in Erinnerung. Basierte nicht gli auf Neutrino - siehe D-Box2 (Philips) in der Signatur.

Vorhin habe ich im AAF-Forum in alten AAF-Image-Erinnerungen geschwelgt und dabei einen inzwischen sehr ruhigen Thread gefunden, der deren TitanNit für den TF7700 zum Thema hatte. Leider ist es nicht weiter verfolgt worden. Wäre das nicht was, den Neutrino-Gedanken nochmal aufzugreifen?

Grüße
Drielander

Audioniek
25.10.2020, 15:15
Wäre das nicht was, den Neutrino-Gedanken nochmal aufzugreifen?

Neutrino lässt sich seit Jahren in meinen buildsystem auch für den Topf bauen und kann genauso installiert werden wie Enigma2. Es gibt die Wahl aus drei verschiedene Neutrino Varianten: MP-DDT, Tangos oder HD2.

Grüße,
Audioniek.

Drielander
25.10.2020, 15:59
Hallo Audioniek.

na - das klingt doch sehr interessant. :)
Ich kenne jetzt die Unterschiede zwischen MP-DDT, Tangos oder HD2 nicht, aber wenn Neutrino doch schlanker ist als E2, wäre das doch eine gute Option für den Topf. So schick ich OpenPli finde, aber damit pfeift der Topf echt auf dem letzten Loch.
Ich habe auch Kontakt mit dem Administrator vom AAF-Forum aufgenommen, der für mich mal nach den damaligen Pre-Alpha-Images von Titanit schauen wollte.

Hättest Du denn ein passendes Neutrino-Image, das ich mal testen könnte?

Grüße
Drielander

Audioniek
25.10.2020, 18:02
Hättest Du denn ein passendes Neutrino-Image, das ich mal testen könnte?

Hier ist etwas zum herumspielen:

15986

Es ist ein alteres Tango's Neutrino V3.8.0. Ein neuere Version von Tango's laesst sich im Moment nicht bauen wegen Compilations-Probleme.

Das Image ist (noch) nicht spezifisch maßgeschneidert für den Topf, aber es startet und gibt ein Eindruck. V- und V+ am FB funktionieren noch falsch (die Frontpanel-Tasten für Volume funktionieren allerdings OK).

Die Unterschiede zwischen MP-DDT, Tango's und HD2 sind ein Bisschen Gesmackssache. MP-DDT und Tango's sind aenlich mit Tango's weiter entwickelt. HD2 gleicht wahrscheinlich am meisten die alte ursprüngliche Code an und hat ein andere Skin. Ich habe ein Vorliebe für Tango's.

Gruße,

Audioniek.

Drielander
27.10.2020, 16:58
So - habe das Image mal geflasht. Schaut interessant aus, erinnert mich an das gli-Image auf der D-Box 2.
Müsste noch viel gemacht werden, um es etwas zu aktualisieren und besser auf den TF77xx abzustimmen?

Gruß

Audioniek
28.10.2020, 19:24
Inzwischen habe ich die neueste Tango's compilieren können. Es baut durch, aber ein schnelle Test hat mich gezeigt das TTX nicht mehr funktioniert. Weitere Sachen die mir aufgefallen sind:


Wie schon bemerkt: V- und V+ am FB reagieren falsch;
Am Front reagieren die Kanalwahltasten nicht;
Nach dem Start leuchtet das MUTE-Icon.

Es ist durchaus möglich das noch andere Details ausbesserung gebrauchen können aber überwiegent funktioniert das meiste wie gedacht. Die Probleme mit den Tasten werden verursacht seit evremote2 geändert worden ist zur Optimalisierung von Enigma2. Da muss noch etwas gepatcht werden.

Grüße,

Audioniek.

JamesBond
11.11.2020, 20:40
Hi, so any idea for when the Cuberevo mini new image with fix's for the problems I reported?

JamesBond
17.11.2020, 22:08
Since there wasn't any new version I decided to compile myself from your latest "buildsystem" git source.
All ended up ok producing the cuberevo_mini_enigma2_gst-epl3_USB_CDK-rev1540 image, but the same problem persist, I get a lot of crashes and enigma reloads (green screen with text debug messages).
Also the shutdown hangs and still not working.

Also I tried using your SH4 and cuberevo meta sources on the official OpenPli git source but here was a no go, lots of warnings and error as starting the compile:


WARNING: Layer sh4-layer should set LAYERSERIES_COMPAT_sh4-layer in its conf/layer.conf file to list the core layer names it is compatible with.
WARNING: Layer cuberevo-layer should set LAYERSERIES_COMPAT_cuberevo-layer in its conf/layer.conf file to list the core layer names it is compatible with.
WARNING: Layer sh4-layer should set LAYERSERIES_COMPAT_sh4-layer in its conf/layer.conf file to list the core layer names it is compatible with.
WARNING: Layer cuberevo-layer should set LAYERSERIES_COMPAT_cuberevo-layer in its conf/layer.conf file to list the core layer names it is compatible with.
ERROR: ExpansionError during parsing /home/devserver/openpli-oe-core/meta-local/recipes-local/images/my-image.bb | ETA: --:--:--

Audioniek
18.11.2020, 17:00
Hello JamesBond,

I have the issues you reported on my todo-list but have not had time to address them. Regarding the crashes, I was surprised you calling it a green screen, while with my images it is blue. I can offer some help if you can report back the cause of the first blue screen occurring. After that is fixed, report then the fist, and so on.

New versions of my images appear around the first of the even months, the next is scheduled for around December 1st.

Regards,

Audioniek.

JamesBond
19.11.2020, 23:50
Ok tried to reproduce the green screen error but I couldn't, don't remember what I did, maybe by that time I had changed the skin and that's why, if that makes any difference on the background crash color, I don't know?!?!
Anyway I installed from scratch on a fresh formatted USB pen and I found 2 problems that gave the blue screen crash you said and a third new one.

1- I installed new settings and after settings wore updated I got the crash but stuck without doing the reboot again, here is the screen:
15997

2- On initial setup I choose 1080P@50Mhz, it works and I have good definition, next reboot all text and image becomes fuzzy, that's why the image from problem 1 is blurred.
I have to choose 30Mhz so in every boot the text and image stays sharp without that problem.

3- Another crash blue screen when changing the skin to the HD midnight something... but this time receiver does the proper enigma reload, here is the screen:
15998

Audioniek
20.11.2020, 18:22
@JamesBond,

Some remarks:

- The colours in the E2 crash screen are independent of the skin and are hard coded into the image. The same is true for the time the crash screen stays on screen before the restart, the number of debug lines in it and the size and font of the texts in it. In my images the background colour should be blue, the text should be white, the time is thirty seconds (longer than most, gives you time to read the screen or make a picture), and a rather large number of debug lines are displayed. Of those the bottom ones are the most important and the ones above it usually provide context.

- The cuberevo mini is rather old. On this old and limited hardware a resolution of 1080p at 50 Hz (not MHz) is not wise as this doubles the use of (rather scarce) memory and has the hardware running in overdrive, compared to 1080p25 or 1080p30. In addition not all TVs handle 1080p50 well for the same reasons. In PAL/SECAM areas a better choice is 1080p25, not 1080p30, although I prefer 1080i50 receiver as this is also the format usually used by the channel on HD.

- The blue screen provided as last is known to me: on SH4 the Overscanwizard is broken. I will have a look if I can either fix it by patching or take it out. If you skip the Overscanwizard, the image should start and run.The wizard is of little use anyway, because the image does have capability to correct overscan or recenter the picture, and many TVs have not either.

Regards,

Audioniek.

Audioniek
21.11.2020, 18:28
Overscanwizard is broken. I will have a look if I can either fix it by patching or take it out.

The Overscanwizard has meanwhile been fixed.

Regards,

Audioniek.

JamesBond
24.11.2020, 01:11
Ok I compile the latest version so I got the cuberevo_mini_enigma2_gst-epl3_USB_CDK-rev1551 and install it.

The crash without rebooting when downloading new settings still exists, now I got a good capture without fuzzy picture since I'm using the 1080p@25 as you recommended.
Here it is:
15999

The problem of changing skin disappear so as you said fixing the Overscanwizard looks like it fixed this. Nice !

Now some questions:
- If I want to use the feeds so I can install emus and so on from OpenPli will they work here?
- Is it difficult to fix your META-CUBEREVO and META-SH4 git or what I can do so they work with official OpenPli git source to try to compile a OpenPli recent version for Cuberevo-mini?

Thanks.

JamesBond
24.11.2020, 03:15
New problem !
I manually installed OSCAM so I can keep testing imaging stability watching and charging from free channels to encrypted ones for longer periods and I just found out that it doesn't open any encrypted channel apart I get valid ECM in OSCAM, TV screen stays black and no sound.
Could be this a dvbapi or demux problem?

Here is some OSCAM log:
2020/11/24 0240 029B198C c (ecm) dvbapiau (P: 1810:000000:7539:08AD:0000: #ECM_L:8E #CW=94BC055544DFEA0DF7275E7C3E08CE14 HOP:01): found (366 ms) by Servercccam (P/2/2/2) - M.ESTRENOSHD
2020/11/24 0255 029B198C c (ecm) dvbapiau (P: 1810:000000:7539:08AD:0000: #ECM_L:8E #CW=94BC055544DFEA0DC3FB9351D7F8EAB9 HOP:01): found (357 ms) by Servercccam (P/2/2/2) - M.ESTRENOSHD
2020/11/24 0210 029B198C c (ecm) dvbapiau (P: 1810:000000:7539:08AD:0000: #ECM_L:8E #CW=D1AB50CC6D16AE31C3FB9351D7F8EAB9 HOP:01): found (396 ms) by Servercccam (P/2/2/2) - M.ESTRENOSHD
2020/11/24 0225 029B198C c (ecm) dvbapiau (P: 1810:000000:7539:08AD:0000: #ECM_L:8E #CW=D1AB50CC6D16AE3120C1A78873558B53 HOP:01): found (378 ms) by Servercccam (P/2/2/2) - M.ESTRENOSHD
2020/11/24 0240 029B198C c (ecm) dvbapiau (P: 1810:000000:7539:08AD:0000: #ECM_L:8E #CW=5572B279B67493BD20C1A78873558B53 HOP:01): found (384 ms) by Servercccam (P/2/2/2) - M.ESTRENOSHD
2020/11/24 0255 029B198C c (ecm) dvbapiau (P: 1810:000000:7539:08AD:0000: #ECM_L:8E #CW=5572B279B67493BDEEBCEB95F717818F HOP:01): found (385 ms) by Servercccam (P/2/2/2) - M.ESTRENOSHD
2020/11/24 0210 029B198C c (ecm) dvbapiau (P: 1810:000000:7539:08AD:0000: #ECM_L:8E #CW=8A87F001BFCB3BC5EEBCEB95F717818F HOP:01): found (377 ms) by Servercccam (P/2/2/2) - M.ESTRENOSHD

I notice with your image on the OSCAM log an error showing up that I don't get on the main normal image I use with this same OSCAM version, this one:
2020/11/24 0240 029B198C c (dvbapi) ERROR: ioctl(CA_SET_DESCR): Invalid argument

Don't really know if It's related with the encrypted channels not giving image.

Audioniek
24.11.2020, 19:44
If I want to use the feeds so I can install emus and so on from OpenPli will they work here?

In general: no. Most plugins contain executables in binary, and OpenPLi those would be compiled for ARM or MIPS CPUs, so these will not work. Plugins that only contain Pyrhon however should.

The OpenPLi OSCam does not run as OSCam is a compiled binary. I am in the process though of adding OSCam in the buildsystem; but it is rather low on my list of priorities. The binary compiles OK at moment, the extra files are yet to be put in and the lot needs to be tested. I will push it all when I get the Dutch scrambled channels visible.



Is it difficult to fix your META-CUBEREVO and META-SH4 git or what I can do so they work with official OpenPli git source to try to compile a OpenPli recent version for Cuberevo-mini?

Yes it is. You need a lot more, for instance STLinux. OpenATV and OpenVisionE2 maintain gits that build for SH4 boxes.

Regards,

Audioniek.

JamesBond
24.11.2020, 22:56
I compile my oscam from the source for SH4, you are sayin that in your image the SH4 version will not work and needs a specific cross compilation?
I can compile for any valid official oscam system or CPU, etc. None of those possible will work on you image is that it?
If you need help to compile a proper version for your image, let me know.

I tried to find any SH4 valid source that I can compile a recent and modern image for my Cuberevo-mini since I love it, but I can't find anything out there.
The OpenVisionE2 images are too slow running and a lot buggy, regarding OpenATV I only can find really old stuff.
The best until now his from some Russian forum, but I have those problems I asked once, the VFD doesn't work and the number key buttons from remote are not working and even this remote problem could be easily fixed I didn't manage to do it.

Do you care to PM me some other links for those sources you know?
Thanks.

Audioniek
25.11.2020, 15:37
You asked about using the feed of OpenPLi, which is about plugins. Plugins not specifically built for SH4 will not work and OpenPLi does not support SH4, so their plugins will not work on an SH4 box, regardless of image origin.

In your reaction you now talk about SH4 versions and cross compilation, which a different thing. As OSCam is basically a binary you need to compile it using a cross compiler for SH4, otherwise it will not run. Wether or not it will work with my image it not tested by me so you will have to build, test and find out. Please note you also have to configure OSCam to make it work with a particular smartcard, which means that just compiling it and putting it into an image will probably not work.

In the second paragraph you use the word source in a different meaning, namely the source for a complete image instead of the source code for a specific program or package. If you mean by source gits or ready made images I think you will not find many for the Cuberevo-mini, as not that many were sold and the receiver is about ten years old. This means you very likely have to build your own and then the ones already mentioned are about the only ones I know of.

With Neutrino, there are more possibilities, try bpanthers image.

Regards,

Audioniek.

JamesBond
26.11.2020, 00:36
Regarding the OSCAM, yes I know and I have compile it for SH4 enigma2 and this same version is running on other enigma2 images without this problem.
I only said that on your image it doesn't work like opening the channels. It runs well and I can see on the log valid ECM (decoding ok) but I just get a black tv screen on any channel.

For OSCAM I use the official source from Streamboard, authors of OSCAM and it permits on a normal Debian PC cross compiling for any system/CPU.
On OSCAM I can say I'm an expert, no problems with compiling, configurations and so on. ; )

Resuming I just wanted you to know that is not working on your image and I say again the "not working" means it runs without problem but doesn't decode the channels, so there is some sort of problem on the demux, dvbapi or something else.

Regarding Cuberevo enigma2 recent git sources I dig a bit more and found a few that I'm trying now.
Thanks for the information that allowed me to narrow the search and found those ones.

satmania2
30.11.2020, 00:53
Hello
thank you Audioniek (http://www.hdmedia-universe.com/board/member.php?1349-Audioniek) for your effort
the webinterface not working, is it a known problem or just me !?
thank you in advance.

Audioniek
01.12.2020, 17:44
@satmania2: I can confirm that the OpenWebIf does not work at the moment. Will look into it.

Regards,

Audioniek.

clausi_e
06.02.2021, 23:42
Hallo, installing image of 2021 for Spark7162 (Spark Triplex) after opening the system options menu to activate the Wlan driver, the receiver hangs up and reboots. Is this possible to fix this? Thanks ! The same opening plugin systemoptions, bluescreen and reboot

Audioniek
08.02.2021, 18:25
Has been fixed.

Regards,

Audioniek.

clausi_e
08.02.2021, 20:47
I downloaded and installed twice for Spark7162. There was missing system options at all in setup and in plugins. Regards Clausi_e

Audioniek
09.02.2021, 14:47
Sorry, I made a mistake. It should be OK now.

Regards,
Audioniek.

clausi_e
09.02.2021, 19:09
Hallo, Audioniek, I tested last image. Switch between t/c dosn´t work, everytime DVB-t (I rebooted more times). Manual- and automatic cable scan does not work, it appears bluescreen and reboot. When cabletuner will work, I´ll test Wlan-sticks, I have any chipsets. A button "find network" would help to setup Wlan. Thank You for Your work and best regards Clausi_e

clausi_e
14.05.2021, 08:42
I tested actually Image for Spark7162 on Spark Triplex, also self builded, one more time. System options, also plugin, dont work, after changing of any options appears a bluescreen. Is it possible to fix this? Thanks! Clausi

satmania2
16.06.2021, 21:39
Hello Audioniek
grab screen not work neither by interface nor telnet
please can you fix it
(http://www.hdmedia-universe.com/board/member.php?1349-Audioniek)

kyk65
15.11.2021, 08:43
16353HiAudioniek You have not tried to replace evremote2 with lircd so that there is no conflict with vfd

Audioniek
15.11.2021, 21:00
I am not sure what conflict you are referring to. AFAIK all CubeRevo models work fine with the current drivers, so why change something that has been working fine for years?

Regards,

Audioniek.

chaban
22.04.2022, 00:31
Hi...Audioniek (http://www.hdmedia-universe.com/board/member.php?1349-Audioniek)

Atevio 7500 usb version

after puting feed opkg
problem wget : tls sertificat....

mountaineer
27.06.2022, 04:28
thank you for all of your work...i have an optibox raptor..which is an atevio7500.....and I run a very old version of hdmu on it. I keep trying your images and they load until "load 6" is on front display and then always hang and go no further. tried many images and different usb sticks , always same result. any help is appreiated. bootloader 6.00, and am currently using HDMU off of usb stick.


Thank you!

Audioniek
29.06.2022, 12:02
As the boot loader 6.00 cannot run an image off an USB stick, something has been changed on your receiver. In order to be able to reproduce your problem, I would like to know:

What are the current boot arguments?
What exactly have you done to convert the tar.gz file provided and put it on the USB stick?


Regards,

Audioniek.

mountaineer
03.07.2022, 01:52
The usb has 2 partitions: VFAT that has the uimage (which comes from the boot folder) and mini1 (ext2) that has the rest of th eimage on it. The raptor original FW will format the usb stick into the two partitons with the plugin TGZ-USB-Installer plug-in.

HDMU_11809_E2_at7500_209_git_5570_nodebug_mix_USB. tar.gz is what i have running on the raptor withbootloader 6.00.

Rhanks for taking the time to look at this.

sadaghiani
04.07.2022, 10:12
Hello everyone
for test
enigma2 external flash for hs 7429
https://www.mediafire.com/file/mp51u27c5x9agkb/hs7429_enigma2_USB-2-rev1419.zip/file

thank you audioniek for
your great work

Regards
ainouna (https://www.mediafire.com/file/mp51u27c5x9agkb/hs7429_enigma2_USB-2-rev1419.zip/file)
(https://www.mediafire.com/file/mp51u27c5x9agkb/hs7429_enigma2_USB-2-rev1419.zip/file)
(https://www.mediafire.com/file/mp51u27c5x9agkb/hs7429_enigma2_USB-2-rev1419.zip/file)
tnx
how did you solve the boot problem?
Of course, it only works once and it won't boot after restarting

ainouna
04.07.2022, 10:50
Hello ...
if you have boot 7.37
then it works fine
otherwise reflash the 7.37 boot on your receiver

Regards
ainouna

Audioniek
04.07.2022, 13:37
Hello everybody,

It is my gut feeling that something is slowly going wrong here.

@mountaineer: it still is not clear to me what has been changed in the boot arguments on your HS8200. With unchanged boot arguments loader 6.00 cannot start an USB image.

@ainouna: The problem is about an HS8200 not an HS7429. Flashing a 7.37 bootloader into an HS8200 will brick the receiver. Also, the HS7429 uses a different style of USB image which only requires 1 FAT32 partition on the USB stick. An HS8200 requires a USB stick with at least a FAT32 partition for uImage and an ext2/ext3 formatted partition for rest of the image as mountaineer has written. Also see here (http://www.hdmedia-universe.com/board/showthread.php?11200-Audioniek-Images-general-info/page2) (posting #20).

Regards,

Audioniek.

sadaghiani
04.07.2022, 15:30
Hello everybody,

It is my gut feeling that something is slowly going wrong here.

@mountaineer: it still is not clear to me what has been changed in the boot arguments on your HS8200. With unchanged boot arguments loader 6.00 cannot start an USB image.

@ainouna: The problem is about an HS8200 not an HS7429. Flashing a 7.37 bootloader into an HS8200 will brick the receiver. Also, the HS7429 uses a different style of USB image which only requires 1 FAT32 partition on the USB stick. An HS8200 requires a USB stick with at least a FAT32 partition for uImage and an ext2/ext3 formatted partition for rest of the image as mountaineer has written. Also see here (http://www.hdmedia-universe.com/board/showthread.php?11200-Audioniek-Images-general-info/page2) (posting #20).

Regards,

Audioniek.
I meant the same boot from external flash for hs7429

sadaghiani
04.07.2022, 16:23
Hello everybody,

It is my gut feeling that something is slowly going wrong here.

@mountaineer: it still is not clear to me what has been changed in the boot arguments on your HS8200. With unchanged boot arguments loader 6.00 cannot start an USB image.

@ainouna: The problem is about an HS8200 not an HS7429. Flashing a 7.37 bootloader into an HS8200 will brick the receiver. Also, the HS7429 uses a different style of USB image which only requires 1 FAT32 partition on the USB stick. An HS8200 requires a USB stick with at least a FAT32 partition for uImage and an ext2/ext3 formatted partition for rest of the image as mountaineer has written. Also see here (http://www.hdmedia-universe.com/board/showthread.php?11200-Audioniek-Images-general-info/page2) (posting #20).

Regards,

Audioniek.
did you access the bootloader source hs7429?

- - - Aktualisiert - - -


Hello ...
if you have boot 7.37
then it works fine
otherwise reflash the 7.37 boot on your receiver

Regards
ainouna
plz share bootloader hs7429

ainouna
04.07.2022, 17:25
hello
I know it's different
between hs8200 boot 6.00 and hs7429 boot 7.37
I thought it was for a hs7429
a problem starting with uimage
Thank you for the clarification
Mr. Audioniek everything is fine and nothing is constant

Regards
ainouna

sadaghiani
04.07.2022, 17:28
hello
I know it's different
between hs8200 boot 6.00 and hs7429 boot 7.37
I thought it was for a hs7429
a problem starting with uimage
Thank you for the clarification
Mr. Audioniek everything is fine and nothing is constant

Regards
ainouna

plz share bootloader hs7429

ainouna
05.07.2022, 10:24
hello sadaghiani
there are many brand hs7429
what is the brand of your receiver
Octagon SF-1008G+ SE+ Intelligence:270130A0
Forever HD-7474 PVR:271530A0
Forever HD-7878 PVR:271531A0
Openbox S6 PRO Plus:270730A0
XCruiser XDSR 420 HD:270330A0
I can find you the loader
you can even search
for octagon=1008g+se+
UpdateLoader.Octagon.SF1008GplusSEplus.L7.36.ird
for forever hd7474
UpdateLoader.FOREVER.HD7474PVR.L7.37.ird
for forever hd7878
UpdateLoader.FOREVER.HD7878PVR.L7.37.ird
for openbox s6 pro plus
UpdateLoader.OPENBOX.S6 pro plus.L7.37.ird
for xcruiser xdsr 420 hd
BootLoader.XCRUISER.XDSR420HD.L7.37.ird

Regards
ainouna

sadaghiani
05.07.2022, 11:48
hello sadaghiani
there are many brand hs7429
what is the brand of your receiver
Octagon SF-1008G+ SE+ Intelligence:270130A0
Forever HD-7474 PVR:271530A0
Forever HD-7878 PVR:271531A0
Openbox S6 PRO Plus:270730A0
XCruiser XDSR 420 HD:270330A0
I can find you the loader
you can even search
for octagon=1008g+se+
UpdateLoader.Octagon.SF1008GplusSEplus.L7.36.ird
for forever hd7474
UpdateLoader.FOREVER.HD7474PVR.L7.37.ird
for forever hd7878
UpdateLoader.FOREVER.HD7878PVR.L7.37.ird
for openbox s6 pro plus
UpdateLoader.OPENBOX.S6 pro plus.L7.37.ird
for xcruiser xdsr 420 hd
BootLoader.XCRUISER.XDSR420HD.L7.37.ird

Regards
ainouna

tnx
fortis hs7429
270130A0

ainouna
05.07.2022, 12:24
hello again sadaghiani
reseller =270130A0=octagon 1008g+se+
is that the brand of your receiver?...
Regards
ainouna

sadaghiani
05.07.2022, 15:03
hello again sadaghiani
reseller =270130A0=octagon 1008g+se+
is that the brand of your receiver?...
Regards
ainouna

hi
u must know that with any bootloader that has its own id, you can install the rom later with the same id
I am looking for 7.37 bootloader with fortis id
In addition, reseller id change programs do not work on bootloader and are more suitable for image
Of course, bokit plugin is suitable for this
The purpose of changing bootloader id to install image with Fortis id without using change reseller id programs

Audioniek
06.07.2022, 10:57
@sadaghiani "I am looking for 7.37 bootloader with fortis id"

There is no such thing as a Fortis ID as Fortis never sold the HS7429 under its own brand name. If it would exist, its reseller ID would be 270030A0.

What you are wishing for is something that cannot be done without having to hs7429 boot loader source code in order to remove the code that checks for a particular reseller ID. I do not have the source code so I cannot help you there. I also think this wish is not a very wise one, as Fortis built this mechanism in to prevent flashing the wrong software into a receiver, which is sound engineering practice.

For years I have been following this routine and it works for me. In each of the Fortis receivers I have the reseller ID in the boot loader is the original factory one belonging to that particular model. Now in practice I only have to change one reseller ID byte in case I want to flash software for the same basic model (in this case a HS7429) but for another brand name. Normally this approach seldomly needs a reseller changer and if it does it alerts me to pay close attention.

The most convenient approach for you would in my view be installing a 7.37 boot loader with the resellerID at 27XX30A0 with XX corresponding to the reseller brand of your particular receiver. If you need a flash file for that, tell me the value of XX you want and I can post it.

As always: NEVER mess around with boot loaders unless you EXACTLY know what you are doing: it is VERY easy to brick a receiver!

Regards,

Audioniek.

mountaineer
11.07.2022, 02:41
I have loaded the openvision image Atevio 7500 on to the box off of usb and it loads and runs. ( https://images.openvision.dedyn.io/7.6/Vision/SH4/) ...there are issues with that image but it loads and runs...so there is still something going with the image here that it will not load past 6...hope you find a solution as I am sure your image solves a lot of problems the other images have. Please let me know if I can help...thank you for all your work!

Drielander
29.09.2022, 19:07
@Audioniek

Gestern habe ich entdeckt, dass es wieder neue Images für den Topf gibt, weshalb ich heute das Image tf7700_Audioniek_enigma2_gst-epl3_flash_P217_CDK-rev1921.zip (http://www.hdmedia-universe.com/board/attachment.php?attachmentid=16537&d=1654088722) heruntergeladen und geflasht habe. Wie ich schon vor 2 Jahren sagte, ist es halt doch etwas zeitgemäßer/moderner als das HDMU-Image.

Allerdings habe ich wieder/immer noch das Problem mit den Untertiteln für Gehörlose als auch das Problem mit der akustischen Szenen-Beschreibung für Blinde. Ich weiß gar nicht mehr, wo ich damals an welchen Knöpfen gedreht habe - muss ich mich wohl wieder einarbeiten.

Bei einem meiner TF7750 ging das Flashen sehr träge - da stimmt am Topf was nicht mehr. Ein anderer TF7750 ließ den Flash sehr flott wie auch beim HDMU ablaufen. Ich werde jetzt mal damit arbeiten und schauen, wie stabil das Image läuft.

Erstmal besten Dank für Deine Arbeit. :)

Audioniek
01.10.2022, 22:26
Guten Tag Drielander,

Wie früher gesagt, ist die Lösung mit Untertitel und alternative Tonspuren nicht in die Menü-Struktur zu finden. Bei Enigma2 funktioniert das wie folgt.

Der erste Schritt ist das Scannen der Kanäle. Wenn ein Kanal in Sender-liste beim Scannen eingetragen wird es erstmals festgelegt mit die vom Sender angegebenen Vorzugs-Einstellungen. Im allgemeinen sind das Untertitel ausgeschaltet und Normalton. Wird ein Kanal dann später angewählt dann wird es also mit die Standard-Spuren gezeigt.

Die Untertitel-Wahl und Tonspur können jetzt direkt per Fernbedienung geändert werden. In meinen Image sind die tasten die Untertitel-taste (unter die 0) und für das Tonspu die Taste links davon. Man gelangt dann automatisch in das zuständige Auswahlmenü und die zu benutzende Tasten sind meistens die Farbtasten. Gewünschte Wahl machen und das Menü wieder korrekt abschließen. Die Wahl wird jetzt in die Sender-Liste festgelegt, und die Sender soll nächste Mal automatisch mit die festgelegte Wahl gezeigt werden. Um das alles optimal zu wirken zu lassen, Enigma2 richtig abschließen beim ausschalten damit die Sender-Liste gespeichert wird.

Im Praxis ist es also ziemlich einfach: für jedes Kanal muss auf die angegebene Weise die gewünschte Wahl nur einmal gemacht werden, die dann festgehalten wird.

Gruesse,

Audioniek.

Drielander
07.10.2022, 18:02
Hallo Audioniek,

Danke für die Tipps bzgl. Untertitel bzw. Audio-Description, denen ich aber später nachgehen werde.

Im Moment habe ich ein anderes, größeres Problem: bereits beim Start bleibt der Topf oft genug bei START 5x bis START 6x hängen und ich muss den Netzstecker ziehen und wieder zum Boot neu einstecken.
In 50% der Fälle startet der Topf dann bis zu den Programmen durch, aber es gibt kein Bild. Dann muss ich via "Benutzeroberfläche (Enigma) neu starten" neu starten und dann habe ich auch ein Bild zum Rest.

Dass der Ton beim Zappen schon mal wegbleibt und durch Vor/Zurück dann erst kommt, ist ja von früheren Versionen schon bekannt. Das sind noch immer kleine Baustellen.

Das Hängen beim Start ist derzeit sehr lästig, weil die Töpfe keinen Netzschalter haben und man zum Steckerziehen immer nach hinten durchgreifen muss - je nach Regal nicht so bequem.

Grüße
Drillender

Drielander
05.06.2023, 17:29
Hallo Audioniek,

ist die tf7700_Audioniek_enigma2_gst-epl3_flash_P217_CDK-rev1921 die bisher letzte Version oder gibt es etwas Neues? Ich hab zwar immer noch ab und an Probleme mit den Untertiteln bzw. der Bildbeschreibung für Blinde bei zwei, drei Sendern (nicht immer & unterschiedlich), aber mir gefällt die OpenPli-Oberfläche besser als bei den anderen Images.

Grüße

Audioniek
07.06.2023, 15:44
Hallo Drielander,

Das ist in der Tat die letzte. Ich bin beschäftigt mit ein Paar noch nicht unterstützte Modelle und komme damit ziemlich gut voran. Werde mal schauen ob es Sinn hat ein neue Auflage zu bauen. Problem dabei ist dass OpenPli seit einigen Zeit Python 3.X benötigt und das habe ich noch nicht implementiert wegen Zeitmangel. Das unterliegende Enigma2 wird also nicht viel neuer sein.

Grüße,

Audioniek.

Saayacoolu
08.06.2023, 11:53
Very very happy to hear u say trying to get a little time to get us python3 of OpenPli image that all the deck I have and like it very much.we standby to hear from u,sorry may of your heath?

Audioniek
09.06.2023, 13:58
Regarding my health I am am doing much better than half a year ago, thank you for asking.

Regards,

Audioniek.

Drielander
12.06.2023, 11:57
Hallo Drielander,

Das ist in der Tat die letzte. ...... Werde mal schauen ob es Sinn hat ein neue Auflage zu bauen. .......

Audioniek.

Danke für Deine Antwort.
Wäre schön, wenn Du einen Sinn darin siehst - ansonsten geht es halt nicht weiter.

Ich werde jedenfalls bis auf weiteres obiges Image auf meinem Haupt-Topf installiert lassen, weil OpenPli doch viel Bedienkomfort bietet, auch wenn manchmal plötzlich unerwünschte Untertitel und/oder Bildbeschreibungston nerven. Ich habe noch kein System dahimter erkennen können.
Irgendwann schaffe ich es bestimmt, das zu unterbinden. ;)

Alles Gute & bleib gesund.

Gruß
Drielander

sadaghiani
01.08.2023, 19:02
What could this problem be?
On all sh4 devices except official images
When the signal is weak in an HD channel, the device hangs and requires a physical reboot
Do you think it is from the kernel settings?

mihaip
11.09.2023, 15:46
I just tested the image from June 2022 !
I have some problems and I don't know if those were
solved in the mean time ! Can I found the image a more
recent Flash image for HS8200 ?

- network does not work
- DVB-T/DVB-C tuner cannot tune DVB-C is set in DVB-T mode
- scan of Thor 1w found only few TP with signal
- software management cannot install IPK from USB stick ....

Audioniek
16.09.2023, 16:25
Here are some answers to your questions.

The cabled network works on my three test receivers. If you refer to wireless, your observation is correct. This is caused by leaving out the very space consuming wireless drivers, so the first step is to add the wireless driver required for you wireless USB network adapter. After adding that to /lib/modules/, restart the box. Then in enigma2 add the driver in the Wireless menu and again restart the box. than add your wireless credentials in the Wireless menu, and it should work. The reason for all this is that enigma2 occupies almost all of the available flash memory on the HS8200 and even adding one WLAN driver makes things very tight.

I may be mistaken, but as far as I know no DVB-T/C tuner exists for the HS8200. The tuners I know of are either DVB-C or DVB-T (of these two versions were made, the early one without an open source driver). The non-DVB-S tuner in your box is therefore not switchable, appears to be a DVB-T tuner. For that reason there is also no way in the menus to set the tuner mode.

Thor: the image is over one year old, and the file satellite.xml (which holds the transponder list) has the same age. I recommend downloading the latest satellites.xml from the net and installing it in /etc/tuxbox. After that restart the box and try a new scan.

I will test IPK install from USB and try and fix it if it broken.

The june 2022 set of images is currently the last set I built and published. The reason for that is that OpenPLi has switched to Python3 and sigc++ version 3. I have still not found time to implement Python3 on SH4 and am a bit hesitant to do so, as everything gets larger with it and involves a LOT of testing. This in turn will probably cause the receivers with 64Mbyte of flash no longer being capable of running E2 from flash; the HS8200 is one of those receivers. As with sigc++ version 3, it requires a c17 capable compiler which we do not have and I have not been able to build one so far. This means everything must be patched back to sigc++ version 2. This again is a lot of work, and will only work as long as OpenPLi does not start using features of sigc++ not present in version 2.

Regards,

Audioniek.

chaban
29.01.2024, 09:23
Hello ...AUDIONIEK

I TESTED THIS VESION hs8200_Audioniek_enigma2_epl3_flash_P217_CDK-rev1388.zip (http://www.hdmedia-universe.com/board/attachment.php?attachmentid=16659&d=1706455609)

BUT WE HAVE SOME PROBLEME WITH ''OPENWEBIF''

when i inter in menu---plugins (some plugins are not available : extentions/openwebif (long object has no attribute find) systemplugins/networkbrowser('str' object has no attribute 'findall')

NO WORKING IN BROWSER

chaban
29.01.2024, 13:13
Here is log install hs8200_Audioniek_enigma2_epl3_flash_P217_CDK-rev1388.zip


16681


(http://www.hdmedia-universe.com/board/attachment.php?attachmentid=16659&d=1706455609)

Audioniek
29.01.2024, 16:23
Hello chaban,

Thank you for the feedback. Your observations regarding the openwebif and the networkbrowser are correct. They are caused by the fact that these plugins have begun to use Python3 code. I will try and patch them back to Python2 compatible code.

The first boot log looks OK to me, and apart from the plugin-problems, you should have a reasonably well working image.

Regards,

Audioniek.