Jump to content

Cubieboard3 / Cubietruck experience (I2C MUX, si2168 DVB-C)

Azrael

By Azrael
in Allwinner sunxi

 Share

Recommended Posts

Azrael

Azrael

Posted
Posted

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

1
Link to comment
Share on other sites
papasmurfster

papasmurfster

Posted
Posted

Hi Azreal,

 

I'm in a similar situation, I have a Banana Pi. I'm using Igors Jessie Image with kernel 4.1.2 and I cant seem to see any of my usb dvb devices (one of which is Triplestick 292e).

Could you details what exactly you did, I've tried the the cross compiler with the menuconfig option enabled. I just cant see to see what features need to be enabled in the config.

 

Regards

 

Steve

 

 

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

Link to comment
Share on other sites
Azrael

Azrael

Posted
  • Author
Posted

Hi Azreal,

 

I'm in a similar situation, I have a Banana Pi. I'm using Igors Jessie Image with kernel 4.1.2 and I cant seem to see any of my usb dvb devices (one of which is Triplestick 292e).

Could you details what exactly you did, I've tried the the cross compiler with the menuconfig option enabled. I just cant see to see what features need to be enabled in the config.

 

Regards

 

Steve

 

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

1
Link to comment
Share on other sites
seppel

seppel

Posted
Posted

Just for information:

 

i use my CT with Sundtek MediaTV Pro III DVB-C/T/T2 and it works like a charm. Driver installation is easy (execute script provided by Sundtek -> done).

 

Tested on Igors Images with Kernel 3.4.xxx and Kernel 4.1.2 (wheezy! jessie did not work with tvheadend!)

TVheadend 3.4 and 4.0.5 tested.

 

Its currently in use as tvheadend server for a kodi installation on another machine.

 

This is a GERMAN howto:

 

https://bunchofbricks.wordpress.com/2015/06/18/howto-cubietruck-mit-tvheadend-minnowboard-max-mit-kodi/

 

greetings

seppel

1
Link to comment
Share on other sites
papasmurfster

papasmurfster

Posted
Posted

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
 
 
I'll try and post some more details on the results after I've tried it for a week or 2.
 
Thanks again
1
Link to comment
Share on other sites
Azrael

Azrael

Posted
  • Author
Posted

Just for information:

 

i use my CT with Sundtek MediaTV Pro III DVB-C/T/T2 and it works like a charm. Driver installation is easy (execute script provided by Sundtek -> done).

 

Tested on Igors Images with Kernel 3.4.xxx and Kernel 4.1.2 (wheezy! jessie did not work with tvheadend!)

TVheadend 3.4 and 4.0.5 tested.

 

Its currently in use as tvheadend server for a kodi installation on another machine.

 

This is a GERMAN howto:

 

https://bunchofbricks.wordpress.com/2015/06/18/howto-cubietruck-mit-tvheadend-minnowboard-max-mit-kodi/

 

greetings

seppel

 

I am using the debian jessie image with kernel 4.1.2 and tvheadend from git, works good so far, haven't noticed any problems yet...

 

 

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
 
 
I'll try and post some more details on the results after I've tried it for a week or 2.
 
Thanks again

 

 

Good to hear they are all working now. A short report would be good since a lot of ppl seem to have problems with these dvb sticks. I have spent some time watching live-tv now with android smartphones (kodi), but have not tested the recording and timeshift feature yet. I need an additional harddrive for that first :)

Link to comment
Share on other sites
sschöne

sschöne

Posted
Posted

Hello everybody,

 

I've also a Banana Pi and a PCTV 292e. For me it does not work. Did you only compile the kernel?

 

I do the following steps:

 

apt-get -y install git
git clone https://github.com/igorpecovnik/lib
cp lib/compile.sh .
chmod +x compile.sh
change the line in the compile.sh KERNEL_CONFIGURE="no" to KERNEL_CONFIGURE="yes"

./compile.sh

 

Choose Banana Pi

https://camo.githubusercontent.com/d17f9933c508cd6b06b6d57ac0aa9d0d447b0777/687474703a2f2f7777772e69676f727065636f766e696b2e636f6d2f77702d636f6e74656e742f75706c6f6164732f323031352f30352f63686f6f73652d6b65726e652e706e67

 

But what do you choose on the next two screenshots?

 

https://camo.githubusercontent.com/6e3a9352468638bc2d098d4ee8483b9fea725edd/687474703a2f2f7777772e69676f727065636f766e696b2e636f6d2f77702d636f6e74656e742f75706c6f6164732f323031352f30352f63686f6f73652d64697374726f2e706e67

https://camo.githubusercontent.com/d17f9933c508cd6b06b6d57ac0aa9d0d447b0777/687474703a2f2f7777772e69676f727065636f766e696b2e636f6d2f77702d636f6e74656e742f75706c6f6164732f323031352f30352f63686f6f73652d6b65726e652e706e67

 

