[linux-dvb] Errors when running dvbscan for Twinhan VisionPlus DVB-T

Henrik Sjöberg henke at epact.se
Sat May 14 12:02:42 CEST 2005


Hi,

After some testing I have made the following discoveries:

* My card is identified as DTT-CI by dst_get_device_id
* The problems from dmesg doesn't seem to be a timeout. If I read 10
bytes from the answer from the tuning string instead of 8 (FIXED_COMM)
I get a complete message with a correct checksum in the end. However,
even though the tuning seems to go ok, dst_get_signal returns returns
the string '0x0 0x0 0x0 0x0 0x0 0x2 0xff 0xff' which is not
appreciated by the driver.
* So, reading 10 bytes instead of 8 looks a bit like a card with
DST_TYPE_HAS_NEWTUNE. So, I tried setting DST_TYPE_HAS_NEWTUNE. This
however, gave another problem. Since the request string for frequency
tuning changed, so did the answer. An answer that the driver
interpreted as an indication that the tuning failed.

Can anyone with more experience of the drivers draw any conclusions
from the logs below?

I'm a bit curious of the messages sent to the card.
00 06 00 00 00 00 00 fa is an identification reqeust
00 05 00 00 00 00 00 fb is a signel request
so, the second(and first?) byte(s) seem to be some kind of primitive
id. However, this is different when setting the frequency. For non
NEWTUNE card f1 f2 f3 00 bw 00 iv ea (fx=frequency, bw=bandwith,
iv=inversion) is used and for NEWTUNE cards, the same, but with a two
byte header is used. These two bytes are 09 00, which could be
primitive id, if it is two bytes.

How have you deduced the different messages? By trial and error, by
debugging the windows driver or by some other mean?

Ok, now finally to the two logs:

Reading 10 bytes instead of 8 in dst_get_tuna:
==============================================
May 14 09:56:35 thay kernel: Set Frequency = [522000000]
May 14 09:56:35 thay kernel: dst_write_tuna: type_flags 0x52
May 14 09:56:35 thay kernel: dst_comm_init: Initializing DST..
May 14 09:56:35 thay kernel: dst_gpio_outb: mask=[ffffffff],
enbb=[0001], outhigh=[0000]
May 14 09:56:35 thay kernel: rdc_reset_state: Resetting state machine
May 14 09:56:35 thay kernel: dst_gpio_outb: mask=[0002], enbb=[0002],
outhigh=[0000]
May 14 09:56:35 thay kernel: dst_gpio_outb: mask=[0002], enbb=[0002],
outhigh=[0002]
May 14 09:56:35 thay kernel: write_dst writing 07 f7 10 00 08 00 00 ea
May 14 09:56:35 thay kernel: dst_gpio_outb: mask=[ffffffff],
enbb=[0000], outhigh=[0000]
May 14 09:56:35 thay kernel: read_dst reply is 0xff
May 14 09:56:35 thay kernel: dst_wait_dst_ready: dst wait ready after
1
May 14 09:56:35 thay kernel: read_dst reply is 0x9
May 14 09:56:35 thay kernel:  0xc1 0x11 0xbd 0x0 0x26 0x0 0x0 0x0 0x42
May 14 09:56:35 thay kernel: dst_comm_init: Initializing DST..
May 14 09:56:35 thay kernel: dst_gpio_outb: mask=[ffffffff],
enbb=[0001], outhigh=[0000]
May 14 09:56:35 thay kernel: rdc_reset_state: Resetting state machine
May 14 09:56:35 thay kernel: dst_gpio_outb: mask=[0002], enbb=[0002],
outhigh=[0000]
May 14 09:56:36 thay kernel: dst_gpio_outb: mask=[0002], enbb=[0002],
outhigh=[0002]
May 14 09:56:36 thay kernel: write_dst writing 00 05 00 00 00 00 00 fb
May 14 09:56:36 thay kernel: dst_gpio_outb: mask=[ffffffff],
enbb=[0000], outhigh=[0000]
May 14 09:56:36 thay kernel: read_dst reply is 0xff
May 14 09:56:36 thay kernel: dst_wait_dst_ready: dst wait ready after
1
May 14 09:56:36 thay kernel: read_dst reply is 0x0
May 14 09:56:36 thay kernel:  0x0 0x0 0x0 0x0 0x2 0xff 0xff

