home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
General Support
AverTV DVB-T 771
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="RaStr" data-source="post: 10846"><p><strong>ZULU driver - success !</strong></p><p></p><p>So finally I have found where the C0 is stored, but it took another 4 hours from my regular sleep time ! The major problem was, that the tuning is not served by the zulutune.sys, after a couple of tries and some hours of work I have find out that I could even delete the .sys file from system32\drivers folder and the behavior of my setup will be still the same (i.e. all I2C command passed in the same order). So I have focused on the zulubda.sys driver, as it uses registry value named "TunerModel" which is actually the parameter deciding which tunnig algorithm will be used ! Then after some more hours I have found some part of its code, suspicious of defining the PLL I2C address, I have changed this to give it a try, but the driver then failed to load ! After another hour of research and tries I have discovered that the driver binary is protected by CRC, so I have had to change at least two bytes of code instead one only, after one more try I have discovered that they have to be word aligned (as the CRC is at least 16-bita) and then (was so exciting) , the driver initialized and sent the wished C2 PLL address over I2C bus <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin :D" loading="lazy" data-shortname=":D" /> .</p><p></p><p>Suddenly it has not tuned anything, as it is searching for a 7MHz bandwidth signal, while in my area we have 8MHz channels. And probably there is at least one more thing in the setup of MT352, which is not correct and this is a method how the TS data are sent to a bt878. So with a drivers posted here: <a href="http://www.althan.cz/A771/fusion1.rar" target="_blank">http://www.althan.cz/A771/fusion1.rar</a> you should be able to tune to a channel a get a channel lock and some signal level readings, but of course still not any DVB data probably. </p><p></p><p>I will have to install some BDA DVB-T player now and configure it properly to test it here, where 8MHz bandwidth channels are used, but I have tried DW7.01 with no luck, so, please, somebody try it with MP or something. I would really like to see that we are on the good way, so I should keep continuing !</p></blockquote><p></p>
[QUOTE="RaStr, post: 10846"] [b]ZULU driver - success ![/b] So finally I have found where the C0 is stored, but it took another 4 hours from my regular sleep time ! The major problem was, that the tuning is not served by the zulutune.sys, after a couple of tries and some hours of work I have find out that I could even delete the .sys file from system32\drivers folder and the behavior of my setup will be still the same (i.e. all I2C command passed in the same order). So I have focused on the zulubda.sys driver, as it uses registry value named "TunerModel" which is actually the parameter deciding which tunnig algorithm will be used ! Then after some more hours I have found some part of its code, suspicious of defining the PLL I2C address, I have changed this to give it a try, but the driver then failed to load ! After another hour of research and tries I have discovered that the driver binary is protected by CRC, so I have had to change at least two bytes of code instead one only, after one more try I have discovered that they have to be word aligned (as the CRC is at least 16-bita) and then (was so exciting) , the driver initialized and sent the wished C2 PLL address over I2C bus :D . Suddenly it has not tuned anything, as it is searching for a 7MHz bandwidth signal, while in my area we have 8MHz channels. And probably there is at least one more thing in the setup of MT352, which is not correct and this is a method how the TS data are sent to a bt878. So with a drivers posted here: [url]http://www.althan.cz/A771/fusion1.rar[/url] you should be able to tune to a channel a get a channel lock and some signal level readings, but of course still not any DVB data probably. I will have to install some BDA DVB-T player now and configure it properly to test it here, where 8MHz bandwidth channels are used, but I have tried DW7.01 with no luck, so, please, somebody try it with MP or something. I would really like to see that we are on the good way, so I should keep continuing ! [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
General Support
AverTV DVB-T 771
Contact us
RSS
Top
Bottom