Could somebody explain me step by step, how to compile the kernel? Or perhaps papasmurfster can you provide me your working image? That would be very nice.

 

Sorry for my bad english.

Link to comment
Share on other sites
Igor

Igor

Posted
Posted

By default you are compiling everything. 

You started properly and first / default options is the safest one (Wheezy) and (defaut 3.4.x) in next screen.

 

If you only need kernel, than alter one more config. option: KERNEL_ONLY="no" - >  "yes"

Link to comment
Share on other sites
papasmurfster

papasmurfster

Posted
Posted

By default you are compiling everything. 

 

You started properly and first / default options is the safest one (Wheezy) and (defaut 3.4.x) in next screen.

 

If you only need kernel, than alter one more config. option: KERNEL_ONLY="no" - >  "yes"

 

I dont think the PCTV 292e is supported in the 3.4 kernek http://www.linuxtv.org/wiki/index.php/PCTV_Systems_tripleStick_T2_(292e)

Link to comment
Share on other sites
sschöne

sschöne

Posted
Posted

When I choose mainline and wheezy, I have other options later:

 

Device Drivers --> I2C-Support --> Multiplexer I2C Chip Support: There are 5 Options

 

and

 

Autoselect ancillary drivers (tubers, sensors, i2c, frontends) [*] is under Device Drivers --> Multimedia Support

 

Edit: Now i have a file Armbian_4.4_Bananapi_Debian_wheezy_4.2.1.zip in /output/images which is only 300MB.

When I unzip this file, I have 3 files: imagewriter.exe, Armbian_4.4_Bananapi_Debian_wheezy_4.2.1.raw an armbian.txt. I can unzip the raw file to 0.img. This file is only 900MB. When I write this image on a sd card, the banana pi does not start with it. When I want to open the sdcard in the explorer, it comes a message, that I have to format the card.

 

What is wrong?

 

Edit: It works!!!

 

Edit: I installed tvheadend. There I can choose the Silicon Labs Si2168 under TV Adapter. When I choose the DVB Network, it search the muxes. But it does not find any services.

Does somebody has any idea?

1
Link to comment
Share on other sites
sschöne

sschöne

Posted
Posted

dmesg | grep dvb shows:

 

si2168 3-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'

 

This file is under /lib/firmware

 

Edit: now, 1 hour later, dmesg | grep dvb shows nothing! When I start w_scan -fc and stop it after a few seconds, dmesg | grep dvb shows:

 

si2168 3-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'

si2168 3-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'

 

After a reboot:

dmesg | grep dvb

[ 2.010462] usbcore: registered new interface driver dvb_usb_dvbsky

[ 2.010565] em28xx: Registered (Em28xx dvb Extension) extension

[ 4.565730] em28178 #0: dvb set to isoc mode.

[ 22.000949] si2168 3-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'

1
Link to comment
Share on other sites
sschöne

sschöne

Posted
Posted

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
1
Link to comment
Share on other sites
mosen

mosen

Posted
Posted

Hi guys,

 

I have a cubietruck and I've tried to compile a new kernel (4.x - wheezy, jessie, or trusty) according to this how-to.

Unfortunately the kernel-compilation fails for me. (It works with 3.4.x but not with 4.x)

I need a 4.x Kernel due to the I2C MUX which Azrael mentioned above. In addition to that I need EM28xxx-driver for my PCTV 520e-USB-Stick.

 

 

I hope you can help me. Thank you!

 

Here is my output-log of the kernel-compilation:

root@ubuntu:/home/m# ./compile.sh
Already up-to-date.
[ o.k. ] Dependencies check [ @host ]
[ o.k. ] Building [ Armbian 4.70 Cubietruck Debian jessie next ]
[ o.k. ] Synching clock [ host ]
[ o.k. ] source downloading [ @host ]
[ o.k. ] ... updating [ u-boot ]
remote: Counting objects: 508, done.
remote: Compressing objects: 100% (52/52), done.
remote: Total 418 (delta 360), reused 418 (delta 360)
Receiving objects: 100% (418/418), 46.60 KiB | 0 bytes/s, done.
Resolving deltas: 100% (360/360), completed with 83 local objects.
From git://git.denx.de/u-boot
   f84c2b66..7868031 master     -> origin/master
