A
Anonymous
Guest
- Thread starter
- #72
Thanks to you all, guys.
Luca
Luca
A
Anonymous
Guest
- Thread starter
- #73
Re: Aver with DVICO
Rastr,
I've noted that the values for the FusionHDTV and the A771 PLLs might be available in the Linux DVB-T source code, according to this posting:
http://216.239.57.104/search?q=cach...5-2004/msg00418.html+a771++tuner++linux&hl=en
more comments here:
http://216.239.57.104/search?q=cach...6-2004/msg00183.html+a771++tuner++linux&hl=en
Hopefully this is of some use and might re-kindle your interest in getting BDA working for the A771?
Best of luck, unfortunately my coding experience isn't of much use in this instance.
Gizmomelb
RaStr said:
Rastr,
I've noted that the values for the FusionHDTV and the A771 PLLs might be available in the Linux DVB-T source code, according to this posting:
http://216.239.57.104/search?q=cach...5-2004/msg00418.html+a771++tuner++linux&hl=en
more comments here:
http://216.239.57.104/search?q=cach...6-2004/msg00183.html+a771++tuner++linux&hl=en
Hopefully this is of some use and might re-kindle your interest in getting BDA working for the A771?
Best of luck, unfortunately my coding experience isn't of much use in this instance.
Gizmomelb
A
Anonymous
Guest
- Thread starter
- #74
Whoa!
Some searching of the Linux DVB-T forums/wiki has revealed some potentially useful info - the Avermedia A771 and the Technisat Airstar 2 share a lot of common elements.
Since there is a SDK available for the Technisat Airstar 2, then possibly those drivers can have support for the BT878 added so we can get the A771 supported under Media Portal (it's a big ask, but it might happen):
Avermedia DVB-T 771
(mt352/samsung tdtc9251dh0(??))
features: fullts, AVin
card driver: dvb-bt8xx
interface: PCI
PCI device id: 109e:036e
PCI subsystem id: 1461:0771
Bridge: Brooktree bt878
frontend 1:
tin box: samsung tdtc9251dh0
frontend driver: mt352
demodulator location: tin box
demodulator: mt352 @0x0f
PLL: ?? @0x61
Technisat Airstar2
(mt352/Samsung tdtc9251dh0(??))
features: fullts
card driver: skystar2
interface: PCI
PCI device id: 13d0:2103 (rev 02)
PCI subsystem id: 13d0:2103
frontend 1:
tin box: samsung tdtc9251dh0
frontend driver: mt352
demodulator location: tin box
demodulator: ST MT352 @0x0f
PLL: ?? @0x61
Notes: Based on B2C2 FlexCop Chipset. The PCI address of this is identical to the skystar2!!! Have to probe frontend to identify.
some info on the B2C2 FlexCop chipset as used on the Technicsat Airstar2 can be found here:
http://www.linuxtv.org/wiki/index.php/B2C2_FlexCop
and here:
http://www.b2c2.com/docs/flexcop.pdf
Technisat website::
www.technisat.com or www.technisat.de
SDK can be found at:
http://www.technisat.hu/download/skystar2-sdk404.zip
or:
http://www.technisat.com/?site=service/download.php&produktID=1281&reload
Some searching of the Linux DVB-T forums/wiki has revealed some potentially useful info - the Avermedia A771 and the Technisat Airstar 2 share a lot of common elements.
Since there is a SDK available for the Technisat Airstar 2, then possibly those drivers can have support for the BT878 added so we can get the A771 supported under Media Portal (it's a big ask, but it might happen):
Avermedia DVB-T 771
(mt352/samsung tdtc9251dh0(??))
features: fullts, AVin
card driver: dvb-bt8xx
interface: PCI
PCI device id: 109e:036e
PCI subsystem id: 1461:0771
Bridge: Brooktree bt878
frontend 1:
tin box: samsung tdtc9251dh0
frontend driver: mt352
demodulator location: tin box
demodulator: mt352 @0x0f
PLL: ?? @0x61
Technisat Airstar2
(mt352/Samsung tdtc9251dh0(??))
features: fullts
card driver: skystar2
interface: PCI
PCI device id: 13d0:2103 (rev 02)
PCI subsystem id: 13d0:2103
frontend 1:
tin box: samsung tdtc9251dh0
frontend driver: mt352
demodulator location: tin box
demodulator: ST MT352 @0x0f
PLL: ?? @0x61
Notes: Based on B2C2 FlexCop Chipset. The PCI address of this is identical to the skystar2!!! Have to probe frontend to identify.
some info on the B2C2 FlexCop chipset as used on the Technicsat Airstar2 can be found here:
http://www.linuxtv.org/wiki/index.php/B2C2_FlexCop
and here:
http://www.b2c2.com/docs/flexcop.pdf
Technisat website::
www.technisat.com or www.technisat.de
SDK can be found at:
http://www.technisat.hu/download/skystar2-sdk404.zip
or:
http://www.technisat.com/?site=service/download.php&produktID=1281&reload
A
Anonymous
Guest
- Thread starter
- #75
or if anyone has the VisionPlus BDA drivers by Sprectrum, or the source to the official Twinhan BDA drivers then interfacing the BT878A on the Avermedia to the Samsung/Zarlink should be reasonably straight forward (in theory).
New Zealand
R
RaStr
Guest
- Thread starter
- #77
AVER T771 & DVICO drivers - probbably real final results
Hi all, I have finally patched the DVICO's drivers to fully match the programming of mt352 done by original drivers from Aver. While driver from DVICO seems to be pretty straight-forward and it's behavior reflects the suggested mt352 datasheets's steps, the work done by an original driver from Aver is a big mess with a lot of redundant I2C commands and operations, so analyzing it is a bit complicated. I have made my patched zulutune to send all most important config values to mt352, but it was unable to lock to a channel either. There are some commands missing compared to a steps performed by an Aver driver and originally I thought there are not critical. While my sniffing hardware currently doesn't support sending I2C commands from the monitoring application I can't check my sequence step by step and I am not sure where is the problem, one possible reason could be some kind of missetup of general purpose pins of BT878A PCI chip on the card (there could be something like enable pin for a tin box, etc.), but I don't expect much this would be the case, another option is that the tuner is much slower then the tuner on DVICO's card, so the driver check it's status before it actually locks on the channel, I can't test this before I will get my sniffer fully operational, so I could send the read-status command manually and the last possibility is that some more config data must be sent to a mt352 before it can lock on the channel, I can check this with my saved Aver's driver session, but it would be extremely difficult to patch the DVICO driver further, so without the source code is almost impossible to make necessary changes in it anyhow. So as I have already stated, until we will get the driver sources, we can't do much about it. Maybe we can ask for a current Aver's driver sources, as this could be very helpful to me too !
Hi all, I have finally patched the DVICO's drivers to fully match the programming of mt352 done by original drivers from Aver. While driver from DVICO seems to be pretty straight-forward and it's behavior reflects the suggested mt352 datasheets's steps, the work done by an original driver from Aver is a big mess with a lot of redundant I2C commands and operations, so analyzing it is a bit complicated. I have made my patched zulutune to send all most important config values to mt352, but it was unable to lock to a channel either. There are some commands missing compared to a steps performed by an Aver driver and originally I thought there are not critical. While my sniffing hardware currently doesn't support sending I2C commands from the monitoring application I can't check my sequence step by step and I am not sure where is the problem, one possible reason could be some kind of missetup of general purpose pins of BT878A PCI chip on the card (there could be something like enable pin for a tin box, etc.), but I don't expect much this would be the case, another option is that the tuner is much slower then the tuner on DVICO's card, so the driver check it's status before it actually locks on the channel, I can't test this before I will get my sniffer fully operational, so I could send the read-status command manually and the last possibility is that some more config data must be sent to a mt352 before it can lock on the channel, I can check this with my saved Aver's driver session, but it would be extremely difficult to patch the DVICO driver further, so without the source code is almost impossible to make necessary changes in it anyhow. So as I have already stated, until we will get the driver sources, we can't do much about it. Maybe we can ask for a current Aver's driver sources, as this could be very helpful to me too !
A
Anonymous
Guest
- Thread starter
- #79
hey RaStr, DMAN,
First off I'm really impressed with the work you guys are putting in, though I feel RaStr won't be able to progress much further as the tuners on the Fusion and the Avermedia cards are totally different (Thomson vs. Samsung). Unless you're correctly initialising the tuner etc. by programming the MT352 you won't get a thing. There is publically available source for the Samsung tuner as part of the Technisat Airstar2 SDK on their web site, which might be of use if you're actively programming the MT352 (useful to find out which settings/controls need to be initialised etc.) and hacking that into the DVico driver (ie: change the 'initialise Thomson tuner' to 'initialise Samsung tuner', if they have different ways of being initialised)..
I'm the gizmomelb running the public Avermedia beta on the Aussie DBA forums (www.dba.org.au) and I'm in direct contact with some of the Avermedia higher management and the lead programmers for the A771/A800/A16A hardware. I *almost* got the source code for the A771 hardware from them after negotiating for another programmer, but the NDA for the BT878A hardware from Conexant forbid any more reverse engineering, so the programmer decided to continue working on his software the way he had been previously (disassembling the Aver drivers and filters and finding/fixing the errors in the A771 driver himself). Avermedia cannot release source code for the A771 hardware as Conexant will not release public source code for the BT878A PCI bridge. There is a data sheet with some pin info on the BT878A from the Conexant site here:
http://www.conexant.com/products/entry.jsp?id=272
I've asked the programmer who has already disassembled the Aver drivers for some info etc. but he is not currently involved in developing the commercial software he was working on. I am hopeful that the information he learnt will one day appear anonymously on the net, as he once remarked to me that he felt sure BDA driver development could be done without the Avermedia SDK - given the 40 or so lines of demux interface code he had reverse engineered (I'm guessing as a WDM to BDA wrapper, much like Spectrum's BDA code for the VisionPlus DVB-T card).
First off I'm really impressed with the work you guys are putting in, though I feel RaStr won't be able to progress much further as the tuners on the Fusion and the Avermedia cards are totally different (Thomson vs. Samsung). Unless you're correctly initialising the tuner etc. by programming the MT352 you won't get a thing. There is publically available source for the Samsung tuner as part of the Technisat Airstar2 SDK on their web site, which might be of use if you're actively programming the MT352 (useful to find out which settings/controls need to be initialised etc.) and hacking that into the DVico driver (ie: change the 'initialise Thomson tuner' to 'initialise Samsung tuner', if they have different ways of being initialised)..
I'm the gizmomelb running the public Avermedia beta on the Aussie DBA forums (www.dba.org.au) and I'm in direct contact with some of the Avermedia higher management and the lead programmers for the A771/A800/A16A hardware. I *almost* got the source code for the A771 hardware from them after negotiating for another programmer, but the NDA for the BT878A hardware from Conexant forbid any more reverse engineering, so the programmer decided to continue working on his software the way he had been previously (disassembling the Aver drivers and filters and finding/fixing the errors in the A771 driver himself). Avermedia cannot release source code for the A771 hardware as Conexant will not release public source code for the BT878A PCI bridge. There is a data sheet with some pin info on the BT878A from the Conexant site here:
http://www.conexant.com/products/entry.jsp?id=272
I've asked the programmer who has already disassembled the Aver drivers for some info etc. but he is not currently involved in developing the commercial software he was working on. I am hopeful that the information he learnt will one day appear anonymously on the net, as he once remarked to me that he felt sure BDA driver development could be done without the Avermedia SDK - given the 40 or so lines of demux interface code he had reverse engineered (I'm guessing as a WDM to BDA wrapper, much like Spectrum's BDA code for the VisionPlus DVB-T card).
R
RaStr
Guest
- Thread starter
- #80
Re: Gizmomelb
Thank you for your advices Gizmomelb, but I have had no intention to search for a right command sequence for an Aver card, it would be pointless if I don't have the driver source to patch and it seems to be impossible to make the DVICO driver operational just by patching the binary. I am getting ready for my 3 week holiday trip to NZ next month, so I am a bit too busy now, maybe I will make some further "experiments" when I will return, if there still won't be BDA driver for A771 or far much better application from Aver then now. I have been already reading the docs from Connexant, the problem is that there is almost no word about TS Stream capture in it, they say something about further document update, which seems to be unavailable to the public ! But my primary goal was to make the tuning operational and this code should rely on bdatune.sys and PLL+mt352 solely, so maybe I can learn something from the mentioned SDK for a Technisat Airstar2 but suddenly I could not find it anywhere !
Thank you for your advices Gizmomelb, but I have had no intention to search for a right command sequence for an Aver card, it would be pointless if I don't have the driver source to patch and it seems to be impossible to make the DVICO driver operational just by patching the binary. I am getting ready for my 3 week holiday trip to NZ next month, so I am a bit too busy now, maybe I will make some further "experiments" when I will return, if there still won't be BDA driver for A771 or far much better application from Aver then now. I have been already reading the docs from Connexant, the problem is that there is almost no word about TS Stream capture in it, they say something about further document update, which seems to be unavailable to the public ! But my primary goal was to make the tuning operational and this code should rely on bdatune.sys and PLL+mt352 solely, so maybe I can learn something from the mentioned SDK for a Technisat Airstar2 but suddenly I could not find it anywhere !