PCTV Triplestick and Raspberry Pi B+

PCTV Triplestick and Raspberry Pi B+

[Peter Fassberg]

Hi all!

I'm trying to get PCTV TripleStick 292e working in a Raspberry Pi B+ environment.

I have no problem getting DVB-T to work, but I can't tune to any DVB-T2 channels. I have tried with three different kernels: 3.18.11, 3.18.16 and 4.0.6.  Same problem.  I also cloned the media_build under 4.0.6 to no avail.

The same physical stick works perfectly with DVB-T2 in an Intel platform using kernel 3.16.0.

Do you have any suggestions what I can do to get this running or is there a known problem with Raspberry/ARM?



Best regards,

Peter Fassberg
Sweden

----------

>From dmesg:


Working Debian:
Linux debian-usb 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1 (2015-05-24) x86_64 GNU/Linux

[   10.148481] media: Linux media interface: v0.10
[   10.154268] Linux video capture interface: v2.00
[  549.805030] usb 2-2: new high-speed USB device number 8 using xhci_hcd
[  549.933927] usb 2-2: New USB device found, idVendor=2013, idProduct=025f
[  549.933931] usb 2-2: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[  549.933933] usb 2-2: Product: PCTV 292e
[  549.933935] usb 2-2: Manufacturer: PCTV
[  549.933936] usb 2-2: SerialNumber: 0011477026
[  550.955796] em28xx: New device PCTV PCTV 292e @ 480 Mbps (2013:025f, interface 0, class 0)
[  550.955805] em28xx: DVB interface 0 found: isoc
[  550.955875] em28xx: chip ID is em28178
[  552.918404] em28178 #0: EEPROM ID = 26 00 01 00, EEPROM hash = 0x5110ff04
[  552.918411] em28178 #0: EEPROM info:
[  552.918414] em28178 #0:      microcode start address = 0x0004, boot configuration = 0x01
[  552.925114] em28178 #0:      AC97 audio (5 sample rates)
[  552.925123] em28178 #0:      500mA max power
[  552.925128] em28178 #0:      Table at offset 0x27, strings=0x146a, 0x1888, 0x0a7e
[  552.925245] em28178 #0: Identified as PCTV tripleStick (292e) (card=94)
[  552.925250] em28178 #0: dvb set to isoc mode.
[  552.925350] usbcore: registered new interface driver em28xx
[  552.939512] em28178 #0: Binding DVB extension
[  552.947676] i2c i2c-10: Added multiplexed i2c bus 11
[  552.947683] si2168 10-0064: si2168: Silicon Labs Si2168 successfully attached
[  552.952791] si2157 11-0060: si2157: Silicon Labs Si2157 successfully attached
[  552.952803] DVB: registering new adapter (em28178 #0)
[  552.952810] usb 2-2: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)...
[  552.954155] em28178 #0: DVB extension successfully initialized
[  552.954161] em28xx: Registered (Em28xx dvb Extension) extension
[  552.960517] em28178 #0: Registering input extension
[  552.987528] Registered IR keymap rc-pinnacle-pctv-hd
[  552.987649] input: em28xx IR (em28178 #0) as /devices/pci0000:00/0000:00:14.0/usb2/2-2/rc/rc0/input26
[  552.987786] rc0: em28xx IR (em28178 #0) as /devices/pci0000:00/0000:00:14.0/usb2/2-2/rc/rc0
[  552.987904] em28178 #0: Input extension successfully initalized
[  552.987908] em28xx: Registered (Em28xx Input Extension) extension
[ 1268.446509] si2168 10-0064: si2168: found a 'Silicon Labs Si2168' in cold state
[ 1268.446564] si2168 10-0064: firmware: direct-loading firmware dvb-demod-si2168-02.fw
[ 1268.446574] si2168 10-0064: si2168: downloading firmware from file 'dvb-demod-si2168-02.fw'
[ 1268.604691] si2168 10-0064: si2168: found a 'Silicon Labs Si2168' in warm state



Non-working Raspberry:
Linux raspberrypi 4.0.6-v7+ #798 SMP PREEMPT Tue Jun 23 18:06:01 BST 2015 armv7l GNU/Linux

[    0.000000] Linux version 4.0.6-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.8.3 20140303 (prerelease) (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #798 SMP PREEMPT Tue Jun 23 18:06:01 BST 2015
[    0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine model: Raspberry Pi 2 Model B Rev 1.1
[    7.200879] media: Linux media interface: v0.10
[    7.223037] Linux video capture interface: v2.00
[    7.245815] em28xx: New device PCTV PCTV 292e @ 480 Mbps (2013:025f, interface 0, class 0)
[    7.256731] em28xx: DVB interface 0 found: isoc
[    7.262712] em28xx: chip ID is em28178
[    9.258341] em28178 #0: EEPROM ID = 26 00 01 00, EEPROM hash = 0x5110ff04
[    9.267163] em28178 #0: EEPROM info:
[    9.272644] em28178 #0:      microcode start address = 0x0004, boot configuration = 0x01
[    9.291418] em28178 #0:      AC97 audio (5 sample rates)
[    9.298231] em28178 #0:      500mA max power
[    9.303993] em28178 #0:      Table at offset 0x27, strings=0x146a, 0x1888, 0x0a7e
[    9.313288] em28178 #0: Identified as PCTV tripleStick (292e) (card=94)
[    9.321852] em28178 #0: dvb set to isoc mode.
[    9.328536] usbcore: registered new interface driver em28xx
[    9.357476] em28178 #0: Binding DVB extension
[    9.380909] i2c i2c-1: Added multiplexed i2c bus 2
[    9.389469] si2168 1-0064: Silicon Labs Si2168 successfully attached
[    9.410263] si2157 2-0060: Silicon Labs Si2147/2148/2157/2158 successfully attached
[    9.422419] DVB: registering new adapter (em28178 #0)
[    9.428929] usb 1-1.4: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)...
[    9.442954] em28178 #0: DVB extension successfully initialized
[    9.450692] em28xx: Registered (Em28xx dvb Extension) extension
[    9.482115] em28178 #0: Registering input extension
[    9.529742] Registered IR keymap rc-pinnacle-pctv-hd
[    9.538138] input: em28xx IR (em28178 #0) as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4/rc/rc0/input0
[    9.551330] rc0: em28xx IR (em28178 #0) as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4/rc/rc0
[    9.563907] em28178 #0: Input extension successfully initalized
[    9.571364] em28xx: Registered (Em28xx Input Extension) extension
[  297.703612] si2168 1-0064: found a 'Silicon Labs Si2168-B40'
[  300.998391] si2168 1-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
[  301.275434] si2168 1-0064: firmware version: 4.0.4
[  301.284625] si2157 2-0060: found a 'Silicon Labs Si2157-A30'
[  301.340643] si2157 2-0060: firmware version: 3.0.5

----------

Re: PCTV Triplestick and Raspberry Pi B+

[Andy Furniss]

Peter Fassberg wrote:
> Hi all!
>
> I'm trying to get PCTV TripleStick 292e working in a Raspberry Pi B+
>  environment.
>
> I have no problem getting DVB-T to work, but I can't tune to any
> DVB-T2 channels. I have tried with three different kernels: 3.18.11,
> 3.18.16 and 4.0.6.  Same problem.  I also cloned the media_build
> under 4.0.6 to no avail.
>
> The same physical stick works perfectly with DVB-T2 in an Intel
> platform using kernel 3.16.0.
>
> Do you have any suggestions what I can do to get this running or is
> there a known problem with Raspberry/ARM?

What are you trying to tune with?

Maybe that could be the difference - unlike the 290 the 292e won't tune
with apps that are not dvb-t2 "aware" eg. dvbv5-zap will work but not tzap.

The current version of w_scan and eg. tvheadend will work, but older
versions may not.

Re: PCTV Triplestick and Raspberry Pi B+

[Peter Fassberg]

>> I'm trying to get PCTV TripleStick 292e working in a Raspberry Pi B+
>>  environment.
>> 
>> I have no problem getting DVB-T to work, but I can't tune to any
>> DVB-T2 channels. I have tried with three different kernels: 3.18.11,
>> 3.18.16 and 4.0.6.  Same problem.  I also cloned the media_build
>> under 4.0.6 to no avail.
>> 
>> The same physical stick works perfectly with DVB-T2 in an Intel
>> platform using kernel 3.16.0.
>> 
>> Do you have any suggestions what I can do to get this running or is
>> there a known problem with Raspberry/ARM?
>
> What are you trying to tune with?

I'm using dvbv5-scan.

I use the same program on the system that works.

The output for a DVB-T mux:
Lock   (0x1f) Signal= -42.00dBm C/N= 20.25dB

And a DVB-T2:
Carrier(0x03) Signal= -35.00dBm

There is a difference between Raspberry/ARM and Intel that I don't understand.



Regards,

Peter

Re: PCTV Triplestick and Raspberry Pi B+

[Andy Furniss]

Peter Fassberg wrote:
>
>>> I'm trying to get PCTV TripleStick 292e working in a Raspberry Pi
>>> B+ environment.
>>>
>>> I have no problem getting DVB-T to work, but I can't tune to any
>>> DVB-T2 channels. I have tried with three different kernels:
>>> 3.18.11, 3.18.16 and 4.0.6.  Same problem.  I also cloned the
>>> media_build under 4.0.6 to no avail.
>>>
>>> The same physical stick works perfectly with DVB-T2 in an Intel
>>> platform using kernel 3.16.0.
>>>
>>> Do you have any suggestions what I can do to get this running or
>>> is there a known problem with Raspberry/ARM?
>>
>> What are you trying to tune with?
>
> I'm using dvbv5-scan.
>
> I use the same program on the system that works.
>
> The output for a DVB-T mux: Lock   (0x1f) Signal= -42.00dBm C/N=
> 20.25dB
>
> And a DVB-T2: Carrier(0x03) Signal= -35.00dBm
>
> There is a difference between Raspberry/ARM and Intel that I don't
> understand.

Hmm, not sure then - maybe try md5sum on the firmware that dmesg shows
loading on each then if different backup/copy over etc.

I am just a user so don't know what's different between 3.16 and later.

One thing I noticed at one point when setting mine up was (after
unknowingly breaking a splitter) that with the degraded splitter I could
get working/not on some T2 muxed by flipping the lna on off with the
option available with dvbv5-*.

Re: PCTV Triplestick and Raspberry Pi B+

[Peter Fassberg]

> Peter Fassberg wrote:
>> 
>>>> I'm trying to get PCTV TripleStick 292e working in a Raspberry Pi
>>>> B+ environment.
>>>> 
>>>> I have no problem getting DVB-T to work, but I can't tune to any
>>>> DVB-T2 channels. I have tried with three different kernels:
>>>> 3.18.11, 3.18.16 and 4.0.6.  Same problem.  I also cloned the
>>>> media_build under 4.0.6 to no avail.
>>>> 
>>>> The same physical stick works perfectly with DVB-T2 in an Intel
>>>> platform using kernel 3.16.0.
>>>> 
>>>> Do you have any suggestions what I can do to get this running or
>>>> is there a known problem with Raspberry/ARM?
>>> 
>>> What are you trying to tune with?
>> 
>> I'm using dvbv5-scan.
>> 
>> I use the same program on the system that works.
>> 
>> The output for a DVB-T mux: Lock   (0x1f) Signal= -42.00dBm C/N=
>> 20.25dB
>> 
>> And a DVB-T2: Carrier(0x03) Signal= -35.00dBm
>> 
>> There is a difference between Raspberry/ARM and Intel that I don't
>> understand.
>
> Hmm, not sure then - maybe try md5sum on the firmware that dmesg shows
> loading on each then if different backup/copy over etc.
>
> I am just a user so don't know what's different between 3.16 and later.
>
> One thing I noticed at one point when setting mine up was (after
> unknowingly breaking a splitter) that with the degraded splitter I could
> get working/not on some T2 muxed by flipping the lna on off with the
> option available with dvbv5-*.

Yes, I also tested that.  The firmware is identical and the LNA as well.

It do work 100% of the times I scan on the Intel platform.



// Peter

Re: PCTV Triplestick and Raspberry Pi B+

[Andy Furniss]

Peter Fassberg wrote:
>
>> Peter Fassberg wrote:
>>>
>>>>> I'm trying to get PCTV TripleStick 292e working in a
>>>>> Raspberry Pi B+ environment.
>>>>>
>>>>> I have no problem getting DVB-T to work, but I can't tune to
>>>>> any DVB-T2 channels. I have tried with three different
>>>>> kernels: 3.18.11, 3.18.16 and 4.0.6.  Same problem.  I also
>>>>> cloned the media_build under 4.0.6 to no avail.
>>>>>
>>>>> The same physical stick works perfectly with DVB-T2 in an
>>>>> Intel platform using kernel 3.16.0.
>>>>>
>>>>> Do you have any suggestions what I can do to get this running
>>>>> or is there a known problem with Raspberry/ARM?
>>>>
>>>> What are you trying to tune with?
>>>
>>> I'm using dvbv5-scan.
>>>
>>> I use the same program on the system that works.
>>>
>>> The output for a DVB-T mux: Lock   (0x1f) Signal= -42.00dBm C/N=
>>> 20.25dB
>>>
>>> And a DVB-T2: Carrier(0x03) Signal= -35.00dBm
>>>
>>> There is a difference between Raspberry/ARM and Intel that I
>>> don't understand.
>>
>> Hmm, not sure then - maybe try md5sum on the firmware that dmesg
>> shows loading on each then if different backup/copy over etc.
>>
>> I am just a user so don't know what's different between 3.16 and
>> later.
>>
>> One thing I noticed at one point when setting mine up was (after
>> unknowingly breaking a splitter) that with the degraded splitter I
>> could get working/not on some T2 muxed by flipping the lna on off
>> with the option available with dvbv5-*.
>
> Yes, I also tested that.  The firmware is identical and the LNA as
> well.
>
> It do work 100% of the times I scan on the Intel platform.

OK - strange, is the issue reproducable with the current version of w_scan?

Re: PCTV Triplestick and Raspberry Pi B+

[Peter Fassberg]

> Peter Fassberg wrote:
>> 
>>> Peter Fassberg wrote:
>>>> 
>>>>>> I'm trying to get PCTV TripleStick 292e working in a
>>>>>> Raspberry Pi B+ environment.
>>>>>> 
>>>>>> I have no problem getting DVB-T to work, but I can't tune to
>>>>>> any DVB-T2 channels. I have tried with three different
>>>>>> kernels: 3.18.11, 3.18.16 and 4.0.6.  Same problem.  I also
>>>>>> cloned the media_build under 4.0.6 to no avail.
>>>>>> 
>>>>>> The same physical stick works perfectly with DVB-T2 in an
>>>>>> Intel platform using kernel 3.16.0.

> OK - strange, is the issue reproducable with the current version of w_scan?

Yes, it is.

I used the latest I could find: w_scan version 20141122 (compiled for DVB API 5.10)

Excerpt from scanning:

198500: (time: 02:02.219)
205500: (time: 02:04.269)
         (0.250sec): SC (0x3)
         (0.250sec) signal
         (0.920sec):  (0x0)
         (1.180sec): SC (0x3)
         (1.840sec):  (0x0)
         (2.100sec): SC (0x3)
         (2.760sec):  (0x0)
         (3.020sec): SC (0x3)
         (3.680sec):  (0x0)
         (3.940sec): SC (0x3)
212500: (time: 02:08.619)

As you can see it do find Signal and Carrier, but no Lock.  Without debug (-v) it doesn't show anything.



// Peter

Re: PCTV Triplestick and Raspberry Pi B+

[Andy Furniss]

Peter Fassberg wrote:

>> OK - strange, is the issue reproducable with the current version of
>>  w_scan?
>
> Yes, it is.

Clutching at straws now, but maybe it's possible that the Pi is
electrically more noisy then the intel.

The USB lead on the 292e doesn't have a ferrite core - maybe if you have
an extension lead that does you could try adding that.

Re: PCTV Triplestick and Raspberry Pi B+

[Patrick Boettcher]

Hi,

On Sat, 4 Jul 2015 13:07:17 +0200 (SST)
Peter Fassberg <pf@leissner.se> wrote:

> Hi all!
> 
> I'm trying to get PCTV TripleStick 292e working in a Raspberry Pi B+
> environment.
> 
> I have no problem getting DVB-T to work, but I can't tune to any
> DVB-T2 channels. I have tried with three different kernels: 3.18.11,
> 3.18.16 and 4.0.6.  Same problem.  I also cloned the media_build
> under 4.0.6 to no avail.
> 
> The same physical stick works perfectly with DVB-T2 in an Intel
> platform using kernel 3.16.0.

Your Intel platform is 64bit. I don't know the TripleStick nor the SI or
the EM28xx-driver but _maybe_ there is a problem with it on 32-bit
platforms. A long shot, I know, but you'll never know.

--
Patrick.

Re: PCTV Triplestick and Raspberry Pi B+

[Peter Fassberg]

On Sun, 5 Jul 2015, Patrick Boettcher wrote:

> Your Intel platform is 64bit. I don't know the TripleStick nor the SI or
> the EM28xx-driver but _maybe_ there is a problem with it on 32-bit
> platforms. A long shot, I know, but you'll never know.

That was a very good point.

I installed the 32-bit version of the same OS (Debian 8, kernel 3.16.0, i386) and the result was a bit suprising.

In 32-bit I couldn't even scan a DVT-T transponder!  dvbv5-scan did Lock, but it didn't find any PSI PIDs.  So there is for sure a problem with 32-bit platforms.  And the DVT-T2 transponders didn't work either.

Maybe the Raspberry problem can be a Endianess problem?



On Mon, 6 Jul 2015, Andy Furniss wrote:

> Clutching at straws now, but maybe it's possible that the Pi is electrically more noisy then the intel.
> 
> The USB lead on the 292e doesn't have a ferrite core - maybe if you have an extension lead that does you could try adding that.

That was actually also a good point.  I installed a 50 cm extension but no difference. :(


Can anyone suggest a DVB-T2 USB stick that works on the Raspberry Pi B+?



// Peter

Re: PCTV Triplestick and Raspberry Pi B+

[Patrick Boettcher]

On Tue, 7 Jul 2015 17:33:01 +0200 (SST) Peter Fassberg <pf@leissner.se>
wrote:

> On Sun, 5 Jul 2015, Patrick Boettcher wrote:
> 
> > Your Intel platform is 64bit. I don't know the TripleStick nor the SI or
> > the EM28xx-driver but _maybe_ there is a problem with it on 32-bit
> > platforms. A long shot, I know, but you'll never know.
> 
> That was a very good point.
> 
> I installed the 32-bit version of the same OS (Debian 8, kernel 3.16.0, i386) and the result was a bit suprising.
> 
> In 32-bit I couldn't even scan a DVT-T transponder!  dvbv5-scan did Lock, but it didn't find any PSI PIDs.  So there is for sure a problem with 32-bit platforms.  And the DVT-T2 transponders didn't work either.
> 
> Maybe the Raspberry problem can be a Endianess problem?

No, rpi (arm) is little-endian as Intel.

Which drivers is your device using again? 

regards,
--
Patrick.

Re: PCTV Triplestick and Raspberry Pi B+

[Peter Fassberg]

On Tue, 7 Jul 2015, Patrick Boettcher wrote:

>> I installed the 32-bit version of the same OS (Debian 8, kernel 3.16.0, i386) and the result was a bit suprising.
>>
>> In 32-bit I couldn't even scan a DVT-T transponder!  dvbv5-scan did Lock, but it didn't find any PSI PIDs.  So there is for sure a problem with 32-bit platforms.  And the DVT-T2 transponders didn't work either.
>>
>> Maybe the Raspberry problem can be a Endianess problem?
>
> No, rpi (arm) is little-endian as Intel.
>
> Which drivers is your device using again?

[    7.245815] em28xx: New device PCTV PCTV 292e @ 480 Mbps (2013:025f, interface 0, class 0)
[    7.256731] em28xx: DVB interface 0 found: isoc
[    7.262712] em28xx: chip ID is em28178
[    9.258341] em28178 #0: EEPROM ID = 26 00 01 00, EEPROM hash = 0x5110ff04
[    9.267163] em28178 #0: EEPROM info:
[    9.272644] em28178 #0:      microcode start address = 0x0004, boot configuration = 0x01
[    9.291418] em28178 #0:      AC97 audio (5 sample rates)
[    9.298231] em28178 #0:      500mA max power
[    9.303993] em28178 #0:      Table at offset 0x27, strings=0x146a, 0x1888, 0x0a7e
[    9.313288] em28178 #0: Identified as PCTV tripleStick (292e) (card=94)
[    9.321852] em28178 #0: dvb set to isoc mode.
[    9.328536] usbcore: registered new interface driver em28xx
[    9.357476] em28178 #0: Binding DVB extension
[    9.380909] i2c i2c-1: Added multiplexed i2c bus 2
[    9.389469] si2168 1-0064: Silicon Labs Si2168 successfully attached
[    9.410263] si2157 2-0060: Silicon Labs Si2147/2148/2157/2158 successfully attached
[    9.422419] DVB: registering new adapter (em28178 #0)
[    9.428929] usb 1-1.4: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)...
[    9.442954] em28178 #0: DVB extension successfully initialized
[    9.450692] em28xx: Registered (Em28xx dvb Extension) extension
[    9.482115] em28178 #0: Registering input extension
[    9.563907] em28178 #0: Input extension successfully initalized
[    9.571364] em28xx: Registered (Em28xx Input Extension) extension
[  297.703612] si2168 1-0064: found a 'Silicon Labs Si2168-B40'
[  300.998391] si2168 1-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
[  301.275434] si2168 1-0064: firmware version: 4.0.4 [  301.284625] si2157 2-0060: found a 'Silicon Labs Si2157-A30'
[  301.340643] si2157 2-0060: firmware version: 3.0.5



// Peter

Re: PCTV Triplestick and Raspberry Pi B+

[Patrick Boettcher]

On Tue, 7 Jul 2015 17:38:25 +0200 (SST)
Peter Fassberg <pf@leissner.se> wrote:

> On Tue, 7 Jul 2015, Patrick Boettcher wrote:
> 
> >> I installed the 32-bit version of the same OS (Debian 8, kernel 3.16.0, i386) and the result was a bit suprising.
> >>
> >> In 32-bit I couldn't even scan a DVT-T transponder!  dvbv5-scan did Lock, but it didn't find any PSI PIDs.  So there is for sure a problem with 32-bit platforms.  And the DVT-T2 transponders didn't work either.
> >>
> >> Maybe the Raspberry problem can be a Endianess problem?
> >
> > No, rpi (arm) is little-endian as Intel.
> >
> > Which drivers is your device using again?
> 
> [    7.245815] em28xx: New device PCTV PCTV 292e @ 480 Mbps (2013:025f, interface 0, class 0)
> [    7.256731] em28xx: DVB interface 0 found: isoc
> [    7.262712] em28xx: chip ID is em28178
> [    9.258341] em28178 #0: EEPROM ID = 26 00 01 00, EEPROM hash = 0x5110ff04
> [    9.267163] em28178 #0: EEPROM info:
> [    9.272644] em28178 #0:      microcode start address = 0x0004, boot configuration = 0x01
> [    9.291418] em28178 #0:      AC97 audio (5 sample rates)
> [    9.298231] em28178 #0:      500mA max power
> [    9.303993] em28178 #0:      Table at offset 0x27, strings=0x146a, 0x1888, 0x0a7e
> [    9.313288] em28178 #0: Identified as PCTV tripleStick (292e) (card=94)
> [    9.321852] em28178 #0: dvb set to isoc mode.
> [    9.328536] usbcore: registered new interface driver em28xx
> [    9.357476] em28178 #0: Binding DVB extension
> [    9.380909] i2c i2c-1: Added multiplexed i2c bus 2
> [    9.389469] si2168 1-0064: Silicon Labs Si2168 successfully attached
> [    9.410263] si2157 2-0060: Silicon Labs Si2147/2148/2157/2158 successfully attached
> [    9.422419] DVB: registering new adapter (em28178 #0)
> [    9.428929] usb 1-1.4: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)...
> [    9.442954] em28178 #0: DVB extension successfully initialized
> [    9.450692] em28xx: Registered (Em28xx dvb Extension) extension
> [    9.482115] em28178 #0: Registering input extension
> [    9.563907] em28178 #0: Input extension successfully initalized
> [    9.571364] em28xx: Registered (Em28xx Input Extension) extension
> [  297.703612] si2168 1-0064: found a 'Silicon Labs Si2168-B40'
> [  300.998391] si2168 1-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
> [  301.275434] si2168 1-0064: firmware version: 4.0.4 [  301.284625] si2157 2-0060: found a 'Silicon Labs Si2157-A30'
> [  301.340643] si2157 2-0060: firmware version: 3.0.5

Just reading quickly the changes made to the si2157 and si2168 driver
since 3.16 up to 4.1 makes me think that it is worth a try. 

Plenty of things have changed regarding buffers and memcpy. Though I
haven't found (yet) a 64bit and 32bit mix up yet in the 3.16 version.

Might be the RF frequency that is truncated on 32bit platforms
somewhere. That could explain that there is no crash but simply not
tuning.

Can you easily try more recent kernels or media_trees?
--
Patrick.

Re: PCTV Triplestick and Raspberry Pi B+

[Patrick Boettcher]

On Tue, 7 Jul 2015 18:25:41 +0200
Patrick Boettcher <patrick.boettcher@posteo.de> wrote:

> > [  301.275434] si2168 1-0064: firmware version: 4.0.4 [  301.284625] si2157 2-0060: found a 'Silicon Labs Si2157-A30'
> > [  301.340643] si2157 2-0060: firmware version: 3.0.5

> Can you easily try more recent kernels or media_trees?

It seems you are already using a more recent version of the
si21xx-drivers than provided with 3.16. (in 3.16.0 there is no firmware
version-print in si2157)

--
Patrick.

Re: PCTV Triplestick and Raspberry Pi B+

[Peter Fassberg]

> Patrick Boettcher <patrick.boettcher@posteo.de> wrote:
>
>>> [  301.275434] si2168 1-0064: firmware version: 4.0.4 [  301.284625] si2157 2-0060: found a 'Silicon Labs Si2157-A30'
>>> [  301.340643] si2157 2-0060: firmware version: 3.0.5
>
>> Can you easily try more recent kernels or media_trees?
>
> It seems you are already using a more recent version of the
> si21xx-drivers than provided with 3.16. (in 3.16.0 there is no firmware
> version-print in si2157)

Yes, I did an upgrade to the latest I could find before I gave up.

This is in use:

root@raspberrypi:~# uname -a
Linux raspberrypi 4.0.6-v7+ #798 SMP PREEMPT Tue Jun 23 18:06:01 BST 2015 armv7l GNU/Linux

root@raspberrypi:~# modinfo si2157
filename:       /lib/modules/4.0.6-v7+/kernel/drivers/media/tuners/si2157.ko
firmware:       dvb-tuner-si2158-a20-01.fw
author:         Antti Palosaari <crope@iki.fi>
description:    Silicon Labs Si2146/2147/2148/2157/2158 silicon tuner driver
srcversion:     397E31D773FD172EA0CE7F6

root@raspberrypi:~# modinfo si2168
filename:       /lib/modules/4.0.6-v7+/kernel/drivers/media/dvb-frontends/si2168.ko
firmware:       dvb-demod-si2168-b40-01.fw
firmware:       dvb-demod-si2168-a30-01.fw
firmware:       dvb-demod-si2168-a20-01.fw
description:    Silicon Labs Si2168 DVB-T/T2/C demodulator driver
author:         Antti Palosaari <crope@iki.fi>
srcversion:     12127041CAEFE39931DE3A1

root@raspberrypi:~# modinfo em28xx
filename:       /lib/modules/4.0.6-v7+/kernel/drivers/media/usb/em28xx/em28xx.ko
version:        0.2.1
description:    Empia em28xx device driver
author:         Ludovico Cavedon <cavedon@sssup.it>, Markus Rechberger <mrechberger@gmail.com>, Mauro Carvalho Chehab <mchehab@infradead.org>, Sascha Sommer <saschasommer@freenet.de>
srcversion:     1E6C5892B8BEB1E429BECC7
vermagic:       4.0.6-v7 SMP preempt mod_unload modversions ARMv7
parm:           tuner:tuner type (int)
parm:           disable_ir:disable infrared remote support (int)
parm:           disable_usb_speed_check:override min bandwidth requirement of 480M bps (int)
parm:           card:card type (array of int)
parm:           usb_xfer_mode:USB transfer mode for frame data (-1 = auto, 0 = prefer isoc, 1 = prefer bulk) (int)
parm:           i2c_scan:scan i2c bus at insmod time (int)
parm:           i2c_debug:i2c debug message level (1: normal debug, 2: show I2C transfers) (int)
parm:           core_debug:enable debug messages [core] (int)
parm:           reg_debug:enable debug messages [URB reg] (int)

root@raspberrypi:~# modinfo em28xx_dvb
filename:       /lib/modules/4.0.6-v7+/kernel/drivers/media/usb/em28xx/em28xx-dvb.ko
version:        0.2.1
description:    Empia em28xx device driver - digital TV interface
author:         Mauro Carvalho Chehab <mchehab@infradead.org>
srcversion:     60267D5DE16B950E37CD3FF
vermagic:       4.0.6-v7 SMP preempt mod_unload modversions ARMv7
parm:           debug:enable debug messages [dvb] (int)
parm:           adapter_nr:DVB adapter numbers (array of short)

root@raspberrypi:~# modinfo em28xx_rc
filename:       /lib/modules/4.0.6-v7+/kernel/drivers/media/usb/em28xx/em28xx-rc.ko
version:        0.2.1
description:    Empia em28xx device driver - input interface
author:         Mauro Carvalho Chehab
srcversion:     C0534469E29D3F7AEB3353A
depends:        em28xx,rc-core
vermagic:       4.0.6-v7 SMP preempt mod_unload modversions ARMv7
parm:           ir_debug:enable debug messages [IR] (int)

Re: PCTV Triplestick and Raspberry Pi B+

[Peter Fassberg]

On Tue, 7 Jul 2015, Patrick Boettcher wrote:

> Might be the RF frequency that is truncated on 32bit platforms
> somewhere. That could explain that there is no crash but simply not
> tuning.

This is the current status:

ARM 32-bit, kernel 4.0.6, updated media_tree: Works with DVB-T, no lock on DVB-T2.

Intel 32-bit, kernel 3.16.0, standard media_tree: Locks, but no PSIs detected.

Intel 64-bit, kernel 3.16.0, standard media_tree: Works like a charm.


So I don't think that en RF freq is truncated.



-- Peter

Re: PCTV Triplestick and Raspberry Pi B+

[Patrick Boettcher]

On Tue, 7 Jul 2015 18:51:16 +0200 (SST) Peter Fassberg <pf@leissner.se>
wrote:

> On Tue, 7 Jul 2015, Patrick Boettcher wrote:
> 
> > Might be the RF frequency that is truncated on 32bit platforms
> > somewhere. That could explain that there is no crash but simply not
> > tuning.
> 
> This is the current status:
> 
> ARM 32-bit, kernel 4.0.6, updated media_tree: Works with DVB-T, no lock on DVB-T2.
> 
> Intel 32-bit, kernel 3.16.0, standard media_tree: Locks, but no PSIs detected.
> 
> Intel 64-bit, kernel 3.16.0, standard media_tree: Works like a charm.
> 
> 
> So I don't think that en RF freq is truncated.

Yes, it was an assumption - not a right one as it turned out. I didn't
find any obvious 32/64-problem in the si*-drivers you are using.

I'm too afraid to look into the em*-drivers and I doubt that there is
any obvious 32/64-bit-problem.

If I were you, I would try to compare the usb-traffic (using
usbmon with wireshark) between a working tune on one frequency with one
standard on each of the 3 scenarios (maybe starting with the intel 32
and 64 platform).

For example

on each platform:

1) start wireshark-capture on the right USB-port,
2) plug the device, 
3) tune (tzap) a valid DVB-T frequency
4) stop capturing

Then compare the traffic log. Most outgoing data should be
identical. Incoming data (except monitoring values and TS) should be
equal as well.

If you see differences in data-buffer-sizes or during the
firmware-download-phase or anywhere else, we can try to find the code
which corresponds and place debug messages. You are lucky, your drivers
are using embedded firmwares which simplifies the communication between
the driver and the device.

regards,
--
Patrick.

Re: PCTV Triplestick and Raspberry Pi B+

[Olli Salonen]

Patrick has suggested many things here worth trying. In addition, you
can load the modules with more debugging enabled:

unload the modules first
modprobe si2168 dyndbg==pmf
modprobe si2157 dyndbg==pmf
modprobe em28xx debug=1

If you are willing to try, TechnoTrend CT2-4400 has the same si2168
and si2157 chips, but instead of the EM28xx it uses another USB
bridge. There are at least a few reports of people having a working
CT2-4400 with RPi2 here:
http://openelec.tv/forum/71-pvr-live-tv/72071-experimental-support-for-tt-ct2-4400-dvb-t2-c?start=30

Furthermore, kernel 3.16 was the first one to support the TripleStick
and the Si2168/si2157 chips. The drivers for those SiLabs devices have
improved quite significantly since that. Also, be extra careful with
the firmwares - I remember there was something different in the way
kernel 3.16 handled the Si2168 firmware compared to anything newer
than that. If you could try to upgrade the intel devices to 3.17 at
least (or with the latest media-build), download the firmware from
http://palosaari.fi/linux/v4l-dvb/firmware/Si2168/Si2168-B40/4.0.11/
and place it in /lib/firmware and then redo your test, it would be
helpful.

Cheers,
-olli


On 8 July 2015 at 09:33, Patrick Boettcher <patrick.boettcher@posteo.de> wrote:
> On Tue, 7 Jul 2015 18:51:16 +0200 (SST) Peter Fassberg <pf@leissner.se>
> wrote:
>
>> On Tue, 7 Jul 2015, Patrick Boettcher wrote:
>>
>> > Might be the RF frequency that is truncated on 32bit platforms
>> > somewhere. That could explain that there is no crash but simply not
>> > tuning.
>>
>> This is the current status:
>>
>> ARM 32-bit, kernel 4.0.6, updated media_tree: Works with DVB-T, no lock on DVB-T2.
>>
>> Intel 32-bit, kernel 3.16.0, standard media_tree: Locks, but no PSIs detected.
>>
>> Intel 64-bit, kernel 3.16.0, standard media_tree: Works like a charm.
>>
>>
>> So I don't think that en RF freq is truncated.
>
> Yes, it was an assumption - not a right one as it turned out. I didn't
> find any obvious 32/64-problem in the si*-drivers you are using.
>
> I'm too afraid to look into the em*-drivers and I doubt that there is
> any obvious 32/64-bit-problem.
>
> If I were you, I would try to compare the usb-traffic (using
> usbmon with wireshark) between a working tune on one frequency with one
> standard on each of the 3 scenarios (maybe starting with the intel 32
> and 64 platform).
>
> For example
>
> on each platform:
>
> 1) start wireshark-capture on the right USB-port,
> 2) plug the device,
> 3) tune (tzap) a valid DVB-T frequency
> 4) stop capturing
>
> Then compare the traffic log. Most outgoing data should be
> identical. Incoming data (except monitoring values and TS) should be
> equal as well.
>
> If you see differences in data-buffer-sizes or during the
> firmware-download-phase or anywhere else, we can try to find the code
> which corresponds and place debug messages. You are lucky, your drivers
> are using embedded firmwares which simplifies the communication between
> the driver and the device.
>
> regards,
> --
> Patrick.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html