Skip to contentSkip to conversation

Kworld ATSC usb 435Q device and RF tracking filter calibration

DISCUSSION Amy Overmyer 3 participants 3 messages Feb 9, 2010 Media (V4L/DVB)

lore
Share & tools
lore
#0 lore raw

I have one of these devices. It works OK in windows, but I'd like to stick it on my myth backend as a 3rd tuner, just in case. I'm using it for 8VSB OTA. I took a patch put forth a while back on this list and was able to put that on the kernel 2.6.31.6. I am able to tune and lock channels with it, but, like the people earlier, I see the RF tracking filter calibration in the syslogs and tuning takes some time.

Is there anything I can do to debug this? I'm a programmer by trade (err my systems are usually a bit more special purpose than a linux box as I'm an embedded systems type guy, but it's all bits anyway), so don't be afraid to suggest code changes or point me in a direction.

Thanks,

#1 lore raw
Quoted 3 lines · Amy Overmyer

I have one of these devices. It works OK in windows, but I'd like to stick it on my myth backend as a 3rd tuner, just in case. I'm using it for 8VSB OTA. I took a patch put forth a while back on this list and was able to put that on the kernel 2.6.31.6. I am able to tune and lock channels with it, but, like the people earlier, I see the RF tracking filter calibration in the syslogs and tuning takes some time.

Is there anything I can do to debug this? I'm a programmer by trade (err my systems are usually a bit more special purpose than a linux box as I'm an embedded systems type guy, but it's all bits anyway), so don't be afraid to suggest code changes or point me in a direction.

Best as I can recall, the problem is with the gpio reset sequence for these devices. Something is getting reset when it shouldn't, and all the tda18271 registers wind up zeroed out when they shouldn't be, and thus rf tracking filter calibration gets re-run, because the register bit that signifies its already been done isn't set any longer... So there needs to be some debugging done, probably with the gpio reset config. I keep meaning to hook the stick up under windows and sniff traffic again to see if I can see what's being done differently, just don't ever seem to get around to it.

Signature · 2 lines
Jarod Wilson
[email protected]
#2 lore raw
In reply to Amy Overmyer

I have this stick running on my Mythtv box with the patch and a quick hack to disable the additional calibrations. It works, most of the time, but will occasionally stop working until I reboot. The frequency of this is reduced if I tell Mythbackend to only grab the tuner when it needs it... might be a calibration issue, might be marginal hardware overheating.

-R C

Quoted 13 lines · Amy Overmyer

I have one of these devices. It works OK in windows, but I'd like to stick it on my myth backend as a 3rd tuner, just in case. I'm using it for 8VSB OTA. I took a patch put forth a while back on this list and was able to put that on the kernel 2.6.31.6. I am able to tune and lock channels with it, but, like the people earlier, I see the RF tracking filter calibration in the syslogs and tuning takes some time.

Is there anything I can do to debug this? I'm a programmer by trade (err my systems are usually a bit more special purpose than a linux box as I'm an embedded systems type guy, but it's all bits anyway), so don't be afraid to suggest code changes or point me in a direction.

Thanks,

--
To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html