Skip to contentSkip to conversation

YUAN High-Tech STK7700PH problem

linux-dvb roshan karki 3 participants 6 messages Jan 2, 2009 2 messages not in the archive Media (V4L/DVB)

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

roshan karki

author
#2 lore raw

Here is the usbsnoop I had taken when I had Windows with me,
http://pastebin.com/m49cacaba

Quoted 117 lines · Devin Heitmueller

I looked at the annotation of the patch you sent, and indeed I think you have the correct patch. I also checked to see if there was a subsequent change to the GPIO configuration that might have broken your card, and there doesn't appear to have been one.

You can try emailing Patrick Boettcher and see if he has any advice, since he is driver maintainer for dib0700.

Also, if you could get a usbsnoop from a Windows system that includes plugging in the device and starting a capture, I can check to see if the GPIOs are correct.

Devin

Quoted 10 lines · Roshan Karki

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I've found this, this matches my usb id. Is there anything you can do, or should I try to contact the author?
http://linuxtv.org/hg/v4l-dvb/rev/0dc9cba480ba

On Sat, Dec 20, 2008 at 6:25 AM, Roshan Karki <[email protected]>

Quoted 5 lines · wrote:
Quoted 5 lines
Quoted 5 lines

Hello,

I have tv-tuner with may laptop. I downloaded the source from linuxtv.org and installed it. It asked for two files dvb-usb-dib0700-1.20.fw and xc3028-v27.fw. which I copied from

internet.

Quoted 76 lines
Quoted 12 lines
Quoted 12 lines

I cant however scan for any channels. I have added dump_stack to dib0700_core.c and here is the dmesg output.

http://pastebin.com/d77534a37

snippet from irc
<roxan> devinheitmueller: does it look if my hardware is damaged? <devinheitmueller> Well, the dib7000p demodulator is not answering the very first i2c command it is sent, which usually means the chip is totally non-functional.

Quoted 4 lines
Quoted 4 lines

Please help.
--
Regards,
Roshan Karki

To elaborate on Roshan's situation (since I spent an hour debugging it this morning with him on #linuxtv), basically his problem is the dib7000p is not responding to even the i2c query for the vendor info (which is the first request sent to the chip). I suspect that perhaps the GPIOs are not setup properly and the chip is being held in reset.

I had him rule out faulty hardware by having him boot into Windows and successfully perform a capture.

Does anyone know who did the driver work for the "YUAN High-Tech STK7700PH" product? I will dig through the hg history if nobody speaks up...

Also, there were some bugs in the dib0700 exception handling that made this harder to debug than it should have been. I will send Patrick some patches next week if I have time (I found three or four issues).

Devin

= Below is the dump_stack() results I had him add so we could see
where the i2c error was coming from =

[<f8c36afd>] dib0700_i2c_xfer+0x44d/0x470 [dvb_usb_dib0700]
[<f8acb5c9>] i2c_transfer+0x69/0xa0 [i2c_core]
 [<f8bf7143>] dib7000p_read_word+0x63/0xc0 [dib7000p]
[<f8bf7ebc>] dib7000p_identify+0x2c/0x130 [dib7000p]
[<f8bf8088>] dib7000p_i2c_enumeration+0xc8/0x270 [dib7000p]
[<f8c37609>] stk7700ph_frontend_attach+0x119/0x1c0 [dvb_usb_dib0700]
[<f8bb207b>] dvb_usb_adapter_frontend_init+0x1b/0x100 [dvb_usb]
[<f8bb1917>] dvb_usb_device_init+0x387/0x600 [dvb_usb]
[<f8c36b75>] dib0700_probe+0x55/0x80 [dvb_usb_dib0700]
[<f88df4e7>] usb_probe_interface+0xa7/0x140 [usbcore]
[<c0201107>] ? sysfs_create_link+0x17/0x20
[<c02c3d4e>] really_probe+0xee/0x190
[<f88de8a9>] ? usb_match_id+0x49/0x60 [usbcore]
[<c02c3e33>] driver_probe_device+0x43/0x60
[<c02c3ec9>] __driver_attach+0x79/0x80
[<c02c3593>] bus_for_each_dev+0x53/0x80
[<c02c3b6e>] driver_attach+0x1e/0x20
[<c02c3e50>] ? __driver_attach+0x0/0x80
[<c02c2f37>] bus_add_driver+0x1b7/0x230
[<c02c409e>] driver_register+0x6e/0x150
[<f88df7bc>] usb_register_driver+0x7c/0xf0 [usbcore]
[<f8991000>] ? dib0700_module_init+0x0/0x55 [dvb_usb_dib0700]
[<f8991000>] ? dib0700_module_init+0x0/0x55 [dvb_usb_dib0700]
[<f8991035>] dib0700_module_init+0x35/0x55 [dvb_usb_dib0700]
[<c0101120>] _stext+0x30/0x160
[<c014c604>] ? __blocking_notifier_call_chain+0x14/0x70
[<c015c208>] sys_init_module+0x88/0x1b0
[<c0103f7b>] sysenter_do_call+0x12/0x2f

