Terratec CINERGY TC2 Stick does not work - actually works with correct firmware and correct muxes

oJPTo · October 22, 2023 at 2:06 PM

Hi,

I just installed a fresh LE 11 on Raspberry 3B+.

Now I wanted to try my DVB-T/DVB-C USB stick: Terratec CINERGY TC2 Stick

But it doesn't work.

I already tried on my PC, where I had to fetch dvb-usb-it9303-01.fw, dvb-demod-si2168-b40-01.fw, dvb-usb-terratec-htc-stick-drxk.fw, dvb-demod-si2168-02.fw from OpenElec Github repo.

on the PC it does not work either, because the Si2157 "device is buggy" and it does not load the firmware.

is here someone who supports making it work?

I am currently building mainline kernel to check if a newer kernel helps.

The errors shown below look like what I was getting on my PC when the firmware wasn't installed yet. But here there are no requests for firmware?

The chips used are:

ITE IT9306, Silicon Labs Si2157 ("device is buggy") and Si2168-B40

thanks

JPT

PS. tried putting the firmware in /storage/.config/firmware but this did not change anything. Why doesn't it load the firmware?

Code

[ 1870.870886] usb 1-1.3: new high-speed USB device number 7 using dwc_otg
[ 1870.965058] usb 1-1.3: New USB device found, idVendor=0ccd, idProduct=10b2, bcdDevice= 1.00
[ 1870.965104] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1870.965123] usb 1-1.3: Product: TS Aggregator
[ 1870.965139] usb 1-1.3: Manufacturer: CINERGY TC2 Stick
[ 1871.083996] em28xx 1-1.3:1.0: New device CINERGY TC2 Stick TS Aggregator @ 480 Mbps (0ccd:10b2, interface 0, class 0)
[ 1871.084027] em28xx 1-1.3:1.0: DVB interface 0 found: bulk
[ 1871.140985] em28xx 1-1.3:1.0: unknown em28xx chip ID (0)
[ 1871.198511] em28xx 1-1.3:1.0: reading from i2c device at 0xa0 failed (error=-5)
[ 1871.198541] em28xx 1-1.3:1.0: board has no eeprom
[ 1871.254173] em28xx 1-1.3:1.0: Identified as Terratec Cinergy H6 rev. 2 (card=101)
[ 1871.254205] em28xx 1-1.3:1.0: dvb set to bulk mode.
[ 1871.255632] usbcore: registered new interface driver em28xx
[ 1871.268407] em28xx 1-1.3:1.0: Binding DVB extension
[ 1871.272414] usbcore: registered new interface driver dvb_usb_af9035
[ 1871.302599] em28xx 1-1.3:1.0: writing to i2c device at 0x82 failed (error=-5)
[ 1871.302817] em28xx 1-1.3:1.0: writing to i2c device at 0x82 failed (error=-5)
[ 1871.303031] em28xx 1-1.3:1.0: writing to i2c device at 0x82 failed (error=-5)
[ 1871.303242] em28xx 1-1.3:1.0: writing to i2c device at 0x82 failed (error=-5)
[ 1871.303437] em28xx 1-1.3:1.0: writing to i2c device at 0x82 failed (error=-5)
[ 1871.372880] em28xx 1-1.3:1.0: reading from i2c device at 0x52 failed (error=-5)
[ 1871.373121] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1871.373134] drxk: i2c write error at addr 0x29
[ 1871.390387] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1871.390417] drxk: i2c write error at addr 0x29
[ 1871.401052] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1871.401077] drxk: i2c write error at addr 0x29
[ 1871.412335] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1871.412357] drxk: i2c write error at addr 0x29
[ 1871.423610] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1871.423633] drxk: i2c write error at addr 0x29
[ 1871.434399] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1871.434426] drxk: i2c write error at addr 0x29
[ 1871.445681] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1871.445706] drxk: i2c write error at addr 0x29
[ 1871.456959] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1871.456985] drxk: i2c write error at addr 0x29
[ 1871.467736] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1871.467767] drxk: i2c write error at addr 0x29
[ 1871.479020] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1871.479046] drxk: i2c write error at addr 0x29
[ 1871.490309] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1871.490335] drxk: i2c write error at addr 0x29
[ 1871.501117] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1871.501144] drxk: i2c write error at addr 0x29
[ 1871.512432] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1871.512460] drxk: i2c write error at addr 0x29
[ 1871.523719] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1871.523744] drxk: i2c write error at addr 0x29
[ 1871.534423] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1871.534452] drxk: i2c write error at addr 0x29
[ 1871.545695] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1871.545717] drxk: i2c write error at addr 0x29
[ 1871.556979] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1871.557006] drxk: i2c write error at addr 0x29
[ 1871.567733] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1871.567758] drxk: i2c write error at addr 0x29
[ 1871.579025] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1871.579049] drxk: i2c write error at addr 0x29
[ 1871.590310] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1871.590336] drxk: i2c write error at addr 0x29
[ 1871.600888] drxk: Error -5 on power_up_device
[ 1871.600913] drxk: Error -5 on init_drxk
[ 1871.600921] drxk: frontend initialized.
[ 1871.640750] tda18271 12-0060: creating new instance
[ 1871.641081] em28xx 1-1.3:1.0: writing to i2c device at 0xc0 failed (error=-5)
[ 1871.641101] tda18271_read_regs: [12-0060|M] ERROR: i2c_transfer returned: -5
[ 1871.641111] tda18271: Error reading device ID @ 12-0060, bailing out.
[ 1871.641120] tda18271_attach: [12-0060|M] error -5 on line 1271
[ 1871.641130] tda18271 12-0060: destroying instance
[ 1871.641308] em28xx: Registered (Em28xx dvb Extension) extension
[ 1871.668037] em28xx 1-1.3:1.0: Registering input extension
[ 1871.668128] em28xx: Registered (Em28xx Input Extension) extension
[ 1873.482992] usb 1-1.3: USB disconnect, device number 7
[ 1873.483636] em28xx 1-1.3:1.0: Disconnecting em28xx
[ 1873.483667] em28xx 1-1.3:1.0: Closing input extension
[ 1873.486843] em28xx 1-1.3:1.0: Freeing device
[ 1875.734726] usb 1-1.2: USB disconnect, device number 4
[ 1876.367563] usb 1-1.1.2: new low-speed USB device number 8 using dwc_otg
[ 1876.489781] usb 1-1.1.2: New USB device found, idVendor=413c, idProduct=2113, bcdDevice= 1.08
[ 1876.489811] usb 1-1.1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 1876.489820] usb 1-1.1.2: Product: Dell KB216 Wired Keyboard
[ 1876.504267] input: Dell KB216 Wired Keyboard as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0/0003:413C:2113.0007/input/input8
[ 1876.564960] hid-generic 0003:413C:2113.0007: input,hidraw0: USB HID v1.11 Keyboard [Dell KB216 Wired Keyboard] on usb-3f980000.usb-1.1.2/input0
[ 1876.582118] input: Dell KB216 Wired Keyboard System Control as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.1/0003:413C:2113.0008/input/input9
[ 1876.641215] input: Dell KB216 Wired Keyboard Consumer Control as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.1/0003:413C:2113.0008/input/input10
[ 1876.641539] hid-generic 0003:413C:2113.0008: input,hidraw1: USB HID v1.11 Device [Dell KB216 Wired Keyboard] on usb-3f980000.usb-1.1.2/input1
[ 1878.300921] usb 1-1.3: new high-speed USB device number 9 using dwc_otg
[ 1878.398031] usb 1-1.3: New USB device found, idVendor=0ccd, idProduct=10b2, bcdDevice= 1.00
[ 1878.398061] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1878.398070] usb 1-1.3: Product: TS Aggregator
[ 1878.398078] usb 1-1.3: Manufacturer: CINERGY TC2 Stick
[ 1878.398938] em28xx 1-1.3:1.0: New device CINERGY TC2 Stick TS Aggregator @ 480 Mbps (0ccd:10b2, interface 0, class 0)
[ 1878.398966] em28xx 1-1.3:1.0: DVB interface 0 found: bulk
[ 1878.454390] em28xx 1-1.3:1.0: unknown em28xx chip ID (0)
[ 1878.514818] em28xx 1-1.3:1.0: reading from i2c device at 0xa0 failed (error=-5)
[ 1878.514851] em28xx 1-1.3:1.0: board has no eeprom
[ 1878.570921] em28xx 1-1.3:1.0: Identified as Terratec Cinergy H6 rev. 2 (card=101)
[ 1878.570953] em28xx 1-1.3:1.0: dvb set to bulk mode.
[ 1878.571060] em28xx 1-1.3:1.0: Binding DVB extension
[ 1878.607950] em28xx 1-1.3:1.0: writing to i2c device at 0x82 failed (error=-5)
[ 1878.608169] em28xx 1-1.3:1.0: writing to i2c device at 0x82 failed (error=-5)
[ 1878.608376] em28xx 1-1.3:1.0: writing to i2c device at 0x82 failed (error=-5)
[ 1878.608572] em28xx 1-1.3:1.0: writing to i2c device at 0x82 failed (error=-5)
[ 1878.608781] em28xx 1-1.3:1.0: writing to i2c device at 0x82 failed (error=-5)
[ 1878.620484] em28xx 1-1.3:1.0: reading from i2c device at 0x52 failed (error=-5)
[ 1878.620701] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1878.620712] drxk: i2c write error at addr 0x29
[ 1878.631956] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1878.631985] drxk: i2c write error at addr 0x29
[ 1878.643223] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1878.643246] drxk: i2c write error at addr 0x29
[ 1878.654511] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1878.654539] drxk: i2c write error at addr 0x29
[ 1878.665798] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1878.665817] drxk: i2c write error at addr 0x29
[ 1878.676541] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1878.676567] drxk: i2c write error at addr 0x29
[ 1878.687810] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1878.687842] drxk: i2c write error at addr 0x29
[ 1878.699095] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1878.699118] drxk: i2c write error at addr 0x29
[ 1878.710366] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1878.710388] drxk: i2c write error at addr 0x29
[ 1878.721651] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1878.721674] drxk: i2c write error at addr 0x29
[ 1878.732917] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1878.732941] drxk: i2c write error at addr 0x29
[ 1878.744180] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1878.744220] drxk: i2c write error at addr 0x29
[ 1878.755455] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1878.755482] drxk: i2c write error at addr 0x29
[ 1878.766724] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1878.766748] drxk: i2c write error at addr 0x29
[ 1878.777833] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1878.777857] drxk: i2c write error at addr 0x29
[ 1878.789106] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1878.789129] drxk: i2c write error at addr 0x29
[ 1878.800391] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1878.800413] drxk: i2c write error at addr 0x29
[ 1878.811114] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1878.811137] drxk: i2c write error at addr 0x29
[ 1878.822457] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1878.822508] drxk: i2c write error at addr 0x29
[ 1878.833819] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5)
[ 1878.833851] drxk: i2c write error at addr 0x29
[ 1878.844246] drxk: Error -5 on power_up_device
[ 1878.844271] drxk: Error -5 on init_drxk
[ 1878.844284] drxk: frontend initialized.
[ 1878.844312] tda18271 12-0060: creating new instance
[ 1878.844574] em28xx 1-1.3:1.0: writing to i2c device at 0xc0 failed (error=-5)
[ 1878.844593] tda18271_read_regs: [12-0060|M] ERROR: i2c_transfer returned: -5
[ 1878.844621] tda18271: Error reading device ID @ 12-0060, bailing out.
[ 1878.844633] tda18271_attach: [12-0060|M] error -5 on line 1271
[ 1878.844651] tda18271 12-0060: destroying instance
[ 1878.844859] em28xx 1-1.3:1.0: Registering input extension

Display More

electrolurch · October 22, 2023 at 9:16 PM

idVendor=0ccd, idProduct=10b2 ,same id for different chipset !!

add module_blacklist=em28xx to extlinux.conf,then correct driver load

oJPTo · October 23, 2023 at 10:25 AM

Thanks, that did the job. I put it into

/storage/.config/modprobe.d/blacklist.conf

oJPTo · October 23, 2023 at 12:31 PM

Still does not work.

Where do I put the firmware? Looks like it did not find the firmware in

/storage/.config/firmware/

dmesg says

kernel-overlays-setup: added firmware from /storage/.config/firmware

Code

usb 1-1.3: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)...
dvbdev: dvb_create_media_entity: media entity 'Silicon Labs Si2168' registered.
si2157 12-0063: Silicon Labs Si2157 successfully attached
si2168 11-0067: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
si2168 11-0067: firmware download failed -22
si2157 12-0063: device is buggy, skipping firmware download
usb 1-1.3: dvb_usb_v2: 'TerraTec Cinergy TC2 Stick' successfully initialized and connected
usbcore: registered new interface driver dvb_usb_af9035
si2157 12-0063: firmware version: 3.0.5
usb 1-1.3: DVB: adapter 0 frontend 0 frequency 0 out of range (48000000..870000000)
si2168 11-0067: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
si2168 11-0067: firmware download failed -22
si2168 11-0067: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
si2168 11-0067: firmware download failed -22

Display More

petediscrete · October 23, 2023 at 12:46 PM

https://wiki.libreelec.tv/how-to/add-firmware#

oJPTo · October 23, 2023 at 1:01 PM

thanks, this is the guide i followed.

on the PC it does not need sub directories.

and in the log it does not use sub directories as well.

so if I should place it into a sub dir, what dir do you suggest?

or is there anything else I was wrong about?

petediscrete · October 23, 2023 at 1:26 PM

This link will give you the current situation with your USB stick https://wiki.archlinux.org/title/TerraTec…_MKII_USB_Stick

The perceived wisdom here is that you setup a separate server on another RPI using RPIOS and have it feed your LE client.

oJPTo · October 23, 2023 at 2:57 PM

This is a completely different device.

but that was the plan already in the first place.

Trying different platforms to make it work.

My backup laptop broke down yesterday while tring to build 6.5 kernel.

Got another spare PC now for experimenting.

ps: seems like one of the firmware files was bad. replaced it and now I get the "buggy device" messages again. So same state as on the PC.

see http://ix.io/4JKR

next try is compiling 6.5 kernel

but maybe I should give up trying on libreelec for now. Will mark the thread as "given up".

thanks to all people who tried to help.

petediscrete · October 23, 2023 at 3:28 PM

The biggest problem using DVB devices on LE directly is breakage on every kernel update. And that’s if you’re lucky enough to get the device working in the first place. That’s why I suggested using a separate RPI with the USB attached acting as a server, pin the kernel version on the server and you can do what you like with the LE client without worrying about breaking your server install.

Many of those USB sticks are hit and miss in Linux and many don’t even work no matter what firmware you throw at them. Again you can see from this list that your stick might be supported http://www.linux-hardware-guide.de/2012-11-02-ter…tc-usb-stick-hd

electrolurch · October 23, 2023 at 5:02 PM

ignore "device is buggy" ,firmware version: ÿ.ÿ.255 is the firm on eprom inside the stick and works. test it in tvheadend!

oJPTo · October 25, 2023 at 1:10 PM

Yeah, thanks. The device actually works. Problem was I didn't know the exact symbol rates.

There are a ton of sources for firmware, not all identical, some broken.

I made it work with these

Code

$ md5sum *
d8da7ff67cd56cd8aa4e101aea45e052  dvb-demod-si2168-02.fw
c8e089c351e9834060e962356f8697b8 dvb-demod-si2168-b40-01.fw
0c3f6bc5028bc37cfbf3a16d480bbaa5  dvb-usb-it9303-01.fw
9822ca23d24c46569ede9e07b1f13eee  dvb-usb-terratec-htc-stick-drxk.fw

petediscrete · October 25, 2023 at 2:41 PM

Quote from oJPTo
Yeah, thanks. The device actually works. Problem was I didn't know the exact symbol rates.
There are a ton of sources for firmware, not all identical, some broken.
I made it work with these
Code
$ md5sum *
d8da7ff67cd56cd8aa4e101aea45e052  dvb-demod-si2168-02.fw
d643a75d2ced161bc5fb635aec694d9f  dvb-demod-si2168-b40-01.fw
0c3f6bc5028bc37cfbf3a16d480bbaa5  dvb-usb-it9303-01.fw
9822ca23d24c46569ede9e07b1f13eee  dvb-usb-terratec-htc-stick-drxk.fw

When you say you made it work with these, was that in LE or something else. The big problem is the different revisions of this stick. It is usually down to the Vendor ID reported not matching the actual installed on the chip.

Could you supply a little more detail on the cable service you are using and maybe someone here could supply you with the relevant S/R.

oJPTo · October 26, 2023 at 6:03 PM

It works in LibreElec and on PC/Ubuntu.

But on LibreElec 11 the USB stick does not come up on boot-up. I have to remove and re-insert it.

There should be a simple solution, but I don't know it

I think this is triggered bei udev?

dmesg log of bootup is here:

http://ix.io/4K1e

dmesg log of remove and reinsert USB device is here:

http://ix.io/4K1d

My provider is Synvia. They deliver FTTH (fiber internet). In my flat they mounted a converter from fiber to cable and LAN. No idea what it does.

The symbol rate seems to be 6,900,000 for all muxes.

one of the above was wrong. good one is

c8e089c351e9834060e962356f8697b8 dvb-demod-si2168-b40-01.fw

(fixed it in my post, but couldn't in your quote)

not sure if the vendor id really makes trouble. the stick works fine, even if I do not blacklist the other driver and it is loaded.

thanks.

petediscrete · October 26, 2023 at 6:42 PM

So when you say “works in LibreElec and on PC/Ubuntu.“ can you successfully scan muxes and view them. What version of LibreELEC does it work in.

I’ve a feeling the lack of supported drivers in LE 11 on your RPI3 is the problem.

oJPTo · October 26, 2023 at 6:57 PM

Yes, everything works fine now on LE11

I can try LE 12 tomorrow if the driver is loaded at boot-up.

oJPTo · October 27, 2023 at 9:52 AM

Same on LE12. LibreELEC 6.1.58, nightly build of 23th october.

You have to re-insert the usb device after every boot, else it won't work.

Boot-up log

http://ix.io/4JnM

reinsert log

http://ix.io/4Jo2

any idea?

petediscrete · October 27, 2023 at 10:53 AM

Run dmesg after boot. Then unplug the stick run it again. Finally plug it in and again run dmesg. Just post the relevant section of dmesg that relates to the stick.

frakkin64 · October 27, 2023 at 12:15 PM

Quote from oJPTo

You have to re-insert the usb device after every boot, else it won't work.

I don't know if this still works, and what the PSU requirements are.

RPi 3: USB not enumerating during boot, fine on hotplug - Raspberry Pi Forums

But in essence your issue:

Code

[   14.777058] usb 1-1.1.2: dvb_usb_v2: 2nd usb_bulk_msg() failed=-110
[   14.777103] dvb_usb_af9035: probe of 1-1.1.2:1.0 failed with error -110

Appears to be kernel/bootloader related, nothing to do with LE. Earlier on you can see it enumerating the device, it just later on fails with this. You might want to try logging an issue on https://github.com/raspberrypi/linux and see what they have to say, the forum post suggests it doesn't do anything (would have to check config.txt documentation to see, it might be for RPi2 and earlier)

More info on max_usb_current, seems applicable to 3B+?

B+ and max_usb_current - Raspberry Pi Forums