DVB via USB: Difference between revisions

From LinuxTVWiki
Jump to navigation Jump to search
 
(333 intermediate revisions by 84 users not shown)
Line 1: Line 1:
For information about supported USB devices, see the appropriate device category: <BR>
== Introduction ==
* [[ATSC USB Devices]]
Here is a market overview of available DVB/ATSC USB devices sorted by its required LinuxTV driver (if supported - and yes - most of them are).
* [[DVB-C USB Devices]]
* [[DVB-S USB Devices]]
* [[DVB-S2 USB Devices]]
* [[DVB-T USB Devices]]
* [[DVB-T2 USB Devices]]
<BR>


__TOC__
Please help to keep this list up-to-date so that it is useful for everyone!
==Introduction==
'''For all DVB USB devices you will need to load (if not compiled into the kernel):'''
* i2c-core
* crc32
* firmware_class
* dvb-core.ko
* dvb-pll.ko
and maybe others too. If the loading fails for any particular module you'll get a "unknown symbol" message. Then have a look at dmesg to find out, which symbols (functions) are missing. After you've found out which module was absent, please come back here and add it to the list/device-entry.


The ''Type'' field specifies the USB standard(s) supported by the device.
'''For all devices shown below you need to load (if not compiled into the kernel):'''
- i2c-core
- crc32
- firmware_class
- dvb-core.ko
- dvb-pll.ko
and maybe others too. If the loading fails for any particular module you'll get a "unkown symbol"-message. Then take a look at dmesg to find out, which symbols (functions) are missing. After you've found out which module was absent, please come back here and add it to the list/device-entry.


