

Azrael
-
Posts
4 -
Joined
-
Last visited
Reputation Activity
-
Azrael reacted to papasmurfster in Cubieboard3 / Cubietruck experience (I2C MUX, si2168 DVB-C)
Well I got round to building the new Image last night.
All I can say is thank you.
The kernel so far at least is working perfect. its found all 4 devices
PCTV 461
PCTV 292e PCTV 290e DVbSky 960 I used the following firmware commands sudo wget https://github.com/OpenELEC/dvb-firmware/blob/master/firmware/dvb-demod-si2168-02.fw?raw=true-O /lib/firmware/dvb-demod-si2168-02.fw sudo wget https://github.com/OpenELEC/dvb-firmware/blob/master/firmware/dvb-demod-si2168-b40-01.fw?raw=true-O /lib/firmware/dvb-demod-si2168-b40-01.fw sudo wget https://github.com/OpenELEC/dvb-firmware/blob/master/firmware/dvb-demod-m88ds3103.fw?raw=true-O /lib/firmware/dvb-demod-m88ds3103.fw I'll try and post some more details on the results after I've tried it for a week or 2. Thanks again -
Azrael reacted to sschöne in Cubieboard3 / Cubietruck experience (I2C MUX, si2168 DVB-C)
I installed the working image from papasmurfster and downloaded the firmware to /lib/firmware
dmesg | grep -i dvb [32967.819770] si2168 3-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw' [76506.731502] em28178 #0: Closing DVB extension [76508.984748] em28xx: DVB interface 0 found: isoc [76510.989783] em28178 #0: dvb set to isoc mode. [76510.990710] em28178 #0: Binding DVB extension [76511.175456] DVB: registering new adapter (em28178 #0) [76511.175482] usb 2-1: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)... [76511.182309] em28178 #0: DVB extension successfully initialized It seems that the firmware cannot be load. But why? What am I doing wrong? When I start w_scan -fc: w_scan version 20120605 (compiled for DVB API 5.4) WARNING: could not guess your country. Falling back to 'DE' guessing country 'DE', use -c <country> to override using settings for GERMANY DVB cable DVB-C scan type CABLE, channellist 7 output format vdr-1.6 WARNING: could not guess your codepage. Falling back to 'UTF-8' output charset 'UTF-8', use -C <charset> to override Info: using DVB adapter auto detection. /dev/dvb/adapter0/frontend0 -> CABLE "Silicon Labs Si2168": very good Using CABLE frontend (adapter /dev/dvb/adapter0/frontend0) _ _ Getting frontend capabilities-_ _-_ Using DVB API 5.a frontend 'Silicon Labs Si2168' supports INVERSION_AUTO QAM_AUTO FEC_AUTO FREQ 55.00MHz ... 862.00MHz SRATE 1.000MSym/s ... 7.200MSym/s 73000: sr6900 time: 00:00 sr6875 time: 00:02 after that: dmesg | grep -i dvb [32967.819770] si2168 3-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw' [76506.731502] em28178 #0: Closing DVB extension [76508.984748] em28xx: DVB interface 0 found: isoc [76510.989783] em28178 #0: dvb set to isoc mode. [76510.990710] em28178 #0: Binding DVB extension [76511.175456] DVB: registering new adapter (em28178 #0) [76511.175482] usb 2-1: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)... [76511.182309] em28178 #0: DVB extension successfully initialized [78579.659829] si2168 3-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw' Edit: It works!!! I do the following steps: 1. Start "w_scan -tc" and stop it immediately with Ctrl-C. This will set the stick in DVB-C mode and leaves it there.
Alternativesly, you can execute "dvb-fe-tool --adapter=0 --frontend=0 --set-delsys=DVBC/ANNEX_A".
2. Restart TVH with "service tvheadend restart"
3. Now go to http://<yourserver>:9981 and check that the stick is enabled and so on -
Azrael reacted to Igor in Cubieboard3 / Cubietruck experience (I2C MUX, si2168 DVB-C)
Use the branch "master", will be default in a matter of days but now you need to:
1. Edit compile.sh and change:
from: git clone --depth 1 https://github.com/igorpecovnik/lib '>https://github.com/igorpecovnik/lib to: git clone --depth 1 https://github.com/igorpecovnik/lib -b master 2. Remove lib and everything else too since sources are organized differently
3. Run compile.sh again.
Edit: we were working about a month strait to fix things and bring script to next level. There are many changes, documentation is on the way ...
-
Azrael reacted to d1dd1 in Cubieboard3 / Cubietruck experience (I2C MUX, si2168 DVB-C)
I can confim this, the Truck is rock-solid !
I use it with a SSD as Home Automation Server (Openhab, FHEM & Mosquitto), as well as little Web- & MySQL Server and since a few days also as DVB-S2 Recording / SatIP Server (TVHeadend). Still plenty resources available ;-)
With a Hub and 7 USB devices (DVB-S2 and several Home Automation Sticks / Arduinos ) connected, no problems so far.
Despite all Marketing blabla from competitiors, I have not found a comparable SBC (especially because of the SATA port, RAM and your amazing work)
Thanks !
-
Azrael got a reaction from Igor in Cubieboard3 / Cubietruck experience (I2C MUX, si2168 DVB-C)
Looks like this Thread became a good source of information for i2c_mux, si2168 and em28xx problems - even google lists it as first link when searching for cubietruck and any of i2c_mux or si2168
i've been running my cubietruck for months without any problems or need to reboot now, and we're using it as video recorder a few times a week. There is also a samba service running für backing up the windows machines, all without problems. So thanks again Igor for your work on the image and scripts. Wouldn't have worked without it.
-
Azrael got a reaction from papasmurfster in Cubieboard3 / Cubietruck experience (I2C MUX, si2168 DVB-C)
Hi papasmurfster,
on my system I could see the usb devices in lsusb and dmesg command outputs (lsusb found the stick as "ID 2013:025f PCTV Systems"). If you can't see the USB stick there, i'm afraid i cannot help you. If the stick shows up there, dmesg should output something like:
usb 2-1: New USB device found, idVendor=2013, idProduct=025f
usb 2-1: Product: PCTV 292e
usb 2-1: Manufacturer PCTV
usb 2-1: SerialNumber *somenumber*
this is standard USB device output and also showed up with no working driver. It shows the USB stick is recognized even if no driver is present.
In the compile.sh script i changed the line
KERNEL_CONFIGURE="no" to KERNEL_CONFIGURE="yes". According to your answer you already did this, i just mention it to reproduce all the needed steps
After starting the script, at some point the kernel menuconfig will pop up. Here I selected the following options:
Device Drivers --> I2C-Support --> I2C bus multiplexing support <*>
Device Drivers --> I2C-Support --> Multiplexer I2C Chip Support: All 3 options to <*>
Device Drivers --> Multimedia Support --> Analog TV support [*]
Device Drivers --> Multimedia Support --> Digital TV support [*]
Device Drivers --> Multimedia Support --> AM/FM radio receivers/transmitters support [*]
Device Drivers --> Multimedia Support --> DVB Network support [*]
Device Drivers --> Multimedia Support --> Media USB Adapters [*]
Device Drivers --> Multimedia Support --> Media USB Adapters --> Support for various USB DVB devices v2 <*>, all sub options as module <m> except DVBSky USB support <*>
Device Drivers --> Multimedia Support --> Media USB Adapters --> Empia EM28xx USB devices support <*>
Device Drivers --> Multimedia Support --> Media USB Adapters --> Empia EM28xx analog TV, Video capture and/or webcam support <*>
Device Drivers --> Multimedia Support --> Media USB Adapters --> Empia EM28xx ALSA audio module <M>
Device Drivers --> Multimedia Support --> Media USB Adapters --> DVB/ATSC Support for em28xx based TV cards <*>
Device Drivers --> Multimedia Support --> Media USB Adapters --> Autoselect ancillary drivers (tubers, sensors, i2c, frontends) [*]
I think these options are be everything I changed. After that, the dmesg output shows additional lines when plugging in the stick:
[ 4.577201] em28178 #0: EEPROM ID = 26 00 01 00, EEPROM hash = 0x8f0cf804
[ 4.577222] em28178 #0: EEPROM info:
[ 4.577230] em28178 #0: microcode start address = 0x0004, boot configuration = 0x01
[ 4.585684] em28178 #0: AC97 audio (5 sample rates)
[ 4.585711] em28178 #0: 500mA max power
[ 4.585721] em28178 #0: Table at offset 0x27, strings=0x146a, 0x1888, 0x0a7e
[ 4.586268] em28178 #0: Identified as PCTV tripleStick (292e) (card=94)
[ 4.586291] em28178 #0: dvb set to isoc mode.
[ 4.586614] em28178 #0: Binding DVB extension
[ 4.643405] i2c i2c-4: Added multiplexed i2c bus 5
[ 4.643434] si2168 4-0064: Silicon Labs Si2168 successfully attached
[ 4.658171] si2157 5-0060: Silicon Labs Si2147/2148/2157/2158 successfully attached
[ 4.658246] DVB: registering new adapter (em28178 #0)
[ 4.658270] usb 2-1: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)...
[ 4.660198] em28178 #0: DVB extension successfully initialized
and after downloading the firmware like mentioned in the starting thread, dmesg also shows:
[ 23.848889] si2168 4-0064: found a 'Silicon Labs Si2168-B40'
[ 23.849973] si2168 4-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
[ 24.142642] si2168 4-0064: firmware version: 4.0.4
[ 24.148767] si2157 5-0060: found a 'Silicon Labs Si2157-A30'
[ 24.198515] si2157 5-0060: firmware version: 3.0.5
and now it should work.
Another problem with the stick: It does not start correctly on system boot, i have to unplug and replug it after booting to get it to work. I hope to find a script to "unplug" and "replug" it via console.
Regards
Markus
-
Azrael got a reaction from Igor in Cubieboard3 / Cubietruck experience (I2C MUX, si2168 DVB-C)
Hi there,
i just wanted to report my experience with Igor Pecovnik's debian 4.1.2 image - especially since he says that I2C is untested with Kernel 4.0 and above.
I have a PCTV DVB-C/T2 USB Stick (Triplestick 292e) and could make it work with my Cubietruck. I had to use Igor's compile script from the project website in my ubuntu virtual machine on Windows 7 to get the kernel sources and compile the kernel with the required options (the offered SD-Card image lacks support for I2C Multiplexing). To use this stick, you have to compile the kernel with I2C Multiplexing built in, and build the i2c mux modules for the chipset (I compiled all i2c_mux drivers as modules since i didn't figure out which was the right one). The USB Stick has a multiplexer to change between the DVB-C and DVB-T2 receiver. After that I checked the DVB-frontends and chipset driver to compile as modules (especially si2168, en28xx, si2157) and now the stick works just fine. So I can confirm that the 4.1.2 kernel from Igor's project website has working I2C and I2C Multiplexing support if you compile your own kernel. All you have to do additionally after building the SD-Card image (all included in the compile script) is get the firmware for the stick (see https://tvheadend.org/boards/4/topics/13782).
I use tvheadend as digital video recorder on the cubietruck, with XBMC / KODI Media Center on Windows PCs and android smartphones for programming and watching.
Next steps are SMB server for backups on 3.5" S-ATA harddrive (with Cubietruck 3.5" addon board) and whatever comes into my mind
I had a lot of trouble getting this TV stick to work on ARM since the old kernels (3.4.x) seem to have no option for i2c multiplexing or the chipset (at least i couldn't find it, but i'm not too familliar with linux kernel stuff), and i found a lot of forums where ppl have the same problems, so i thought this info might be useful for someone.
And thanks a lot to Igor Pecovnik for the debian images and the scripts on his project website
http://www.igorpecovnik.com/2013/12/24/cubietruck-debian-wheezy-sd-card-image/
Regards
Markus