[ o.k. ] ... updating [ linux-mainline ]
[ o.k. ] ... updating [ sunxi-tools ]
[ o.k. ] ... updating [ rt8192cu ]
[ o.k. ] ... updating [ fbtft-drivers ]
[ o.k. ] ... updating [ sunxi-display-changer ]
[ o.k. ] Compiling sunxi tools [ @host & target ]
[ o.k. ] Cleaning [ /home/m/sources/u-boot ]
[ o.k. ] Removing [ /home/m/output/debs/linux-u-boot-next-cubietruck_4.70_armhf.                                                                                deb ]
[ o.k. ] Cleaning [ /home/m/sources/linux-mainline ]
error: pathspec 'v4.3.3
(EOL)' did not match any file(s) known to git.
[ o.k. ] Patching [ kernel 4.4.0rc6 ]
[ o.k. ] ... compiler bug [ reverting patch ]  [ kernel ]
[ o.k. ] ... sun4i: spi: Allow transfers larger than FIFO size [ kernel ]
[ o.k. ] ... fix BRCMFMAC AP mode Banana & CT [ kernel ]
[ o.k. ] ... deb packaging fix [ kernel ]
[ o.k. ] ... Banana M2 support, LEDs [ kernel ]
[ o.k. ] ... Cubieboard2 double SD version [ kernel ]
[ warn ] ... Allwinner A10/A20 CAN Controller support already applied [ kernel ]
[ o.k. ] ... adding Lamobo R1 [ kernel ]
[ o.k. ] ... adding Bananapi M2 A31s [ kernel ]
[ o.k. ] ... adding Bananapi M1 Plus [ kernel ]
[ o.k. ] ... adding Bananapi R1 [ kernel ]
[ o.k. ] Patching [ u-boot v2015.10 ]
[ o.k. ] ... Add Lamobo R1 [ u-boot ]
[ o.k. ] ... Add AW SOM [ u-boot ]
[ o.k. ] ... Add Armbian boot splash [ u-boot ]
[ o.k. ] Patching [ other sources ]
[ o.k. ] Compiling uboot. Please wait. [ 2015.10 ]
[ o.k. ] Target directory [ /home/m/output/debs/ ]
[ o.k. ] Building deb [ linux-u-boot-next-cubietruck_4.70_armhf.deb ]
[ o.k. ] Compiling kernel [ @host ]
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/basic/bin2c
  HOSTCC  scripts/kconfig/mconf.o
  HOSTCC  scripts/kconfig/zconf.tab.o
  HOSTCC  scripts/kconfig/lxdialog/checklist.o
  HOSTCC  scripts/kconfig/lxdialog/util.o
  HOSTCC  scripts/kconfig/lxdialog/inputbox.o
  HOSTCC  scripts/kconfig/lxdialog/textbox.o
  HOSTCC  scripts/kconfig/lxdialog/yesno.o
  HOSTCC  scripts/kconfig/lxdialog/menubox.o
  HOSTLD  scripts/kconfig/mconf
scripts/kconfig/mconf  Kconfig
configuration written to .config

*** End of the configuration.
*** Execute 'make' to start the build or try 'make help'.

  HOSTCC  scripts/kconfig/conf.o
  HOSTLD  scripts/kconfig/conf
scripts/kconfig/conf  --oldconfig Kconfig
#
# configuration written to .config
#

 Armbian building script, http://www.armbian.com | Author: Igor Pecovnik
 qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq


                                       lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
                                       x Compiling DTB ccache ...                                                     x
                                       xqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqx
                                       x   DTC     arch/arm/boot/dts/sun5i-a10s-mk802.dtb                             x
                                       x   DTC     arch/arm/boot/dts/sun5i-a10s-olinuxino-micro.dtb                   x
                                       x   DTC     arch/arm/boot/dts/sun5i-a10s-r7-tv-dongle.dtb                      x
                                       x   DTC     arch/arm/boot/dts/sun5i-a10s-wobo-i5.dtb                           x
                                       x   DTC     arch/arm/boot/dts/sun5i-a13-hsg-h702.dtb                           x
                                       x   DTC     arch/arm/boot/dts/sun5i-a13-inet-98v-rev2.dtb                      x
                                       x   DTC     arch/arm/boot/dts/sun5i-a13-olinuxino.dtb                          x
                                       x   DTC     arch/arm/boot/dts/sun5i-a13-olinuxino-micro.dtb                    x
                                       x   DTC     arch/arm/boot/dts/sun5i-a13-q8-tablet.dtb                          x
                                       x   DTC     arch/arm/boot/dts/sun5i-a13-utoo-p66.dtb                           x
                                       x   DTC     arch/arm/boot/dts/sun5i-r8-chip.dtb                                x
                                       x   DTC     arch/arm/boot/dts/sun6i-a31-app4-evb1.dtb                          x
                                       x ERROR (duplicate_node_names): Duplicate node name /soc@01c00000/pinctrl@01c2 x
                                       x ERROR: Input tree has errors, aborting (use -f to force output)              x
                                       x make[1]: *** [arch/arm/boot/dts/sun6i-a31-app4-evb1.dtb] Error 2             x
                                       x make: *** [dtbs] Error 2                                                     x
                                       mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj



[ error ] DTBs was not build [ @host ]
root@ubuntu:/home/m#
 
Link to comment
Share on other sites
Igor

Igor

Posted
Posted

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 ...

1
Link to comment
Share on other sites
Azrael

Azrael

Posted
  • Author
Posted

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.

1
Link to comment
Share on other sites
d1dd1

d1dd1

Posted
Posted

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 !

2
Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept