| ↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |
| Who | What | When | |
|---|---|---|---|
| revell | mchehab or anybody else: i'm trying to add support for a terratec h6 (0ccd:10b2) and was wondering where dvb-usb-terratec-h5-drxk.fw came from and if there is some script to auto-extract the fw from the win drv? i had a look at http://www.linuxtv.org/wiki/index.php/Development:_How_to_extract_a_firmware , but there does not seem to be a script for terratec cards?
i also stumbled upon http://linux.terratec.de , but the site is down for quite a while now | [16:07] | |
| mchehab | terratec h6 already works... at least the one I have here
the same firmware used on H5 works on several other devices including h6 the script is already at Kernel tree, at Documentation/dvb/get_dvb_firmware there are some targets there for teh DRX-J firmware, like drxk_terratec_h5 and drxk_terratec_htc_stick | [16:17] | |
| revell | i see. since which kernel version is it supported? i'm on debian 4.0.0-2, so maybe i just need a newer kernel? and does your stick have the same PCI id (0ccd:10b2)? | [16:21] | |
| i cloned media-build.git and added USB_DEVICE(0x0ccd, 0x10b2) and some other line as this was not present before. now i at least see a basic setup of the card in dmesg, before i only got some output from the USB drv. so is it possible that your device has some different ID or am i missing sth. else? | [16:32] | ||
| ...... (idle for 29mn) | |||
| mchehab: i grepped the whole kernel media src for 0x10b2, but it does not show up anywhere besides the lines i added. http://www.linuxtv.org/wiki/index.php/TerraTec also does not list a H6 as well, so i'm a little bit confused | [17:01] | ||
| mchehab | perhaps Terratec added some new USB ID for it
H6 (the one I have) is identical to Terratec HTC 4.0 is OK are you sure that your H6 is also using DRJ-K? sometimes, manufacturers use the same brand name for different products | [17:02] | |
| revell | mchehab: i don't have much knowledge about the hardware of these cards, so i don't know. i just received this as a gift and was trying to make it work
mchehab: http://pastebin.com/YwSGt5Kx - this is what i added to the driver to get some basic output from dmesg. without this, nothing happened so far | [17:05] | |
| mchehab | revell: if you're creating a new entry, you need to change other things too
the best is to just associate the new USB ID to either Terratec H5 or Terratec HTC and see if it works + { USB_DEVICE(0x0ccd, 0x10b2), /* H6 MKII */ + .driver_info = EM2884_BOARD_TERRATEC_H5 }, should likely be enough if not, try to replace with the _HTC one or HVR_930C | [17:10] | |
| revell | mchehab: i will try, thanks. the product string "TERRATCE H5 MKII" seems a bit messed up as well, the label on the back of the stick says "TERRATEC H6 MKII" | [17:11] | |
| mchehab | if this works, we can just change the existing one to:
Terratec H5/H6 MKII | [17:12] | |
| .... (idle for 15mn) | |||
| revell | mchehab: i get i2c errors for both: http://pastebin.com/mLzAUkRm | [17:27] | |
| mchehab | well, then it very likely means that your H6 uses a different frontend
you would need to open the device, in order to double-check what's inside or that the GPIO used there is different (GPIO is used to turn on components of the device) this page: https://www.reddit.com/r/RTLSDR/comments/s6ddo/ implies that H6 uses DRX3926 with is DRX-K but it may be wrong TERRATEC H6 Empia EM2884 Micronas DRX3926 NXP TDA18271 0CCD 10B2 NO | [17:28] | |
| revell | mchehab: mine says Empia EM2884 Micronas DRX3926KA2 NXP TDA18271HDC2. i hope thats correct, as there are some color marks on the chips and the font is hard to read without magnifying glasses | [17:37] | |
| mchehab | revell: the only way to know for sure is to open the device
in any case, sniffing the device using the original driver is very likely required it is a shame that the PM at Terratec changed the old one used to help giving us some devices for testing and digging some needed info | [17:38] | |
| revell | mchehab: i opened it up, but as said there is some color smeared upon the label of the chips, so some of the numbers above may be incorrect
i rechecked: Empia EM2884 Micronas DRX3926KA2 NXP TDA18271HDC2 it is | [17:41] | |
| mchehab | good
it shouldn't then be hard to make it work... provided that we get the proper GPIO settings | [17:46] | |
| revell | revell is willing to try if you give some hints :) | [17:47] | |
| mchehab | take a look at terratec_h5_gpio and terratec_h5_digital
and terratec_h5_init() at em28xx-dvb something like that is needed to be written for your H6 this should be obtained by sniffing the USB configuration traffic on Windows
http://www.linuxtv.org/wiki/index.php/Usbsnoop | [17:47] | |
| revell | mchehab: allright, i will have a deeper look at it during the next days. should USB snoping work via VirtualBox or do i need a real windows box? | [17:52] | |
| and i forgot to mention: when using the _HTC version, at least /dev/video0 is auto-created, which is not the case with _H5. does this mean i better should look at the _HTC version and try with the HTC firmware?
and when grepping the kernel src for TDA18271HDC2 something shows up, but not for DRX3926KA2. does this mean that the latter is not supported? | [17:57] | ||
| mchehab | you could do USB snooping on a Linux image, but the procedure is different
look at v4l-utils there are some scripts there that helps with em28xx log parsing basically, on a Linux image (like qemu), the logs are sniffed at the host machine never tried to use virtualbox not sure if it provides proper USB2 emulation new versions of qemu do have not perfect, though drx3926 is drx-j I mean: drx-k | [18:06] | |
| revell | mchehab: ok, i will digg deeper into this during the next days and get back to you. thanks for your support so far! :) | [18:11] | |
| ↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |