SAA7164 firmware for Asus MyCinema

Hi,

I found at the site: http://www.linuxtv.org/wiki/index.php/ATSC_PCIe_Cards that if I have a TV-tuner card which is currently unsupported, you may help me how I can make workable this device.

I have an Asus MyCinema EHD3-100/NAQ/FM/AV/MCE RC dual TV-Tuner card with SAA7164 chipset.

My OS version is:

~# lsb_release -a
No LSB modules are available.

Distributor ID: Ubuntu
Description:    Ubuntu 14.04.1 LTS
Release:        14.04
Codename:       trusty

grep for saa7164:

~# dmesg | grep saa

[   12.564005] saa7164 driver loaded
[   12.564142] saa7164[0]: Your board isn't known (yet) to the driver.
[   12.564142] saa7164[0]: Try to pick one of the existing card configs via
[   12.564142] saa7164[0]: card=<n> insmod option.  Updating to the latest
[   12.564142] saa7164[0]: version might help as well.
[   12.564248] saa7164[0]: Here are valid choicesfor  the card=<n> insmod option:
[   12.564277] saa7164[0]:    card=0 -> Unknown
[   12.564295] saa7164[0]:    card=1 -> Generic Rev2
[   12.564315] saa7164[0]:    card=2 -> Generic Rev3
[   12.564334] saa7164[0]:    card=3 -> Hauppauge WinTV-HVR2250
[   12.564357] saa7164[0]:    card=4 -> Hauppauge WinTV-HVR2200
[   12.564380] saa7164[0]:    card=5 -> Hauppauge WinTV-HVR2200
[   12.564403] saa7164[0]:    card=6 -> Hauppauge WinTV-HVR2200
[   12.564427] saa7164[0]:    card=7 -> Hauppauge WinTV-HVR2250
[   12.564450] saa7164[0]:    card=8 -> Hauppauge WinTV-HVR2250
[   12.564473] saa7164[0]:    card=9 -> Hauppauge WinTV-HVR2200
[   12.564496] saa7164[0]:    card=10 -> Hauppauge WinTV-HVR2200
[   12.565287] CORE saa7164[0]: subsystem: 1043:48cb, board: Unknown [card=0,autodetected]
[   12.565291] saa7164[0]/0: found at 0000:03:00.0, rev: 129, irq: 16, latency: 0, mmio: 0xfe400000
[   12.565302] saa7164_initdev() Unsupported board detected, registering without firmware

My TV-Tuner detected parameters:

~# lspci -vvv
...
03:00.0 Multimedia controller: Philips Semiconductors SAA7164 (rev 81)
Subsystem: ASUSTeK Computer Inc. Device 48cb
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 16
Region 0: Memory at fe400000 (64-bit, non-prefetchable) [size=4M] Region 2: Memory at fe000000 (64-bit, non-prefetchable) [size=4M]
Capabilities: [40] MSI: Enable- Count=1/16 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
Capabilities: [50] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s
<256ns, L1 <1us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq-
AuxPwr+ TransPend-

                LnkCap: Port #1, Speed 2.5GT/s, Width x2, ASPM L0s L1, 

Exit Latency L0s <4us, L1 <64us
ClockPM- Surprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 128 bytes Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk-
DLActive- BWMgmt- ABWMgmt-
Capabilities: [74] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [7c] Vendor Specific Information: Len=84 <?>
Capabilities: [100 v1] Vendor Specific Information: ID=0000
Rev=0 Len=060 <?>
Capabilities: [160 v1] Virtual Channel
Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
Arb: Fixed- WRR32- WRR64- WRR128-
Ctrl: ArbSelect=Fixed
Status: InProgress-
VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb: Fixed- WRR32- WRR64- WRR128- TWRR128-
WRR256-
Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01
Status: NegoPending- InProgress-
VC1: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb: Fixed- WRR32- WRR64- WRR128- TWRR128-
WRR256-
Ctrl: Enable- ID=0 ArbSelect=Fixed TC/VC=00
Status: NegoPending- InProgress-
Kernel driver in use: saa7164
...

Currently I use KDE4 (installed from the original Ubuntu 14.04 distribution).

If you need any other parameters to detect my device, please write me some instructions how can I get it from my system. I am software developer so if you have any instructions how can I turn on the TV on my computer with this TV-Tuner, please contact me.

Thank you in advance.

Regards,
Zsolt

Did we talk about this in IRC a couple of days ago?

If not, you will need to find out which demodulator and tuner are used on that card. You can find those by looking at the physical card. Read the text on the bigger ICs and try to put them in the google to find out the components used. The tuner might be under metal shielding, in which case it might be a bit more tricky to find out.

Looking at the files in the Windows driver package might give you some hints as well.

Cheers,
-olli

Hi Olli,

Sorry, unfortunately was not me on IRC.

So as you wrote, I followed your instructions, and I collect as information as I can from the board. I made a small site quickly with some photos, you found it here:
http://myoop.hu/tuner.html

While I took the photos I found that my card is Asus MyCinema EHD2-100/PT/FM/AV/RC.

Can you help me how should I continue my work with this tuner?

Thank you very much in advance.

Best regards,
Zsolt

2014.11.20. 20:51 keltezéssel, Olli Salonen írta:

Hi Zsolt,

In order to support a card in Linux in general, there needs to be a driver for the PCIe bridge, the demodulator and the tuner. Then these building blocks must be put together in a way that makes sense.

You've already identified the PCIe bridge (NXP SAA7164), the demodulator (TDA 10046) and the tuner (Taifun 6034T aka Infineon TUA6034). Now here comes the bad news - even if the PCIe bridge and the demod are supported by existing drivers, the TUA6034 is not supported by currently. You would need to write or get someone to write a driver for the TUA6034. In order for this to be possible you'd need to get the specifications from the manufacturer (often not possible, but worth trying) or reverse-engineer the Windows driver (often quite tricky, especially since taking a trace from a PCIe device can be a lot of work).

Might I suggest that you add also a wiki page in the LinuxTV wiki if you're anyway looking at this? Basically you can document the same things you've very well documented on your website there, but please use the template that the other devices on the site are more or less using. http://www.linuxtv.org/wiki/index.php/ASUS is a good starting point. Even if the conclusion is that the card will not work your research might save someone else time in the future.

Cheers,
-olli

Hi Olli,

Thank you very much for your answer.

I found a data-sheet for TUA6034 at http://pdf.datasheetcatalog.com/datasheet2/4/084ailjhz4xq79otdj14u5laz3py.pdf (found at http://www.datasheetcatalog.com/datasheets_pdf/T/U/A/_/TUA_6034-T.shtml)

At the 46th page of the PDF file I found some programming instructions.
It may be a good start for write driver for this tuner?
I will try to find programming instructions to how can I write driver, but if you (or anybody) have any good start-up instruction for me I am very glade for it.

Regards,
Zsolt

2014.11.23. 8:54 keltezéssel, Olli Salonen írta: