Terratec H7 Rev. 4 is DVBSky

Hi,

I recently got a Terratec H7 in Revision 4 and turned out that it is not just a new revision, but a new product with USB ProductID 0x10a5. Previous revisions have been AZ6007, but this revision does not work with this driver [1].

Output of lsusb (extended output attached):
Bus 001 Device 011: ID 0ccd:10a5 TerraTec Electronic GmbH

The revision 4 seems to a DVBSky variant, adding its Product ID to dvbsky.c with the attached patch enabled me to scan for channels and watch DVB-C and DVB-T.

greetings,
Erik

[1] https://www.mail-archive.com/[email protected]/msg70934.html

From b453f37d9a6e9910cb7d76fa58ba724449ac9a22 Mon Sep 17 00:00:00 2001
From: Erik Andresen <[email protected]>
Date: Fri, 11 Sep 2015 16:51:10 +0200
Subject: [PATCH] Add Terratec H7 Revision 4 to DVBSky driver

---
 drivers/media/dvb-core/dvb-usb-ids.h  | 1 +
 drivers/media/usb/dvb-usb-v2/dvbsky.c | 4 ++++
 2 files changed, 5 insertions(+)

index c117fb3..0a46580 100644
@@ -257,6 +257,7 @@
 #define USB_PID_TERRATEC_CINERGY_T_XXS_2		0x00ab
 #define USB_PID_TERRATEC_H7				0x10b4
 #define USB_PID_TERRATEC_H7_2				0x10a3
+#define USB_PID_TERRATEC_H7_3				0x10a5
 #define USB_PID_TERRATEC_T3				0x10a0
 #define USB_PID_TERRATEC_T5				0x10a1
 #define USB_PID_NOXON_DAB_STICK				0x00b3

index cdf59bc..8f526a4 100644
@@ -841,6 +841,10 @@ static const struct usb_device_id dvbsky_id_table[] = {
 		USB_PID_TECHNOTREND_CONNECT_CT2_4650_CI,
 		&dvbsky_t680c_props, "TechnoTrend TT-connect CT2-4650 CI",
 		RC_MAP_TT_1500) },
+        { DVB_USB_DEVICE(USB_VID_TERRATEC,
+                USB_PID_TERRATEC_H7_3,
+                &dvbsky_t680c_props, "Terratec H7 Rev.4",
+                RC_MAP_TT_1500) },
 	{ }
 };
 MODULE_DEVICE_TABLE(usb, dvbsky_id_table);

2.5.0

Bus 002 Device 009: ID 0ccd:10a5 TerraTec Electronic GmbH Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00

  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x0ccd TerraTec Electronic GmbH
  idProduct          0x10a5 
  bcdDevice            0.00
  iManufacturer           1 
  iProduct                2 
  iSerial                 3 
  bNumConfigurations      1

Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 219
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 4
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 3
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x13f2 3x 1010 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 2
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 3
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x12d6 3x 726 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 3
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 3
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x12ae 3x 686 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 4
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 3
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x03ca 1x 970 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 5
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 3
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x02ac 1x 684 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 6
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 3
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x03ac 1x 940 bytes
bInterval 1

Hi Erik,

Your patch looks good to my eyes. I heard already earlier that the new H7 is the same as the DVBSky receiver and your experience seems to confirm that. Could you resend the patch again with a proper title and a signed-off line to the mailing list?
https://www.kernel.org/doc/Documentation/SubmittingPatches is good reading as well.

Cheers,
-olli

Adds Terratec H7 Rev. 4 with USB id 0ccd:10a5 to DVBSky driver.

---
 drivers/media/dvb-core/dvb-usb-ids.h  | 1 +
 drivers/media/usb/dvb-usb-v2/dvbsky.c | 4 ++++
 2 files changed, 5 insertions(+)

index c117fb3..0a46580 100644
@@ -257,6 +257,7 @@
 #define USB_PID_TERRATEC_CINERGY_T_XXS_2		0x00ab
 #define USB_PID_TERRATEC_H7				0x10b4
 #define USB_PID_TERRATEC_H7_2				0x10a3
+#define USB_PID_TERRATEC_H7_3				0x10a5
 #define USB_PID_TERRATEC_T3				0x10a0
 #define USB_PID_TERRATEC_T5				0x10a1
 #define USB_PID_NOXON_DAB_STICK				0x00b3

index cdf59bc..8f526a4 100644
@@ -841,6 +841,10 @@ static const struct usb_device_id dvbsky_id_table[] = {
 		USB_PID_TECHNOTREND_CONNECT_CT2_4650_CI,
 		&dvbsky_t680c_props, "TechnoTrend TT-connect CT2-4650 CI",
 		RC_MAP_TT_1500) },
+        { DVB_USB_DEVICE(USB_VID_TERRATEC,
+                USB_PID_TERRATEC_H7_3,
+                &dvbsky_t680c_props, "Terratec H7 Rev.4",
+                RC_MAP_TT_1500) },
 	{ }
 };
 MODULE_DEVICE_TABLE(usb, dvbsky_id_table);

2.5.0

Den 2015-09-11 kl. 17:04, skrev Erik Andresen:

Do I feel lucky or what..
Just got my H7 devices delivered and noticed the lack of supported driver and some quick searches gave me this e-mail. Maybe should take a trip to the race track. :)

I have tried this driver and it works wonderfully. I have noticed a freeze or two when handling the device (powering off, ripping USB etc) but I'm not sure it is the driver that is causing this.

I do notice something weird. The remote doesn't seem to work. Found /sys/class/rc/rc0/ (/dev/input/event14) with:
Driver dvb_usb_dvbsky, table rc-tt-1500 Supported protocols: RC-5
Enabled protocols:
Name: Terratec H7 Rev.4
bus: 3, vendor/product: 0ccd:10a5, version: 0x0000 Repeat delay = 500 ms, repeat period = 125 ms

I'm not able to enable any protocols. Nothing happens when running ir-keytable with "-p rc-5". Nothing shows in the row "Enabled protocols" and nothing happens when testing with "ir-keytable -t".

I've tested on a Ubuntu 14.04 (Mythbuntu) with Linux Kernel 4.2 that I have to compile myself. (Don't know in which kernel dvbsky was released) Tested using both Kaffeine and MythTV and it works like a charm (with the exception of missing IR).
I tested using DVB-C with CI for encrypted channels.

Den 2015-09-19 kl. 23:39, skrev Roger Mårtensson:

One more this..
Is there a possibility that Signal strength support could be added to the driver?
MythTV uses this and I think Kaffeine also uses it (not sure). Currently the logs are filling up with "Operation not supported".

Hi Roger,

try to give it the device, e.g.

ir-keytable -d /dev/input/event14 -t

I was able to get output from it. The device is now running for a week under mythbackend.

greetings,
Erik

Am 19.09.2015 um 23:48 schrieb Roger Mårtensson:

Den 2015-09-19 kl. 19:30, skrev Erik Andresen:

I have tested this on a Custom Linux 4.2 kernel and it is working as expected. Noticed a few things.

1) "Supported:" on ir-keytable doesn't show anything.
1b) Setting RC-5 with ir-keytable -p gives me an error.
2) Keymap tt-1500 may be for dvbsky but not for H7 Rev 4. Needed to do my own keymap. (48 button remote) 2b) The Remote buttons "Music" and "Pic" doesn't give any scancodes in ir-keytable -t.

I have tested in a DVB-C environment with CAM/CI and encrypted channels.
I have two H7 devices and one of them seem to get into a hang and needs to be powercycled now and then. At the moment it is always the same one that hangs. A linux reboot does not help but I need to do it sometimes together with a power cycle of the hanging device.

Den 2015-09-20 kl. 11:05, skrev Erik Andresen:

I got this to work but needed to create my own keymap since Ubuntu 14.04 didn't have it.

Den 2015-10-01 kl. 23:01, skrev Roger Mårtensson:

I forgot something and I'm not sure you have the right documentation for it. Some operations seems not to be implemented.
I get a lot of error in MythTV when locking to a channel. It sure would be nice to see it implemented. It doesn't do any harm. Only filling up the log.

Oct  1 23:11:16 tvpc mythbackend: mythbackend[2911]: E TVRecEvent recorders/dvbchannel.cpp:1026 (GetSignalStrength) DVBChan[23](/dev/dvb/adapter2/frontend0): Getting Frontend signal strength failed.#012#011#011#011eno: Operation not supported (95)
Oct  1 23:11:16 tvpc mythbackend: mythbackend[2911]: W TVRecEvent recorders/dvbsignalmonitor.cpp:91 (DVBSignalMonitor) DVBSigMon[23](/dev/dvb/adapter2/frontend0): Cannot measure Signal Strength#012#011#011#011eno: Operation not supported (95)
Oct  1 23:11:16 tvpc mythbackend: mythbackend[2911]: E TVRecEvent recorders/dvbchannel.cpp:1055 (GetSNR) DVBChan[23](/dev/dvb/adapter2/frontend0): Getting Frontend signal/noise ratio failed.#012#011#011#011eno: Operation not supported (95)
Oct  1 23:11:16 tvpc mythbackend: mythbackend[2911]: W TVRecEvent recorders/dvbsignalmonitor.cpp:93 (DVBSignalMonitor) DVBSigMon[23](/dev/dvb/adapter2/frontend0): Cannot measure S/N#012#011#011#011eno: Operation not supported (95)
Oct  1 23:11:16 tvpc mythbackend: mythbackend[2911]: E TVRecEvent recorders/dvbchannel.cpp:1081 (GetBitErrorRate) DVBChan[23](/dev/dvb/adapter2/frontend0): Getting Frontend signal error rate failed.#012#011#011#011eno: Operation not supported (95)
Oct  1 23:11:16 tvpc mythbackend: mythbackend[2911]: W TVRecEvent recorders/dvbsignalmonitor.cpp:95 (DVBSignalMonitor) DVBSigMon[23](/dev/dvb/adapter2/frontend0): Cannot measure Bit Error Rate#012#011#011#011eno: Operation not supported (95)
Oct  1 23:11:16 tvpc mythbackend: mythbackend[2911]: E TVRecEvent recorders/dvbchannel.cpp:1107 (GetUncorrectedBlockCount) DVBChan[23](/dev/dvb/adapter2/frontend0): Getting Frontend uncorrected block count failed.#012#011#011#011eno: Operation not supported (95)
Oct  1 23:11:16 tvpc mythbackend: mythbackend[2911]: W TVRecEvent recorders/dvbsignalmonitor.cpp:97 (DVBSignalMonitor) DVBSigMon[23](/dev/dvb/adapter2/frontend0): Cannot count Uncorrected Blocks#012#011#011#011eno: Operation not supported (95)
Oct  1 23:11:16 tvpc mythbackend: mythbackend[2911]: E SignalMonitor recorders/dvbchannel.cpp:1026 (GetSignalStrength) DVBChan[23](/dev/dvb/adapter2/frontend0): Getting Frontend signal strength failed.#012#011#011#011eno: Operation not supported (95)