TechniSat AirStar-HD5000-USB: Difference between revisions

From LinuxTVWiki
Jump to navigation Jump to search
m (oops, PLX driver does exist!)
 
(3 intermediate revisions by 2 users not shown)
Line 13: Line 13:
===Components Used===
===Components Used===
* LG H061F (NIM):
* LG H061F (NIM):
** ''Infineon TUA6034 (tuner)''
** ''[[Infineon TUA6034]] (tuner)''
** ''Philips TDA9887 (analog IF demodulator)''
** ''[[Philips TDA9887]] (analog IF demodulator)''
** ''LG DT3303 (digital demodulator)''
** ''[[LG DT3303]] (digital demodulator)''
* [[B2C2 Inc.]] [[B2C2 FlexCop|FlexCop IIB]] ([[PCI interface chipsets|PCI interface chipset]])
* [[B2C2 Inc.]] [[B2C2 FlexCop|FlexCop IIB]] ([[PCI interface chipsets|PCI interface chipset]])
* PLX NET2282 (PCI to USB bridge) [http://www.plxtech.com/about/news/pr/?y=2005&rel=0228] ... (also see
* PLX NET2282 (PCI to USB bridge) [http://www.plxtech.com/about/news/pr/?y=2005&rel=0228]


An examination of the device's internals reveals that the PCB contains:<br>
An examination of the device's internals reveals that the PCB contains:<br>
Line 35: Line 35:
* PLX NET2282-A833PC (U9)
* PLX NET2282-A833PC (U9)
* ATMEL 542 25640AN (U11)
* ATMEL 542 25640AN (U11)
* C77331 65T C12E (U13)
* C77331 65T C12E (U13)


===Identification===
===Identification===
Line 41: Line 41:


==Making it Work==
==Making it Work==
Given that its components are near identical to its [[TechniSat AirStar-HD5000-PCI|AirStar-HD5000-PCI]] counterpart, adding support for this device should probably not be too difficult. Driver support for the PLX USB bridge does exist [http://www.mail-archive.com/linux-usb-devel@lists.sourceforge.net/msg42872.html], so adding support for this device ''should be'' a matter of adding the glue code that ties all the components together.
With the exception of the additional PLX USB bridge, the device's components are otherwise near identical, if not the same, to its [[TechniSat AirStar-HD5000-PCI|AirStar-HD5000-PCI]] counterpart. Given that driver support for the PLX USB bridge does exist [http://www.mail-archive.com/linux-usb-devel@lists.sourceforge.net/msg42872.html], adding support for this device ''should probably not be too difficult''' (famous last words), and is likely just a matter of adding the glue code that ties all the components together.


===Firmware===
===Firmware===
Line 53: Line 53:
==External Links==
==External Links==
*[http://www.bbti.us/products_airstar_hd5000_usb.htm BBTI product page]
*[http://www.bbti.us/products_airstar_hd5000_usb.htm BBTI product page]
[[Category:ATSC USB Devices]]

Latest revision as of 20:44, 29 May 2009

An ATSC USB device by TechniSat, but marketed in the U.S. by the associate company BBTI.

It is currently not supported under Linux.

Overview/Features

This device features a USB 2.0 interface.

Origin of the Device's Name

TechniSat never listed this device on their own website's product pages. Rather, one finds information about this ATSC device strictly on the BBTI website (TechniSat's source for North American sales and distribution).

Previous ATSC products manufactured by TechniSat, but marketed by BBTI, retained the naming scheme given to them by their original reference device designer, B2C2; as opposed to being marketed by way of TechinSat's "*Stars" product lineup nomenclature. With the HD5000 products, BBTI has evidently now adopted the TechniSat convention into part of the device names.

Components Used

An examination of the device's internals reveals that the PCB contains:
Top side

  • LG TDVS-H064F demodulator (P1 or U2)
  • Atmel PLD: ATF750C (U8)
  • clock: CTS09-CB3 45M00000 (U23)
  • Flexcop-IIB MM5HG-000 (U1)
  • MKAL 5298 (U22)
  • 62AE N12A (U7) (looks like regulator)
  • ?? (U21)
  • ?? (U20)
  • There's an unpopulated jumper that appears to lead to U11; not checked.

Back side

  • ISSI IS61LV256-15TL (U3)
  • ATMEL616 24C08AN (U4)
  • PLX NET2282-A833PC (U9)
  • ATMEL 542 25640AN (U11)
  • C77331 65T C12E (U13)

Identification

Output of lsusb -v reveals that it has a subsystem ID of 13d0:2282.

Making it Work

With the exception of the additional PLX USB bridge, the device's components are otherwise near identical, if not the same, to its AirStar-HD5000-PCI counterpart. Given that driver support for the PLX USB bridge does exist [2], adding support for this device should probably not be too difficult' (famous last words), and is likely just a matter of adding the glue code that ties all the components together.

Firmware

Drivers

Sample Kernel Outuput

Remote Controller Support

External Links