Reply to thread

Message

<blockquote data-quote="RaStr" data-source="post: 10708"> I have seen this before, but was no much helpfull, as I don't understand the values mentioned there, but at least I have choosen the closest much to AV 771, which is DVBT Lite I don't know what the number 0x61 means, but I believe it is the device ID or something like that, as the DVICO uses Thomson7579 and Aver uses TUA6034, suddenly I have not datasheet of Thomson 7579 for a compare ! For those of you who care, I have made some pictures of my card, with removed and opened tin-box (as the PLL is located on the backside) here: <a href="http://www.althan.cz/A771" target="_blank">http://www.althan.cz/A771</a>Anyhow, yesterday I have had a bad luck, my main PC with Aver card suddenly died after my water-cooling pump failed. But I was able to make a capture of&nbsp; I2C communication during ChannelScan with DVICO driver, but currently the registry setting for that driver were not 100% correct as I have played with them the day before. What seems to be evident is that the DVICO driver is using hard-coded I2C address for PLL chip equal to hC0, which is the main reason why the driver cannot tune ! The calculated frequency divisor seems to be correct and also some other setup data for a MT352 ODFM decoder are loaded with datasheet's defaults. The other main problem (despite of I2C address of PLL chip) is with datamode of MT352, which is configured by the driver for a serial communication, while my card seems to like parallel communication instead. I have intended to capture I2C setup sequence from Aver drivers too, but my PC failed too soon&nbsp; <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite16" alt=":cry:" title="Crying&nbsp; &nbsp; :cry:" loading="lazy" data-shortname=":cry:" /> ! As it will take maybe a month to make it operational, I am not sure, when I could continue, maybe I will have to &quot;steal&quot; some PC from my job for that&nbsp;&nbsp; :roll:&nbsp; ! Then I could try to send a proper I2C commands to the MT352 using my external I2C sniffer and to tune it &quot;manualy&quot; this way, to check the data path and the rest of the driver. Of course I will try to patch the driver in the mean time !So wish me a luck and goodbye for today !</blockquote>

[QUOTE="RaStr, post: 10708"] [b] I have seen this before, but was no much helpfull, as I don't understand the values mentioned there, but at least I have choosen the closest much to AV 771, which is DVBT Lite [/b] [b] I don't know what the number 0x61 means, but I believe it is the device ID or something like that, as the DVICO uses Thomson7579 and Aver uses TUA6034, suddenly I have not datasheet of Thomson 7579 for a compare ![/b] For those of you who care, I have made some pictures of my card, with removed and opened tin-box (as the PLL is located on the backside) here: [url]http://www.althan.cz/A771[/url] Anyhow, yesterday I have had a bad luck, my main PC with Aver card suddenly died after my water-cooling pump failed. But I was able to make a capture of I2C communication during ChannelScan with DVICO driver, but currently the registry setting for that driver were not 100% correct as I have played with them the day before. What seems to be evident is that the DVICO driver is using hard-coded I2C address for PLL chip equal to hC0, which is the main reason why the driver cannot tune ! The calculated frequency divisor seems to be correct and also some other setup data for a MT352 ODFM decoder are loaded with datasheet's defaults. The other main problem (despite of I2C address of PLL chip) is with datamode of MT352, which is configured by the driver for a serial communication, while my card seems to like parallel communication instead. I have intended to capture I2C setup sequence from Aver drivers too, but my PC failed too soon :cry: ! As it will take maybe a month to make it operational, I am not sure, when I could continue, maybe I will have to "steal" some PC from my job for that :roll: ! Then I could try to send a proper I2C commands to the MT352 using my external I2C sniffer and to tune it "manualy" this way, to check the data path and the rest of the driver. Of course I will try to patch the driver in the mean time ! So wish me a luck and goodbye for today ! [/QUOTE]

Verification