Setting DST_TYPE_HAS_NEWTUNE for card DTT-CI
============================================
May 14 10:19:07 thay kernel: Set Frequency = [522000000]
May 14 10:19:07 thay kernel: dst_write_tuna: type_flags 0x51
May 14 10:19:07 thay kernel: dst_comm_init: Initializing DST..
May 14 10:19:07 thay kernel: dst_gpio_outb: mask=[ffffffff],
enbb=[0001], outhigh=[0000]
May 14 10:19:07 thay kernel: rdc_reset_state: Resetting state machine
May 14 10:19:07 thay kernel: dst_gpio_outb: mask=[0002], enbb=[0002],
outhigh=[0000]
May 14 10:19:07 thay kernel: dst_gpio_outb: mask=[0002], enbb=[0002],
outhigh=[0002]
May 14 10:19:07 thay kernel: write_dst writing 09 00 07 f7 10 00 08 00
00 e1
May 14 10:19:07 thay kernel: dst_gpio_outb: mask=[ffffffff],
enbb=[0000], outhigh=[0000]
May 14 10:19:07 thay kernel: read_dst reply is 0xff
May 14 10:19:07 thay kernel: dst_wait_dst_ready: dst wait ready after
1
May 14 10:19:07 thay kernel: read_dst reply is 0x9
May 14 10:19:07 thay kernel:  0x0 0x0 0x0 0x0 0x0 0x8 0x0 0x0 0xef


Henrik