; USB1.1
'''Firmware:''' Most of the USB devices need a firmware to run. Some of the firmware files can be downloaded here: [http://www.linuxtv.org/downloads/firmware/].
: The device supports USB 1.1 only, and will work at 1.1 speeds when attached to a USB 2.0 port.
; USB2.0
: The device supports USB 2.0 only, and will not work when attached to a USB 1.1-only port. Such devices are normally capable of delivering the complete [[TS|Transport Stream]] to the software demuxer.
; USB2.0, USB1.1
: The device supports USB 1.1 and USB 2.0, and will work at any speed supported by 1.1 or 2.0. When running in USB 2.0 mode, such devices can deliver the complete [[TS|Transport Stream]] (unless specified otherwise).


== Firmware ==
'''Legend:''' the field type specifies the real USB-standard of the device
- '''USB1.1''': the device can be run on the USB1.1 and on the USB2.0 bus but only with USB1.1-speed.
- '''USB2.0''': the device can only be connected to a real USB2.0 port and runs with USB2.0-speed.
(delivering the complete [[TS|Transport Stream]] to the software demuxer.)
- '''USB2.0/USB1.1''': the device is actually USB2.0, but can also be driven on a USB1.1 port. (if not
mentioned elsewhere, these boxes can deliver the complete [[TS|Transport Stream]] when running in USB2.0 mode)


Most of the USB devices need firmware to run. Some of the firmware files can be downloaded from [http://www.linuxtv.org/downloads/firmware/ here].
== DVB-T ==


You need to copy the firmware to the correct place on your system. This will normally be /lib/firmware or a folder below it. Here is an example:
=== AVerMedia AverTV A800 ===


- $ cd /lib/firmware
All devices below are fully supported by the LinuxTV driver. The following drivers are needed for these devices:
- $ ls
- dib3000-common.ko
- 2.6.15-23-amd64-xeon
- dib3000mc.ko
- $ cd 2.6.15-23-amd64-xeon
- dvb-usb.ko
- dvb-usb-dibusb-common.ko
- $ sudo cp ~/dvb-usb-umt-010-02.fw .
- dvb-usb-a800.ko


Now, you need to unplug your USB device. Plug it in again, and then take a look at dmesg.
These [[frontend|frontend(s)]]/[[demodulator|demodulator(s)]] can be found in various revisions of this device:
- $ dmesg
- [[DiB3000P|DiBcom 3000P]]
- < ...... lines cut for clarity ..... >
- usb 5-2: USB disconnect, address 3
- usb 5-2: new high speed USB device using ehci_hcd and address 8
- dvb-usb: found a 'Hanftek UMT-010 DVB-T USB2.0' in cold state, will try to load a firmware
- dvb-usb: downloading firmware from file 'dvb-usb-umt-010-02.fw' to the 'Cypress FX2'
- dvb-usb: Hanftek UMT-010 DVB-T USB2.0 successfully initialized and connected.
- usb 5-2: USB disconnect, address 8
- dvb-usb: generic DVB-USB module successfully deinitialized and disconnected.


In this case, I have success, because the firmware was loaded.
'''Comment:''' Devices listed below are clones of a DVB-T USB2.0 reference design made by [[DiBcom]].


Remember that on some system the firmware is loaded by udev, so if for some reason the firmware is not loaded you may check that
{| width="900" border=1 cellpadding=2 cellspacing=0 valign="top"
udev is acutally running.
|- bgcolor=#efefef valign="top"
To check you could for example issue the command:
! '''device/model'''
- $ ps -e | grep udev
! '''type'''
! '''firmware name'''
! '''comments/quirks'''
! '''URL/pictures'''
|- align="left"
! AVerMedia AVerTV DVB-T USB 2.0
! USB2.0/USB1.1
! dvb-usb-avertv-a800-02.fw
! Remote control handling is different to the one used in the other DiBusb clones.
! [http://www.avermedia.com/cgi-bin/products_digitvtuner_dvbtusb2.asp?show=2]
|-
|}


If the output is empty, then you have to restart the udev daemon. For example in a Debian based system you may try with:
=== DiBcom USB1.1 DVB-T devices (based on the [[DiB3000M-B]]) ===
- $ sudo /etc/init.d/udev restart


then try again, removing and inserting the module again with modprobe.
All devices below are fully supported by the LinuxTV driver. The following drivers are needed for these devices:
- dib3000-common.ko
- dib3000mb.ko
- dvb-usb.ko
- dvb-usb-dibusb-common.ko
- dvb-usb-dibusb-mb.ko


== Additional Technical Information ==
These [[frontend|frontend(s)]]/[[demodulator|demodulator(s)]] can be found in various revisions of this device:
- [[DiB3000M-B|DiBcom 3000M-B]]


This section starts describing devices which hit the market beginning of spring 2004. It does not cover TTUSB-based devices.
'''Comment:''' Most of these device listed below are (sometimes slightly modified) clones of a DVB-T USB1.1 reference design made by [[DiBcom]].


=== Host Controlled DVB USB Devices ===
{| width="900" border=1 cellpadding=2 cellspacing=0 valign="top"
|- bgcolor=#efefef valign="top"
! '''device/model'''
! '''type'''
! '''firmware name'''
! '''comments/quirks'''
! '''URL/pictures'''
|- align="left"
! TwinhanDTV USB-Ter (VP7041)
! USB1.1
! dvb-usb-dibusb-5.0.0.11.fw
! first DVB-T USB box on the market with dib3000mb built-in
! [http://www.twinhan.com/product_terrestrial_3.asp]
|- align="left"
! TwinhanDTV Magic Box (VP7041e)
! USB1.1
! dvb-usb-dibusb-5.0.0.11.fw
! -
! [http://www.twinhan.com/product_terrestrial_4.asp]
|- align="left"
! HAMA DVB-T USB1.1 device
! USB1.1
! dvb-usb-dibusb-5.0.0.11.fw
! -
! [http://www.hama.de/bilder/00049/abb/00049021abb.jpg]
|- align="left"
! CTS Portable (Chinese Television System)
! USB1.1
! dvb-usb-dibusb-5.0.0.11.fw
! -
! [http://www.2cts.tv/ctsportable/]
|- align="left"
! DigitalRise DVB-T USB 1.1 Ter
! USB1.1
! dvb-usb-dibusb-5.0.0.11.fw
! -
! [http://www.digitalrise.biz/products/dtv-t7045/]
|- align="left"
! KWorld V-Stream XPERT DTV DVB-T USB
! USB1.1
! dvb-usb-dibusb-5.0.0.11.fw
! -
! [http://www.kworld.com.tw/en/product/DVBT-USB/DVBT-USB.html]
|- align="left"
! JetWay DTV DVB-T USB
! USB1.1
! dvb-usb-dibusb-5.0.0.11.fw
! -
! [http://www.jetway.com.tw/evisn/product/lcd-tv/DVT-USB/dtv-usb.htm]
|- align="left"
! ADSTech Instant TV DVB-T USB
! USB1.1
! dvb-usb-dibusb-5.0.0.11.fw
! -
! [http://www.adstech.com/products/PTV-333/intro/PTV-333_intro.asp?pid=PTV-333]
|- align="left"
! Ultima Electronic/Artec T1 USB TVBOX
! USB1.1
! dvb-usb-dibusb-5.0.0.11.fw or <br />dvb-usb-dibusb-an2235-01.fw
! There are several clones of this device: some have the AN2235 USB controller instead of the AN2135. Some using a Panasonic tuner instead of the default Thomson Cable tuner. Most of the Boxes have standard Cypress USB IDs which makes it very hard to identify them. A HowTo for this devices can be found [[Artec T1 USB TV Box|here]].
! [http://www.ultima-elec.nl/]
|- align="left"
! Compro Videomate DVB-U2000
! USB1.1
! dvb-usb-dibusb-5.0.0.11.fw
! -
! [http://www.comprousa.com/products/vmu2000.htm]
|- align="left"
! Grandtec DVB-T USB1.1
! USB1.1
! dvb-usb-dibusb-5.0.0.11.fw
! -
! [http://www.grand.com.tw/en/product_form.asp?lwk_series=54&lwk_product=h-030&lwk_page=]
|- align="left"
! AVerMedia AverTV DVBT USB
! USB1.1
! dvb-usb-dibusb-5.0.0.11.fw
! -
! [http://www.avermedia.com/cgi-bin/products_digitvtuner_dvbtusb.asp?show=2]
|- align="left"
! ADSTech Instant TV DVB-T USB2.0 (dark blue)
! USB2.0/USB1.1
! dvb-usb-adstech-usb2-02.fw
! The only known USB2.0 device with a [[DiB3000M-B]] demodulator.
! [http://www.adstech.com/products/PTV-333/intro/PTV-333_intro.asp?pid=PTV-333]
|-
|}


When first AC-Adapter-free USB devices (with the capability of receiving DVB Signals) hit the market, every vendor was using the generic USB-device-controller from Cypress (FX1 (AN2135/AN2235), FX2) as an interface between the DVB-hardware and the host.
=== DiBcom USB2.0 DVB-T devices (based on the [[DiB3000M-C/P]]) ===


As those controllers are very generic, one has to create (and download) an (small or not so small) embedded software to those controller to give vendor-specific and the wanted functionality. After downloading the so-called firmware vendors used the reboot-feature of the controller to re-enumerate with new USB Vendor/Product-IDs and a new USB-layout. On the host this looks like a normal disconnect and connect of an USB device.
All devices below are fully supported by the LinuxTV driver. The following drivers are needed for these devices:
- dib3000-common.ko
- dib3000mc.ko
- dvb-usb.ko
- dvb-usb-dibusb-common.ko
- dvb-usb-dibusb-mc.ko


Because the memory for storing the firmware was limited, vendors decided not to put any DVB-demodulator and RF-tuner specific code into the firmware, but only to implement interface functionality. At that time, the common way to control other components was [[I²C Protocol|I²C]]. The other necessary feature was data-streaming. With such a firmware, every functionality is done from the host - mainly the driving of the demodulator and the tuner.
These [[frontend|frontend(s)]]/[[demodulator|demodulator(s)]] can be found in various revisions of this device:
- [[DiB3000M-C|DiBcom 3000M-C]]
- [[DiB3000P|DiBcom 3000P]]


Host-controlled devices are the ones based on DiBcom (dibusb, dib0700), Nebula (DigiTV), Hanftek and others. (see below)
'''Comment:''' Devices listed below are clones of a DVB-T USB2.0 reference design made by [[DiBcom]].


=== Firmware Controlled DVB USB Devices===
{| width="900" border=1 cellpadding=2 cellspacing=0 valign="top"
|- bgcolor=#efefef valign="top"
! '''device/model'''
! '''type'''
! '''firmware name'''
! '''comments/quirks'''
! '''URL/pictures'''
|- align="left"
! Artec T1 USB2.0
! USB2.0/USB1.1
! dvb-usb-dibusb-6.0.0.8.fw
! not confirmed yet.
! [http://www.ultima-elec.nl/]
|-
|}


Another approach was coming later: When it started, that putting more memory on a board/into an IC with almost no increase of the [[BOM]]. Vendors started to put the demodulator and tuner-driver into the firmware. This was simplifying the host-part dramatically, because if you have a new hardware, you just need to modify the (platform-independent) firmware part and, as long as the firmware-interface is not changing, the host-driver stays the same.
=== HanfTek UMT-010 ===


Firmware-controlled devices: Twinhan VP7045/VP7021, Terratec Cinergy T2, Wideview and others.
All devices below are fully supported by the LinuxTV driver. The following drivers are needed for these devices:
- mt352.ko
- dvb-usb.ko
- dvb-usb-dibusb-common.ko
- dvb-usb-umt-010.ko


To be continued ...
These [[frontend|frontend(s)]]/[[demodulator|demodulator(s)]] can be found in various revisions of this device:
- [[MT352|Zarlink MT352]]


'''Comment:''' The USB protocol which is used by this device is equal to the one used in DiBcom USB2.0 reference design. Thanks to Hanftek who especially wrote a firmware for easy Linux-Support.


== lsusb -t ==
{| width="900" border=1 cellpadding=2 cellspacing=0 valign="top"
|- bgcolor=#efefef valign="top"
! '''device/model'''
! '''type'''
! '''firmware name'''
! '''comments/quirks'''
! '''URL/pictures'''
|- align="left"
! Hanftek UMT-010
! USB2.0
! dvb-usb-umt-010-02.fw
! Stick-sized. Different colors (blue, gray, red).
! [http://www.hanftek.com/]
|-
|}


=== Hauppauge WinTV-NOVA-T usb2 ===
=== Wrong ===
With this setup you will have bandwidth problems with no appropriate warning whatsoever on any log file. Except that video will look horrible.
<pre>
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/8p, 12M <-- USB1.1, slow, don't us
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/8p, 480M <-- one bus
|__ Port 2: Dev 2, If 0, Class=vend., Driver=dvb_usb_ttusb2, 480M <-- 1st DVB device, shares bandwidth
|__ Port 4: Dev 2, If 0, Class=vend., Driver=dvb_usb_ttusb2, 480M <-- 2nd DVB device, shares bandwidth
</pre>


=== OK ===
All devices below are fully supported by the LinuxTV driver. The following drivers are needed for these devices:
You can solve the above situation by adding a PCI-Express to USB3.0 card:
- dib3000-common.ko
<pre>
- dib3000mc.ko
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
- dvb-usb.ko
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M <-- one bus
- dvb-usb-dibusb-common.ko
|__ Port 2: Dev 2, If 0, Class=vend., Driver=dvb_usb_ttusb2, 480M <-- one DVB device
- dvb-usb-nova-t-usb2.ko
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/8p, 12M <-- USB1.1, slow, don't use
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/8p, 480M <-- one bus
|__ Port 4: Dev 2, If 0, Class=vend., Driver=dvb_usb_ttusb2, 480M <-- one DVB device
</pre>


'''''Rule''': One device per bus''
These [[frontend|frontend(s)]]/[[demodulator|demodulator(s)]] can be found in various revisions of this device:
- [[DiB3000P|DiBcom 3000P]]


'''Comment:''' Devices listed below are clones of a DVB-T USB2.0 reference design made by [[DiBcom]].


[[Category:Hardware| ]]
{| width="900" border=1 cellpadding=2 cellspacing=0 valign="top"
|- bgcolor=#efefef valign="top"
! '''device/model'''
! '''type'''
! '''firmware name'''
! '''comments/quirks'''
! '''URL/pictures'''
|- align="left"
! Hauppauge WinTV NOVA-T USB2
! USB2.0/USB1.1
! dvb-usb-nova-t-usb2-01.fw
! It has a MAC address.
! [http://www.hauppauge.de/pages/products/data_nova-t-usb2.html]
|-
|}

=== TerraTec Cinergy T² ===

All devices below are fully supported by the LinuxTV driver. The following drivers are needed for these devices:
- cinergyT2.ko

These [[frontend|frontend(s)]]/[[demodulator|demodulator(s)]] can be found in various revisions of this device:
- [[MT352|Zarlink MT352]]

'''Comment:''' The programming of the MT352 is hidden behind the USB protocol defined within the firmware.

{| width="900" border=1 cellpadding=2 cellspacing=0 valign="top"
|- bgcolor=#efefef valign="top"
! '''device/model'''
! '''type'''
! '''firmware name'''
! '''comments/quirks'''
! '''URL/pictures'''
|- align="left"
! [[TerraTec]] [[Cinergy_T2|Cinergy T²]]
! USB2.0
! -
! -
! [http://tvde.terratec.net/modules.php?op=modload&name=News&file=article&sid=238]
|-
|}

=== Twinhan DVB-T USB2.0 ===

All devices below are fully supported by the LinuxTV driver. The following drivers are needed for these devices:
- dvb-usb.ko
- dvb-usb-vp7045.ko

These [[frontend|frontend(s)]]/[[demodulator|demodulator(s)]] can be found in various revisions of this device:
- [[MT352|Zarlink MT352]]

'''Comment:''' The programming of the MT352 is hidden behind the USB protocol defined within the firmware.

{| width="900" border=1 cellpadding=2 cellspacing=0 valign="top"
|- bgcolor=#efefef valign="top"
! '''device/model'''
! '''type'''
! '''firmware name'''
! '''comments/quirks'''
! '''URL/pictures'''
|- align="left"
! TwinhanDTV Alpha
! USB2.0
! dvb-usb-vp7045-01.fw
! Stick-sized.
! [http://www.twinhan.com/product_terrestrial_8.asp]
|- align="left"
! TwinhanDTV MagicBoxII
! USB2.0
! dvb-usb-vp7045-01.fw
! -
! [http://www.twinhan.com/product_terrestrial_7.asp]
|- align="left"
! DigitalNow TinyUSB 2 DVB-t
! USB2.0
! dvb-usb-vp7045-01.fw
! Stick-sized.
! [http://www.digitalnow.com.au/DigitalNow%20tinyUSB2%20Specifications.html]
|- align="left"
! DigitalRise DVB-T USB 2.0 Ter Beetle
! USB2.0
! dvb-usb-vp7045-01.fw
! -
! [http://www.digitalrise.biz/products/dtv-t7045/]
|-
|}

=== Yakumo/Hama/Typhoon/Yuan ===

All devices below are fully supported by the LinuxTV driver. The following drivers are needed for these devices:
- dvb-usb.ko
- dvb-usb-dtt200u.ko

These [[frontend|frontend(s)]]/[[demodulator|demodulator(s)]] can be found in various revisions of this device:
- [[MT352|Zarlink MT352]]

'''Comment:''' The programming of the MT352 is hidden behind the USB protocol defined within the firmware. These boxes can only deliver part of the [[TS|Transport Stream]] (using a hardware PID filter) which is not known how to be deactivated. (The driver was completely [[reverse-engineering|reverse-engineered]] without the help of its real vendor (Who is the _real_ vendor, actually))

{| width="900" border=1 cellpadding=2 cellspacing=0 valign="top"
|- bgcolor=#efefef valign="top"
! '''device/model'''
! '''type'''
! '''firmware name'''
! '''comments/quirks'''
! '''URL/pictures'''
|- align="left"
! Yakumo DVB-T mobile USB
! USB2.0/USB1.1
! dvb-usb-dtt200u-01.fw
! aka DTT200U
! [http://www.yakumo.de/produkte/index.php?pid=1&ag=DVB-T]
|- align="left"
! Yuan DVB2GO UB300
! USB2.0/USB1.1
! dvb-usb-dtt200u-01.fw
! -
! [http://www.yuan.com.tw/en/products/vdo_ub300.html]
|- align="left"
! Hama DVB-T Box
! USB2.0/USB1.1
! dvb-usb-dtt200u-01.fw
! -
! [http://www.hama.de/portal/articleId*114663/action*2563]
|- align="left"
! TYPHOON USB2.0 DVB-T BOX
! USB2.0/USB1.1
! dvb-usb-dtt200u-01.fw
! -
! [http://www.typhoon.de/de/art.php?p=739&c=]
|-
|}

== DVB-C ==

== DVB-S ==

== ATSC ==

== Multi-purpose DVB/ATSC ==

=== [[Technotrend]] Budget USB1.1 (DVB-S/T/C) ===

All devices below are fully supported by the LinuxTV driver. The following drivers are needed for these devices:
- stv0299.ko
- cx22700.ko
- tda1004x.ko
- tda8083.ko
- dvb-ttusb-budget.ko

These [[frontend|frontend(s)]]/[[demodulator|demodulator(s)]] can be found in various revisions of this device:
- [[STV0299|ST STV0299]]
- [[Conexant]] [[CX22700|CX22700]]
- [[Philips]] [[TDA10046]]
- [[Philips]] [[TDA8083]]

'''Comment:'''

{| width="900" border=1 cellpadding=2 cellspacing=0 valign="top"
|- bgcolor=#efefef valign="top"
! '''device/model'''
! '''type'''
! '''firmware name'''
! '''comments/quirks'''
! '''URL/pictures'''
|- align="left"
! Hauppauge WinTV-NOVA-S usb
! USB1.1
! -
! -
! [http://www.hauppauge.de/pages/products/data_nova-s-usb.html]
|- align="left"
! Hauppauge [[WinTV-NOVA-T_USB|WinTV-NOVA-T usb]]
! USB1.1
! dvb-fe-tda10046.fw
! -
! [http://www.hauppauge.de/pages/products/data_nova-t-usb.html]
|- align="left"
! Satelco USB-Box DVB-S/T/C
! USB1.1
! dvb-fe-tda10046.fw
! DVB-C clone is not supported.
! [http://www.satelco.de/htm/shop/boxen/index.htm]
|- align="left"
! Technotrend TT-PCline USB family DVB-S/T/C
! USB1.1
! dvb-fe-tda10046.fw
! DVB-C clone is not supported.
! [http://www.technotrend.de/english/download/download.html]
|-
|}

=== [[Technotrend]] DEC Budget USB1.1 (DVB-S/T) ===

All devices below are fully supported by the LinuxTV driver. The following drivers are needed for these devices:
- ttusbdecfe.ko
- ttusb_dec.ko

These [[frontend|frontend(s)]]/[[demodulator|demodulator(s)]] can be found in various revisions of this device:
- DEC-specific

'''Comment:''' The DECs are Set-Top-Boxes equipped with a USB port and can be used without a PC. The TV-Out can't be used for PC-Output.

{| width="900" border=1 cellpadding=2 cellspacing=0 valign="top"
|- bgcolor=#efefef valign="top"
! '''device/model'''
! '''type'''
! '''firmware name'''
! '''comments/quirks'''
! '''URL/pictures'''
|- align="left"
! Hauppauge DEC3000-S (DVB-S)
! USB1.1
! dvb-ttusb-dec-3000s.fw
! -
! [http://www.hauppauge.de/pages/products/data_dec3000s.html]
|- align="left"
! Hauppauge DEC2000-T (DVB-T)
! USB1.1
! dvb-ttusb-dec-2000t.fw
! -
! [http://www.hauppauge.de/pages/products/data_dec2000t.html]
|- align="left"
! Hauppauge DEC1100-T (DVB-T)
! USB1.1
! -
! not supported (?)
! [http://www.hauppauge.de/pages/products/data_dec1100t.html]
|- align="left"
! Hauppauge [[DEC2540-T_USB|DEC2540-T]] (DVB-T)
! USB1.1
! -
! Similar to DEC2000-T but with Conax(?) decrypt card slot. Decryption is not supported under GNU/Linux.
! -
|-
|}

=== [[Technisat]]/[[B2C2]] Sky/Air/Cable2PC USB ([[Flexcop]]-based) (DVB-S/T/C / ATSC) ===

All devices below are fully supported by the LinuxTV driver. The following drivers are needed for these devices:
- stv0299.ko
- stv0297.ko
- mt352.ko
- mt312.ko
- nxt2002.ko
- bcm3510.ko
- b2c2-flexcop.ko
- b2c2-flexcop-usb.ko

These [[frontend|frontend(s)]]/[[demodulator|demodulator(s)]] can be found in various revisions of this device:
- [[STV0299|ST STV0299]]
- [[STV0297|ST STV0297]]
- [[MT312]]
- [[MT352|Zarlink MT352]]
- [[NXT2002|NextWave 2002]]
- [[BCM3510|Broadcom BCM3510]]

'''Comment:'''

{| width="900" border=1 cellpadding=2 cellspacing=0 valign="top"
|- bgcolor=#efefef valign="top"
! '''device/model'''
! '''type'''
! '''firmware name'''
! '''comments/quirks'''
! '''URL/pictures'''
|- align="left"
! Technisat/B2C2 SkyStar USB
! USB1.1
! -
! -
! [http://www.technisat.de/?site=produkte/produkteview.php&kid=1,29&pid=1476]
|- align="left"
! Technisat/B2C2 AirStar USB DVB-T
! USB1.1
! -
! -
! [http://www.technisat.de/de/produkte/produkteview.php?kid=1,29&pid=1477]
|- align="left"
! Technisat/B2C2 AirStar USB ATSC
! USB1.1
! dvb-fe-bcm3510-01.fw
! -
! [http://www.bbti.us/products_air2pc_atsc_usb.htm]
|- align="left"
! Technisat/B2C2 CableStar USB
! USB1.1
! -
! Discontinued
! -
|}

== Hybrid/Misc ==

== Work-In-Progress ==

=== DViCO FusionHDTV USB - DVB-T ===

This driver is still Work-In-Progress. The following drivers are needed for these devices:
- dvb-usb.ko
- dvb-usb-bluebird.ko

These [[frontend|frontend(s)]]/[[demodulator|demodulator(s)]] can be found in various revisions of this device:
- [[MT352|Zarlink MT352]]

'''Comment:''' The preliminary version of the driver is not public yet, because it very unstable/incomplete. If you want to help develop the driver, please consult the [[linux-dvb-ml|linux-dvb Mailing list]].

{| width="900" border=1 cellpadding=2 cellspacing=0 valign="top"
|- bgcolor=#efefef valign="top"
! '''device/model'''
! '''type'''
! '''firmware name'''
! '''comments/quirks'''
! '''URL/pictures'''
|- align="left"
! DViCO FusionHDTV USB
! USB2.0
! There is a working MAC driver written by John Dalgliesh. It can be used to write the Linux-Driver.
! dvb-usb-bluebird-01.fw
! [http://www.fusionhdtv.co.kr/eng/Products/DVBTUSB.aspx]
|-
|}

=== Nebula DigiTV USB version - DVB-T ===

This driver is still Work-In-Progress. The following drivers are needed for these devices:
- dvb-usb.ko
- dvb-usb-digitv.ko

These [[frontend|frontend(s)]]/[[demodulator|demodulator(s)]] can be found in various revisions of this device:
- [[MT352|Zarlink MT352]]
- [[NXT6000|NextWave 6000]]

'''Comment:''' A preliminary version of the driver can be found in [[dvb-kernel|dvb-kernel CVS]] already. If you want to help develop the driver, please consult the [[linux-dvb-ml|linux-dvb Mailing list]].

{| width="900" border=1 cellpadding=2 cellspacing=0 valign="top"
|- bgcolor=#efefef valign="top"
! '''device/model'''
! '''type'''
! '''firmware name'''
! '''comments/quirks'''
! '''URL/pictures'''
|- align="left"
! Nebula DigiTV USB
! USB2.0
! There is a SDK for download on the Nebula WebSite, which was used to improve the driver's quality. Was the first USB2.0 box on the Market (late 2003/early 2004).
! dvb-usb-digitv-01.fw
! [http://www.nebula-electronics.com/information/info.asp?Code=0003]
|-
|}

=== Pinnacle PCTV 200e USB - DVB-T ===

This driver is pre-Work-In-Progress. The following drivers are needed for these devices:
- dvb-usb.ko
- dvb-usb-pctv-200e.ko (probably)

These [[frontend|frontend(s)]]/[[demodulator|demodulator(s)]] can be found in various revisions of this device:
- [[MT352|Zarlink MT352]]

'''Comment:''' There driver is not written yet. To gather information about the box is the primary task now. If you want to help develop the driver, please consult the [[linux-dvb-ml|linux-dvb Mailing list]].

What we know:
- MT352-frontend (i2c addr: 0x1f)
- Microtune MT2060 tuner (which is the actual problem, because Microtune has a strict information restriction regarding this product) (i2c addr: 0x60)
- (must) have a pid filter
- no firmware needed
- implements a I2CoverUSB bus

{| width="900" border=1 cellpadding=2 cellspacing=0 valign="top"
|- bgcolor=#efefef valign="top"
! '''device/model'''
! '''type'''
! '''firmware name'''
! '''comments/quirks'''
! '''URL/pictures'''
|- align="left"
! Pinnacle PCTV 200e USB - DVB-T
! USB2.0/USB1.1
! - (firmware is not needed)
! Pinnacle claim to be USB2.0 and USB1.1 compatible, so there has to be a PID-filter.
! [http://www.pinnaclesys.com/ProductPage_n.asp?Product_ID=2657&Langue_ID=4]
|-
|}

=== TwinhanDTV StarBox - DVB-S ===

This driver is still Work-In-Progress. The following drivers are needed for these devices:
- dvb-usb.ko
- dvb-usb-vp702x.ko

These [[frontend|frontend(s)]]/[[demodulator|demodulator(s)]] can be found in various revisions of this device:
- [[DST]]

'''Comment:''' The preliminary version of the driver is not public yet, because it very unstable. If you want to help the development, please consult the [[linux-dvb-ml|linux-dvb Mailing list]]. The frontend-part of the DST-driver could be rewritten to be used by the USB driver. Currently it is hard-wired to the PCI-cards.

{| width="900" border=1 cellpadding=2 cellspacing=0 valign="top"
|- bgcolor=#efefef valign="top"
! '''device/model'''
! '''type'''
! '''firmware name'''
! '''comments/quirks'''
! '''URL/pictures'''
|- align="left"
! TwinhanDTV StarBox
! USB2.0/USB1.1
! -
! dvb-usb-vp702x-01.fw
! [http://www.twinhan.com/product_satellite_5.asp]
|- align="left"
! DigitalRise DVB-S USB Sat Starbox
! USB2.0/USB1.1
! -
! dvb-usb-vp702x-01.fw
! [http://www.digitalrise.biz/products/dtv-s7021/]
|- align="left"
! TYPHOON DVB-S USB 2.0 BOX
! USB2.0/USB1.1
! -
! dvb-usb-vp702x-01.fw
! [http://www.typhoon.de/de/art.php?p=822&c=]
|-
|}

== Unspecified/Unkown devices ==

=== Typhoon DVB-T USB DRIVE ===

This stick could be a clone of the [[Twinhan]] Alpha or of the [[DiBcom]] Pen reference design. If you own the device and you want to help the development, please consult the [[linux-dvb-ml|linux-dvb Mailing list].[http://www.typhoon.de/de/art.php?p=826&c=]



[[Category:DVB-T|!USB devices DVB-T]]
[[Category:Hardware|!USB devices DVB-T]]

Latest revision as of 10:13, 3 December 2012

For information about supported USB devices, see the appropriate device category:


Introduction

For all DVB USB devices you will need to load (if not compiled into the kernel):

  • i2c-core
  • crc32
  • firmware_class
  • dvb-core.ko
  • dvb-pll.ko

and maybe others too. If the loading fails for any particular module you'll get a "unknown symbol" message. Then have a look at dmesg to find out, which symbols (functions) are missing. After you've found out which module was absent, please come back here and add it to the list/device-entry.

The Type field specifies the USB standard(s) supported by the device.

USB1.1
The device supports USB 1.1 only, and will work at 1.1 speeds when attached to a USB 2.0 port.
USB2.0
The device supports USB 2.0 only, and will not work when attached to a USB 1.1-only port. Such devices are normally capable of delivering the complete Transport Stream to the software demuxer.
USB2.0, USB1.1
The device supports USB 1.1 and USB 2.0, and will work at any speed supported by 1.1 or 2.0. When running in USB 2.0 mode, such devices can deliver the complete Transport Stream (unless specified otherwise).

Firmware

Most of the USB devices need firmware to run. Some of the firmware files can be downloaded from here.

You need to copy the firmware to the correct place on your system. This will normally be /lib/firmware or a folder below it. Here is an example:

- $ cd /lib/firmware
- $ ls
- 2.6.15-23-amd64-xeon
- $ cd 2.6.15-23-amd64-xeon
- $ sudo cp ~/dvb-usb-umt-010-02.fw .

Now, you need to unplug your USB device. Plug it in again, and then take a look at dmesg.

- $ dmesg
- < ...... lines cut for clarity ..... >
- usb 5-2: USB disconnect, address 3
- usb 5-2: new high speed USB device using ehci_hcd and address 8
- dvb-usb: found a 'Hanftek UMT-010 DVB-T USB2.0' in cold state, will try to load a firmware
- dvb-usb: downloading firmware from file 'dvb-usb-umt-010-02.fw' to the 'Cypress FX2'
- dvb-usb: Hanftek UMT-010 DVB-T USB2.0 successfully initialized and connected.
- usb 5-2: USB disconnect, address 8
- dvb-usb: generic DVB-USB module successfully deinitialized and disconnected.

In this case, I have success, because the firmware was loaded.

Remember that on some system the firmware is loaded by udev, so if for some reason the firmware is not loaded you may check that udev is acutally running. To check you could for example issue the command:

- $ ps -e | grep udev

If the output is empty, then you have to restart the udev daemon. For example in a Debian based system you may try with:

- $ sudo /etc/init.d/udev restart

then try again, removing and inserting the module again with modprobe.

Additional Technical Information

This section starts describing devices which hit the market beginning of spring 2004. It does not cover TTUSB-based devices.

Host Controlled DVB USB Devices

When first AC-Adapter-free USB devices (with the capability of receiving DVB Signals) hit the market, every vendor was using the generic USB-device-controller from Cypress (FX1 (AN2135/AN2235), FX2) as an interface between the DVB-hardware and the host.

As those controllers are very generic, one has to create (and download) an (small or not so small) embedded software to those controller to give vendor-specific and the wanted functionality. After downloading the so-called firmware vendors used the reboot-feature of the controller to re-enumerate with new USB Vendor/Product-IDs and a new USB-layout. On the host this looks like a normal disconnect and connect of an USB device.

Because the memory for storing the firmware was limited, vendors decided not to put any DVB-demodulator and RF-tuner specific code into the firmware, but only to implement interface functionality. At that time, the common way to control other components was I²C. The other necessary feature was data-streaming. With such a firmware, every functionality is done from the host - mainly the driving of the demodulator and the tuner.

Host-controlled devices are the ones based on DiBcom (dibusb, dib0700), Nebula (DigiTV), Hanftek and others. (see below)

Firmware Controlled DVB USB Devices

Another approach was coming later: When it started, that putting more memory on a board/into an IC with almost no increase of the BOM. Vendors started to put the demodulator and tuner-driver into the firmware. This was simplifying the host-part dramatically, because if you have a new hardware, you just need to modify the (platform-independent) firmware part and, as long as the firmware-interface is not changing, the host-driver stays the same.

Firmware-controlled devices: Twinhan VP7045/VP7021, Terratec Cinergy T2, Wideview and others.

To be continued ...


lsusb -t

Wrong

With this setup you will have bandwidth problems with no appropriate warning whatsoever on any log file. Except that video will look horrible.

/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/8p, 12M     <-- USB1.1,  slow, don't us
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/8p, 480M    <-- one bus
    |__ Port 2: Dev 2, If 0, Class=vend., Driver=dvb_usb_ttusb2, 480M <--  1st DVB device, shares bandwidth
    |__ Port 4: Dev 2, If 0, Class=vend., Driver=dvb_usb_ttusb2, 480M <--  2nd DVB device, shares bandwidth

OK

You can solve the above situation by adding a PCI-Express to USB3.0 card:

/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M    <-- one bus
    |__ Port 2: Dev 2, If 0, Class=vend., Driver=dvb_usb_ttusb2, 480M <--  one DVB device
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/8p, 12M     <-- USB1.1,  slow, don't use
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/8p, 480M    <-- one bus
    |__ Port 4: Dev 2, If 0, Class=vend., Driver=dvb_usb_ttusb2, 480M <--  one DVB device

Rule: One device per bus