Xbox One DVB-T/T2/C tuner

noggin · 2014-10-21T15:38:04+00:00

Hi all This looks like it could be very good value if Open Source drivers appear for it : http://www.xbox.com/en-GB/xbox-one/accessories/digital-tv-tuner#fb...

Anthony Shephard

You don't have the kernel source to build the drivers, as it isn't a standard kernel, so the raspberrypi-kernel-headers the posts suggest you download won't work
Use the following package to download the appropriate headers
https://github.com/notro/rpi-source/wiki

you can direct where the download will go using -d and need --skip-gcc (as stretch has a later version)

Be warned it downloads a 150Mb compressed file that when expanded has lots of files (65k).

Anthony

Mesut Oezciftci

@Anthony
Thanks it works fine for me

Jan g

I want to install The Tuner on a rpi with newest raspbian Stretch. In this Thread are a lot of Tutorials But which of them works ?

Greetz

Jan g

I try it at Ubuntu 18.04 and Upgrade The Kernel to 4.16.9 and it work out of The Box. But The raspberry doesnt have such a New Kernel Right?

Anthony Shephard

Hi, I suggest using rpi-update to get the latest available kernel and rpi-source (google to download from github) to get the headers for the kernel. Then the steps I suggested in a post a few weeks back should work for you.

Anthony

Jan g

yes i tried it but have the problem:


[ 3.258406] WARNING: You are using an experimental version of the media stack.
As the driver is backported to an older kernel, it doesn't offer
enough quality for its usage in production.
Use it with care.
Latest git patches (needed if you report a bug to linux-media@vger.kernel.org):
8ed8bba70b4355b1ba029b151ade84475dd12991 media: imx274: remove non-indexed pointers from mode_table
4eb7846d3ead1c2f461811e41e63462016e19ae7 media: imx274: rename and reorder register address definitions
f067ddad003b67be8acb7fd739172dcfb4817a2a media: imx274: remove unused data from struct imx274_frmfmt
[ 3.291929] dvb_core: disagrees about version of symbol vb2_vmalloc_memops
[ 3.291955] dvb_core: Unknown symbol vb2_vmalloc_memops (err -22)

Gordon Williams

Hi,

I'm afraid I have the exact same problem as Jan g (with vb2_vmalloc_memops). I used rpi-update which took me up to 4.14.44-v7+ (which didn't handle the dongle automatically), ran rpi-source and built using Anthony's instructions (https://tvheadend.org/d/2255-xbox-one-dvb-t-t2-c-tuner?r=32427#message-32427) but no luck.

I'm now trying to run rpi-source again and it would appear to be pulling in the same kernel sources as last time

The normal Kernel now seems to be at 4.14.34-v7+ - it looks from the threads on here like that might be good enough, without having to update?

Update: Having rebuilt with the normal kernel it boots and despite reporting 'dvb_core: disagrees about version of symbol module_layout' it doesn't seem too unhappy. However I don't have a device in /dev/dvb. Is there anything I can do to track down what the problem is?

thanks!

Anthony Shephard

Hi,
This is the problem with the latest of stuff! Things change and it doesn't work any more!
From my post I tried with 4.14.37 and this works, I tried with 4.14.34 and it kept crashing as soon as the USB tuner was plugged in.

Try 4.14.37 and see if it works?

Anthony

Gordon Williams

Thanks! I actually havesomething happening with 4.14.34 now...


[  396.071569] usb 1-1.4: new high-speed USB device number 6 using dwc_otg
[  396.202417] usb 1-1.4: New USB device found, idVendor=045e, idProduct=02d5
[  396.202432] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  396.202441] usb 1-1.4: Product: Xbox USB Tuner
[  396.202449] usb 1-1.4: Manufacturer: Microsoft Corp.
[  396.202457] usb 1-1.4: SerialNumber: 005974250615
[  396.240679] dvb_core: disagrees about version of symbol module_layout
[  397.281633] Under-voltage detected! (0x00050005)
[  401.441705] Voltage normalised (0x00000000)

I'll get the under-voltage issue sorted, but as I understand it since it hasn't crashed that probably doesn't explain why nothing is happening.

It seems like the module isn't loading. In fact:

$ sudo modprobe tda18250 modprobe: ERROR: could not insert 'tda18250': Exec format error $ sudo modprobe dvb-usb-dib0700 modprobe: ERROR: could not insert 'dvb_usb_dib0700': Exec format error

Does that help? Is it possible that it is being built for 4.14.34 but it's running 4.14.34-v7+ because it's a Pi 3 (if that makes sense?). Although it is definitely looking in /lib/modules/4.14.34-v7+ for the modules...

Anthony Shephard

Hi, I don't know I'm afraid.
I have an RPI3 that is working better than that if you want me to find out versions etc. It does still seem to crash every now and again though.
Anthony

Gordon Williams

Thanks! I think I might wait a bit and try again with a newer kernel - I could be wrong (I'm new to this) but it seems like when the kernel hits 4.17 I won't have to use media_build and can just compile dvb_usb_dib0700 straight out of the normal kernel sources.

Zane Chua

UPDATE:

Bought a T230C which does support the DVB-T2 Lite standard and it is able to pick up the signals.

I guess this tuner doesn't support all DVB-T2 standards. Do be aware.

ORIGINAL:

I have a Raspberry Pi 2 with the 4.14.48-v7+ kernel and I can build the kernel accordingly with the instructions posted by Anthony 2 pages ago.

This is the following output from dmesg.

[ 17.120325] dvb_core: loading out-of-tree module taints kernel. [ 17.125124] WARNING: You are using an experimental version of the media stack. As the driver is backported to an older kernel, it doesn't offer enough quality for its usage in production. Use it with care. Latest git patches (needed if you report a bug to linux-media@vger.kernel.org): f2809d20b9250c675fca8268a0f6274277cca7ff media: omap2: fix compile-testing with FB_OMAP2=m 8d7ab3a0d72d3c98bcd12ff553c5ead0b5e32c31 media: media/radio/Kconfig: add back RADIO_ISA 5983d3bca5282b6785473434894933fa908ef693 media: v4l2-ioctl.c: fix missing unlock in __video_do_ioctl() [ 17.188871] dvb-usb: found a 'Microsoft Xbox One Digital TV Tuner' in cold state, will try to load a firmware [ 17.194139] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw' [ 17.486097] dib0700: firmware started successfully. [ 18.012530] dvb-usb: found a 'Microsoft Xbox One Digital TV Tuner' in warm state. [ 18.012852] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 18.018829] dvbdev: DVB: registering new adapter (Microsoft Xbox One Digital TV Tuner) [ 18.298910] mn88472 3-0018: Panasonic MN88472 successfully identified [ 18.356971] tda18250 3-0060: NXP TDA18250BHN/M successfully identified [ 18.359592] usb 1-1.3: DVB: registering adapter 0 frontend 0 (Panasonic MN88472)... [ 18.360045] dvb-usb: Microsoft Xbox One Digital TV Tuner successfully initialized and connected. [ 18.360595] usbcore: registered new interface driver dvb_usb_dib0700 [ 1280.927177] mn88472 3-0018: downloading firmware from file 'dvb-demod-mn88472-02.fw' [ 1281.111570] usb 1-1.3: DVB: adapter 0 frontend 0 frequency 0 out of range (42000000..870000000)

And this is when i run lsmod so clearly the module is loaded:

root@raspberrypi:~# lsmod Module Size Used by cfg80211 573440 0 rfkill 28672 2 cfg80211 tda18250 20480 1 mn88472 16384 1 dvb_usb_dib0700 122880 0 dib7000m 24576 1 dvb_usb_dib0700 dib0090 36864 1 dvb_usb_dib0700 dib0070 20480 1 dvb_usb_dib0700 dib3000mc 20480 1 dvb_usb_dib0700 dibx000_common 16384 3 dvb_usb_dib0700,dib7000m,dib3000mc dvb_usb 32768 1 dvb_usb_dib0700 dvb_core 106496 2 mn88472,dvb_usb snd_bcm2835 32768 0 snd_pcm 98304 1 snd_bcm2835 snd_timer 32768 1 snd_pcm snd 69632 3 snd_timer,snd_bcm2835,snd_pcm uio_pdrv_genirq 16384 0 uio 20480 1 uio_pdrv_genirq fixed 16384 0 ip_tables 24576 0 x_tables 32768 1 ip_tables ipv6 434176 24

