Got my hands on a shiny new Gigablue UE 4K stb 2 weeks ago, so I thought I should update the thread on my findings.
Basically I am trying to get a Sony PlayTV usb dual dvb-t tuner working on this box - it uses the dib0700 driver pack.
Box came with Teamblue 6.4 installed, so installed the drivers, rebooted, configured them, but a scan returned nothing!
Tried the oldest version of 6.4 as well as the 6.3 versions - nothing scanned.
Decided to install the extra dvb-s2x tuner in the pnp slot, and tried the images again - no change.
So downloaded all the images from openpli, openvix, openatv, teamblue and openhdf I could find taking the oldest/latest from each major version.
For each I did the following:-
fresh flash, no restore, minimum configuration (display + network), downloaded dib0700 drivers, rebooted, configured dvb-t tuners and attempted scan.
All failed to scan and find anything except 2
openvix 5.1.003 20180828
openpli 6.2 20190512
Both found all the channels on the 2 tp/channels we have in Ireland.
Common thing between them, is that both used the drivers from 20180405.
Did a checksum on the driver files in each image, and they matched exactly.
Using the github history on the gigablue-platform-util-gb7252.bb file, I could see the next driver pack was dated 20180914.
This coincided with a change in the bcm sdk
Code:
https://github.com/oe-alliance/oe-alliance-core/commit/e05da7f15ec22231ad6bfbc438f70973fe8c33f0
[GigaBlue | gb7252] update build
* Update drivers to new BCM SDK
* add opengl Support
* add Kodi Support
* add Chrome-WEB Browser
* add Youtube.TV
* add Bluetooth Audio Support (need optional BCM Bluetooth USB Adpater)
* add QT HBBTV Support
* add Support for new Gigablue DVB-S2X Single and Dualtuner with Multistream
* update LCD modes to only support regular modes (no more pip in lcd)
* Info: Quadpip at the moment only supports 1080i and 2160p as video resolution (the fix to support 720p and 1080p is coming later)
* remove support of 480 and 576 video resolution - new BCM SDK dropped that
Had a look at the driver pack, and it's also the first occurrence of the file dvb.ko, so its a different set of files than the working set.
Not sure if it means anything, but for all the images I tried (except 1 openhdf), the tuners were recognised, they could be configured, and using the Signal/Satellite panel, the tuner could be selected, so could the 2 tps/channels, and in each case a signal level was detected and a signal lock was shown.
So I assuming then that the code was able to talk/control the tuner and also get some feedback from it at a tp level.
So a question for any of you guys who have a better understanding how the code, drivers and tuners all hang together - do you think this is a driver issue?
maybe something left out in the conversion to the new sdk etc
It would be cool if I could get it working with the later images - 12 tuners available in 1 box is useful.
TIA
WW