> -------------------
> > Hi,
> > 
> > I'm using kernel 2.6.11.8, which should have the patches you
> mention.
> > I am still seeing the same kinds of problem. Even with the
> asic_delay
> > patch posted earlier and asic_delay set to 10,30,40,50 and 100.
> > 
> > When trying to scan, dmesg still tells me:
> > Set Frequency = [522000000]
> > dst_comm_init: Initializing DST..
> > dst_gpio_outb: mask=[ffffffff], enbb=[0001], outhigh=[0000]
> > rdc_reset_state: Resetting state machine
> > dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0000]
> > dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002]
> > write_dst writing 07 f7 10 00 08 00 00 ea
> > dst_gpio_outb: mask=[ffffffff], enbb=[0000], outhigh=[0000]
> > read_dst reply is 0xff
> > dst_wait_dst_ready: dst wait ready after 1
> > read_dst reply is 0x9
> >  0xc1 0x11 0xbd 0x0 0x26 0x0 0x0
> > dst_get_tuna: checksum failure?
> > Set Frequency = [522000000]
> > dst_comm_init: Initializing DST..
> > dst_gpio_outb: mask=[ffffffff], enbb=[0001], outhigh=[0000]
> > rdc_reset_state: Resetting state machine
> > dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0000]
> > dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002]
> > write_dst writing 07 f7 10 00 08 00 80 6a
> > write_dst: _write_dst error (err == -5, len == 0x08, b0 == 0x07)
> > dst_error_recovery: Trying to return from previous errors...
> > dst_gpio_outb: mask=[ffffffff], enbb=[0000], outhigh=[0000]
> > dst_gpio_outb: mask=[ffffffff], enbb=[0001], outhigh=[0000]
> > dst_gpio_outb: mask=[ffffffff], enbb=[0000], outhigh=[0000]
> > read_dst reply is 0xff
> > dst_wait_dst_ready: dst wait ready after 1
> > read_dst reply is 0x9
> >  0xc1 0x11 0xbd 0x0 0x26 0x0 0x0
> > dst_get_tuna: checksum failure?
> > 
> > 
> > Am I correct in my assumptions that 2.6.11.8 contains the patches?
> > 
> > /Henrik
> 
> 
> -------------------
> > Hans Gunnarsson wrote:
> > 
> > > Hi all!
> > >
> > > I have patched the bttv driver with Manu's "anti-freeze" patch,
> and am 
> > > using the latest CVS from dvb. The kernel is 2.6.11
> > >
> > > Compiling and loading the modules are fine, but when I try to
scan
> it 
> > > returns Tuning failed!
> > >
> > > Any ideas?
> > >
> > 
> > You need to use the bttv timout patch which i posted a while back
> along 
> > with the freeze patch, for kernel = 2.6.11.
> > for kernel > 2.6.12-rc4 it has the freeze patch as well as the
> timeout 
> > patch.
> > 
> > Right now i am out of station and can't send you the patch..
> > 
> > > The following output on command line:
> > >
> > > hansg at muhammed:~/project/dvb_trunk/dvb-apps/util/scan>./dvbscan 
> > > dvb-t/se-Stockholm_Nacka
> > > scanning dvb-t/se-Stockholm_Nacka
> > > using '/dev/dvb/adapter0/frontend0' and
'/dev/dvb/adapter0/demux0'
> > > initial transponder 730000000 0 2 9 3 1 2 0
> > > initial transponder 754000000 0 2 9 3 1 2 0
> > > initial transponder 778000000 0 2 9 3 1 2 0
> > > initial transponder 706000000 0 2 9 3 1 2 0
> > > initial transponder 746000000 0 2 9 3 1 2 0
> > > >>> tune to: 
> > >
>
730000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANS
> MISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE 
> > >
> > > WARNING: >>> tuning failed!!!
> > > >>> tune to: 
> > >
>
730000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANS
> MISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE 
> > > (tuning failed)
> > 
> > 
> > Yep, timed out..
> > 
> > >
> > > WARNING: >>> tuning failed!!!
> > > >>> tune to: 
> > >
>
754000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANS
> MISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE 
> > >
> > > WARNING: >>> tuning failed!!!
> > > >>> tune to: 
> > >
>
754000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANS
> MISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE 
> > > (tuning failed)
> > > WARNING: >>> tuning failed!!!
> > > >>> tune to: 
> > >
>
778000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANS
> MISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE 
> > >
> > > WARNING: >>> tuning failed!!!
> > > >>> tune to: 
> > >
>
778000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANS
> MISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE 
> > > (tuning failed)
> > > WARNING: >>> tuning failed!!!
> > > >>> tune to: 
> > >
>
706000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANS
> MISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE 
> > >
> > > WARNING: >>> tuning failed!!!
> > > >>> tune to: 
> > >
>
706000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANS
> MISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE 
> > > (tuning failed)
> > > WARNING: >>> tuning failed!!!
> > > >>> tune to: 
> > >
>
746000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANS
> MISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE 
> > >
> > > WARNING: >>> tuning failed!!!
> > > >>> tune to: 
> > >
>
746000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANS
> MISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE 
> > > (tuning failed)
> > > WARNING: >>> tuning failed!!!
> > > ERROR: initial tuning failed
> > > dumping lists (0 services)
> > > Done.
> > >
> > >
> > >
> > >
> > > the interesting parts of dmesg:
> > >
> > > videodev: unsupported module, tainting kernel.
> > > Linux video capture interface: v1.00
> > > tveeprom: unsupported module, tainting kernel.
> > > btcx_risc: unsupported module, tainting kernel.
> > > v4l2_common: unsupported module, tainting kernel.
> > > video_buf: unsupported module, tainting kernel.
> > > bttv: unsupported module, tainting kernel.
> > > bttv: driver version 0.9.15 loaded
> > > bttv: using 8 buffers with 2080k (520 pages) each for capture
> > > bttv: Bt8xx card found (0).
> > > ACPI: PCI interrupt 0000:06:02.0[A] -> GSI 18 (level, low) ->
IRQ
> 217
> > > bttv0: Bt878 (rev 17) at 0000:06:02.0, irq: 217, latency: 32,
> mmio: 
> > > 0xdfefe000
> > > bttv0: detected: Twinhan VisionPlus DVB-T [card=113], PCI
> subsystem ID 
> > > is 1822:0001
> > > bttv0: using: Twinhan DST + clones [card=113,insmod option]
> > > bttv0: gpio: en=00000000, out=00000000 in=00f500fd [init]
> > > bttv0: using tuner=4
> > > tuner: unsupported module, tainting kernel.
> > > bttv0: add subdevice "dvb0"
> > > or51211: unsupported module, tainting kernel.
> > > cx24110: unsupported module, tainting kernel.
> > > dvb_core: unsupported module, tainting kernel.
> > > bt878: unsupported module, tainting kernel.
> > > bt878: AUDIO driver version 0.0.0 loaded
> > > bt878: Bt878 AUDIO function found (0).
> > > ACPI: PCI interrupt 0000:06:02.1[A] -> GSI 18 (level, low) ->
IRQ
> 217
> > > bt878(0): Bt878 (rev 17) at 06:02.1, irq: 217, latency: 32,
> memory: 
> > > 0xdfeff000
> > > dst: unsupported module, tainting kernel.
> > > dst_ca: unsupported module, tainting kernel.
> > > sp887x: unsupported module, tainting kernel.
> > > mt352: unsupported module, tainting kernel.
> > > nxt6000: unsupported module, tainting kernel.
> > > dvb_bt8xx: unsupported module, tainting kernel.
> > > DVB: registering new adapter (bttv0).
> > > dst_get_device_id: Recognise [DTT-CI]
> > > DST type : terrestrial
> > > DST type flags : 0x2 ts204 0x10 firmware version = 2
> > > DVB: registering frontend 0 (DST DVB-T)...
> > > read_dst: read_dst error (err == -5, len == 0x01, b0 == 0xf7)
> > > dst_error_recovery: Trying to return from previous errors...
> > > read_dst: read_dst error (err == -5, len == 0x01, b0 == 0xf7)
> > > dst_error_recovery: Trying to return from previous errors...
> > > dst_error_bailout: Trying to bailout from previous error...
> > > dst_write_tuna: read verify not successful.
> > 
> > 
> > No doubts that it timed out.
> > 
> > 
> > Manu.
> > 
> > 
> > _______________________________________________
> > linux-dvb mailing list
> > linux-dvb at linuxtv.org
> > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
> > 
> 
> _______________________________________________
> linux-dvb mailing list
> linux-dvb at linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
> 




More information about the linux-dvb mailing list