- --
Devin J. Heitmueller
http://www.devinheitmueller.com
AIM: devinheitmueller
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

Quoted 6 lines

iEUEARECAAYFAklaDfwACgkQWFF7kkN08jtYyACfYK1gYeyu6UbK1+TmHcIVAd5F v4EAmILjXFCY/1t0TIdUf+40t0oovBc=
=Pcn+
-----END PGP SIGNATURE-----

Quoted 5 lines

--
Devin J. Heitmueller
http://www.devinheitmueller.com
AIM: devinheitmueller

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#3 lore raw
Quoted 3 lines · roshan karki

Here is the usbsnoop I had taken when I had Windows with me,
http://pastebin.com/m49cacaba

I'll try to look at this over the weekend.

Devin

Signature · 8 lines
Devin J. Heitmueller
http://www.devinheitmueller.com
AIM: devinheitmueller

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
#4 lore raw
In reply to roshan karki

Hi all, sorry for the delay, I didn't noticed the first mail. I added this patch, but I don't own any of this cards; the status was quite strange. One of the testers said that it was working perfectly while the other (there was not much people with that model) said it didn't work. So, I'm not sure if there is more than one hardware version with the same ID or something similar...

Albert

2009/1/2 roshan karki <[email protected]>

Quoted 134 lines

Here is the usbsnoop I had taken when I had Windows with me,
http://pastebin.com/m49cacaba

Quoted 119 lines · Devin Heitmueller

I looked at the annotation of the patch you sent, and indeed I think you have the correct patch. I also checked to see if there was a subsequent change to the GPIO configuration that might have broken your card, and there doesn't appear to have been one.

You can try emailing Patrick Boettcher and see if he has any advice, since he is driver maintainer for dib0700.

Also, if you could get a usbsnoop from a Windows system that includes plugging in the device and starting a capture, I can check to see if the GPIOs are correct.

Devin

Quoted 10 lines · Roshan Karki

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I've found this, this matches my usb id. Is there anything you can do, or should I try to contact the author?
http://linuxtv.org/hg/v4l-dvb/rev/0dc9cba480ba

On Sat, Dec 20, 2008 at 6:25 AM, Roshan Karki <[email protected]>

Quoted 5 lines · wrote:
Quoted 5 lines
Quoted 5 lines

Hello,

I have tv-tuner with may laptop. I downloaded the source from linuxtv.org and installed it. It asked for two files dvb-usb-dib0700-1.20.fw and xc3028-v27.fw. which I copied from

internet.

Quoted 9 lines
Quoted 9 lines
Quoted 9 lines

I cant however scan for any channels. I have added dump_stack to dib0700_core.c and here is the dmesg output.

http://pastebin.com/d77534a37

snippet from irc
<roxan> devinheitmueller: does it look if my hardware is damaged? <devinheitmueller> Well, the dib7000p demodulator is not answering

the

Quoted 67 lines
Quoted 7 lines
Quoted 7 lines

very first i2c command it is sent, which usually means the chip is totally non-functional.

Please help.
--
Regards,
Roshan Karki

To elaborate on Roshan's situation (since I spent an hour debugging it this morning with him on #linuxtv), basically his problem is the dib7000p is not responding to even the i2c query for the vendor info (which is the first request sent to the chip). I suspect that perhaps the GPIOs are not setup properly and the chip is being held in reset.

I had him rule out faulty hardware by having him boot into Windows and successfully perform a capture.

Does anyone know who did the driver work for the "YUAN High-Tech STK7700PH" product? I will dig through the hg history if nobody speaks up...

Also, there were some bugs in the dib0700 exception handling that made this harder to debug than it should have been. I will send Patrick some patches next week if I have time (I found three or four issues).

Devin

= Below is the dump_stack() results I had him add so we could see
where the i2c error was coming from =

[<f8c36afd>] dib0700_i2c_xfer+0x44d/0x470 [dvb_usb_dib0700]
[<f8acb5c9>] i2c_transfer+0x69/0xa0 [i2c_core]
 [<f8bf7143>] dib7000p_read_word+0x63/0xc0 [dib7000p]