However I can never seem to find or scan any muxes. I'm from Singapore and I think we're using the DVB-T2 1.3.1 Standard (DVB-T2 Lite).

All my scans will result in a "FAIL" from the tvheadend muxes page. I get the following in journalctl:

Jun 10 19:43:55 raspberrypi tvheadend[14191]: mpegts: 554MHz in DVB-T Network - tuning on Panasonic MN88472 #0 : DVB-T #0 Jun 10 19:43:55 raspberrypi tvheadend[14191]: epggrab: 554MHz in DVB-T Network - registering mux for OTA EPG Jun 10 19:43:55 raspberrypi tvheadend[14191]: subscription: 0073: "scan" subscribing to mux "554MHz", weight: 5, adapter: "Panasonic MN88472 #0 : DVB-T #0", network: Jun 10 19:44:00 raspberrypi tvheadend[14191]: mpegts: 554MHz in DVB-T Network - scan no data, failed Jun 10 19:44:00 raspberrypi tvheadend[14191]: subscription: 0073: "scan" unsubscribing Jun 10 19:44:14 raspberrypi tvheadend[14191]: mpegts: 570MHz in DVB-T Network - tuning on Panasonic MN88472 #0 : DVB-T #0 Jun 10 19:44:14 raspberrypi tvheadend[14191]: epggrab: 570MHz in DVB-T Network - registering mux for OTA EPG Jun 10 19:44:14 raspberrypi tvheadend[14191]: subscription: 0074: "scan" subscribing to mux "570MHz", weight: 5, adapter: "Panasonic MN88472 #0 : DVB-T #0", network: Jun 10 19:44:19 raspberrypi tvheadend[14191]: mpegts: 570MHz in DVB-T Network - scan no data, failed

w_scan produces absolutely nothing also. I don't think it has anything to do with my antenna either. But can definitely try another antenna.

A scan with dvbv5-scan produces the following:

channels.conf

[MUXA] DELIVERY_SYSTEM = DVBT2 FREQUENCY = 538000000 BANDWIDTH_HZ = 8000000 [MUXB] DELIVERY_SYSTEM = DVBT2 FREQUENCY = 554000000 BANDWIDTH_HZ = 8000000 [MUXC] DELIVERY_SYSTEM = DVBT2 FREQUENCY = 570000000 BANDWIDTH_HZ = 8000000

output

root@raspberrypi:~# dvbv5-scan -v channels.conf using demux 'dvb0.demux0' Device Panasonic MN88472 (/dev/dvb/adapter0/frontend0) capabilities: CAN_2G_MODULATION CAN_FEC_1_2 CAN_FEC_2_3 CAN_FEC_3_4 CAN_FEC_5_6 CAN_FEC_7_8 CAN_FEC_AUTO CAN_GUARD_INTERVAL_AUTO CAN_HIERARCHY_AUTO CAN_INVERSION_AUTO CAN_MULTISTREAM CAN_MUTE_TS CAN_QAM_16 CAN_QAM_32 CAN_QAM_64 CAN_QAM_128 CAN_QAM_256 CAN_QAM_AUTO CAN_QPSK CAN_TRANSMISSION_MODE_AUTO DVB API Version 5.11, Current v5 delivery system: DVBT2 Supported delivery systems: DVBT [DVBT2] DVBC/ANNEX_A Failed to guess country from the current locale setting. Scanning frequency #1 538000000 FREQUENCY = 538000000 MODULATION = QAM/AUTO BANDWIDTH_HZ = 8000000 INVERSION = AUTO CODE_RATE_HP = AUTO CODE_RATE_LP = AUTO GUARD_INTERVAL = AUTO TRANSMISSION_MODE = AUTO HIERARCHY = AUTO STREAM_ID = 0 DELIVERY_SYSTEM = DVBT2 Viterbi(0x07) Signal= 87.19% C/N= 16.24dB Scanning frequency #2 554000000 FREQUENCY = 554000000 MODULATION = QAM/AUTO BANDWIDTH_HZ = 8000000 INVERSION = AUTO CODE_RATE_HP = AUTO CODE_RATE_LP = AUTO GUARD_INTERVAL = AUTO TRANSMISSION_MODE = AUTO HIERARCHY = AUTO STREAM_ID = 0 DELIVERY_SYSTEM = DVBT2 Viterbi(0x07) Signal= 82.21% C/N= 17.97dB Scanning frequency #3 570000000 FREQUENCY = 570000000 MODULATION = QAM/AUTO BANDWIDTH_HZ = 8000000 INVERSION = AUTO CODE_RATE_HP = AUTO CODE_RATE_LP = AUTO GUARD_INTERVAL = AUTO TRANSMISSION_MODE = AUTO HIERARCHY = AUTO STREAM_ID = 0 DELIVERY_SYSTEM = DVBT2 Viterbi(0x07) Signal= 80.35% C/N= 19.28dB

Does this adapter support this standard?

paul griffiths

Just picked up this tuner from Poundland for £5 in their electrical section
I am really struggling to follow the instructions to successfully recompile for a pi 2 / 3 for either Jessie or stretch, getting the same errors as previously reported in the final make.

Has any one got an pi image they are willing to share to test the device

Thanks
Paul
<<

B W

paul griffiths wrote:
> Just picked up this tuner from Poundland for £5 in their electrical section
> I am really struggling to follow the instructions to successfully recompile for a pi 2 / 3 for either Jessie or stretch, getting the same errors as previously reported in the final make.
> Has any one got an pi image they are willing to share to test the device
>
> Thanks

> Paul

Have you tried LibreElec? It has everything preloaded.
<<

paul griffiths

Thanks I'll give it a go, but was looking for a raspbian image to build a tvheadend tuner

B W

paul griffiths wrote:

> Thanks I'll give it a go, but was looking for a raspbian image to build a tvheadend tuner

I put a step by step somewhere on page 8-9 that will work.
As an alternative you can upgrade raspbian with rpi-update to the 4.14 kernel which has support out of the box. Don't forget you will still need to download the firmware file!

Gordon Williams

> upgrade raspbian with rpi-update to the 4.14 kernel which has support out of the box

That sounds perfect. I don't suppose anyone has any instructions for that? A few posts ago I really struggled to get anything working with 4.14.34 on a Pi 3.

paul griffiths

B W wrote:

> As an alternative you can upgrade raspbian with rpi-update to the 4.14 kernel which has support out of the box. Don't forget you will still need to download the firmware file!

Just tried the rpi-update which took me to 4.14.52-v7+, but still no xbox dvb support -

Zane Chua

paul griffiths wrote:
> B W wrote:
>
> > As an alternative you can upgrade raspbian with rpi-update to the 4.14 kernel which has support out of the box. Don't forget you will still need to download the firmware file!
>

> Just tried the rpi-update which took me to 4.14.52-v7+, but still no xbox dvb support -

Not sure why B W said there'll be support out of the box for the tuner when the patch wasn't even made till 4.16 RC

Anthony Thomas

Has anyone managed to get it working with raspbian Stretch Kernel 4.14.52-v7+?

Just done a fresh install of raspbian on an RPi3 - ran rpi-update, installed the drivers without any issues.

When the tuner is plugged in I get these errors


[  188.047089] usb 1-1.5: new high-speed USB device number 5 using dwc_otg
[  188.177942] usb 1-1.5: New USB device found, idVendor=045e, idProduct=02d5
[  188.177955] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  188.177963] usb 1-1.5: Product: Xbox USB Tuner
[  188.177971] usb 1-1.5: Manufacturer: Microsoft Corp.
[  188.177980] usb 1-1.5: SerialNumber: 004117240615
[  188.210531] dvb_usb: disagrees about version of symbol rc_register_device
[  188.210547] dvb_usb: Unknown symbol rc_register_device (err -22)
[  188.210620] dvb_usb: disagrees about version of symbol rc_free_device
[  188.210627] dvb_usb: Unknown symbol rc_free_device (err -22)
[  188.210684] dvb_usb: disagrees about version of symbol rc_allocate_device
[  188.210690] dvb_usb: Unknown symbol rc_allocate_device (err -22)
[  188.210782] dvb_usb: disagrees about version of symbol rc_unregister_device
[  188.210789] dvb_usb: Unknown symbol rc_unregister_device (err -22)

Tried with a powered USB hub also.

« Previous Page Next Page »