[<f8bf7ebc>] dib7000p_identify+0x2c/0x130 [dib7000p]
[<f8bf8088>] dib7000p_i2c_enumeration+0xc8/0x270 [dib7000p]
[<f8c37609>] stk7700ph_frontend_attach+0x119/0x1c0 [dvb_usb_dib0700]
[<f8bb207b>] dvb_usb_adapter_frontend_init+0x1b/0x100 [dvb_usb]
[<f8bb1917>] dvb_usb_device_init+0x387/0x600 [dvb_usb]
[<f8c36b75>] dib0700_probe+0x55/0x80 [dvb_usb_dib0700]
[<f88df4e7>] usb_probe_interface+0xa7/0x140 [usbcore]
[<c0201107>] ? sysfs_create_link+0x17/0x20
[<c02c3d4e>] really_probe+0xee/0x190
[<f88de8a9>] ? usb_match_id+0x49/0x60 [usbcore]
[<c02c3e33>] driver_probe_device+0x43/0x60
[<c02c3ec9>] __driver_attach+0x79/0x80
[<c02c3593>] bus_for_each_dev+0x53/0x80
[<c02c3b6e>] driver_attach+0x1e/0x20
[<c02c3e50>] ? __driver_attach+0x0/0x80
[<c02c2f37>] bus_add_driver+0x1b7/0x230
[<c02c409e>] driver_register+0x6e/0x150
[<f88df7bc>] usb_register_driver+0x7c/0xf0 [usbcore]
[<f8991000>] ? dib0700_module_init+0x0/0x55 [dvb_usb_dib0700]
[<f8991000>] ? dib0700_module_init+0x0/0x55 [dvb_usb_dib0700]
[<f8991035>] dib0700_module_init+0x35/0x55 [dvb_usb_dib0700]
[<c0101120>] _stext+0x30/0x160
[<c014c604>] ? __blocking_notifier_call_chain+0x14/0x70
[<c015c208>] sys_init_module+0x88/0x1b0
[<c0103f7b>] sysenter_do_call+0x12/0x2f

- --
Devin J. Heitmueller
http://www.devinheitmueller.com
AIM: devinheitmueller
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

Quoted 6 lines

iEUEARECAAYFAklaDfwACgkQWFF7kkN08jtYyACfYK1gYeyu6UbK1+TmHcIVAd5F v4EAmILjXFCY/1t0TIdUf+40t0oovBc=
=Pcn+
-----END PGP SIGNATURE-----

Quoted 5 lines

--
Devin J. Heitmueller
http://www.devinheitmueller.com
AIM: devinheitmueller

Quoted 5 lines

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#5 lore raw
Quoted 8 lines · Albert Comerma

Hi all, sorry for the delay, I didn't noticed the first mail. I added this patch, but I don't own any of this cards; the status was quite strange. One of the testers said that it was working perfectly while the other (there was not much people with that model) said it didn't work. So, I'm not sure if there is more than one hardware version with the same ID or something similar...

Albert

Hello Albert,

As the person who submitted the original patch, thank you for taking the time to respond. From a debugging standpoint, it's good to know that the support never worked, as opposed to some breakage being introduced.

I'll look at Roshan's usb snoop trace over the weekend (unless you want to). I suspect the GPIOs are probably just not correctly for his device and the demod is probably still being held in reset when the first i2c command is sent.

Devin

Signature · 8 lines
Devin J. Heitmueller
http://www.devinheitmueller.com
AIM: devinheitmueller

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
#6 lore raw
Quoted 18 lines · Devin Heitmueller
Quoted 8 lines · Albert Comerma

Hi all, sorry for the delay, I didn't noticed the first mail. I added this patch, but I don't own any of this cards; the status was quite strange. One of the testers said that it was working perfectly while the other (there was not much people with that model) said it didn't work. So, I'm not sure if there is more than one hardware version with the same ID or something similar...

Albert

Hello Albert,

As the person who submitted the original patch, thank you for taking the time to respond. From a debugging standpoint, it's good to know that the support never worked, as opposed to some breakage being introduced.

Quoted 6 lines

I'll look at Roshan's usb snoop trace over the weekend (unless you want to). I suspect the GPIOs are probably just not correctly for his device and the demod is probably still being held in reset when the first i2c command is sent.

Devin

On a related note, I do have some patches queuing for Patrick to improve the exception handling, so that it fails in a more graceful manner.

Devin

Signature · 8 lines
Devin J. Heitmueller
http://www.devinheitmueller.com
AIM: devinheitmueller

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
#7 lore raw
In reply to Devin Heitmueller

I would like to understand what's happening, but I don't know anything about usbsnoop logs and next week I leave for a 2 months trip, so it would be difficult to look at it. I'm also thinking that is should be related to some GPIO (that's often the problem with dibcom based devices, find the correct place of everything), and could explain why it seemed to work once (if correctly set on windows and then just reboot without stopping the device. Good luck!

Albert

2009/1/2 Devin Heitmueller <[email protected]>

Quoted 26 lines
Quoted 1 line · Albert Comerma

Hi all, sorry for the delay, I didn't noticed the first mail. I added

this

Quoted 1 line

patch, but I don't own any of this cards; the status was quite strange.

One

Quoted 1 line

of the testers said that it was working perfectly while the other (there

was

Quoted 5 lines

not much people with that model) said it didn't work. So, I'm not sure if there is more than one hardware version with the same ID or something similar...

Albert

Hello Albert,

As the person who submitted the original patch, thank you for taking the time to respond. From a debugging standpoint, it's good to know that the support never worked, as opposed to some breakage being introduced.

I'll look at Roshan's usb snoop trace over the weekend (unless you want to). I suspect the GPIOs are probably just not correctly for his device and the demod is probably still being held in reset when the first i2c command is sent.

Quoted 7 lines

Devin

--
Devin J. Heitmueller
http://www.devinheitmueller.com
AIM: devinheitmueller

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb