OpenWrt Forum Archive

Topic: Working image for Cubietruck

The content of this topic has been archived on 25 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hi Community,

first a big thanks to the Developers.

I've made a small SD-Card-Image for me, because i couldn't activate the Onboard-WiFi.

Image is maximum 600MB sized.

inside the package are :

- openWRT from Trunk, Date 10. December 2015 with brcmfmac with sdio support
- packages directory with kernel modules
- firmware downloadscript to get the missing files in place
- md5 file

Download
openwrt_trunk_10.12.2015.zip   

MD5 for Zip :  ec56de39033438835fa18aac4a6fda3d

feel free to try

Greets, Dierk Schneider


here some images:

http://imgur.com/a/37O6w

(Last edited by Dierk_S on 11 Dec 2015, 19:22)

are there any tests from other cubietruck users?
any suggestions?

Hello Dierk,

I also want to use openwrt on my cubietruck.
Is it right, on the screen shots it looks as it you managed to use the onboard wifi?

How exactly did you manage this?

Have you got Chaos Calmer with Wifi working, too?

I have Chaos Calmer w/o wifi running, so far.
I compiled it myself.

Help would be appreciated!

Zappel

(Last edited by zappel on 12 Jan 2017, 22:10)

Hello,

I got it working! But there are a few things to change in the script.

The firmware files can now only be loaded via https, which is not supported by wget, I did did not mange to replace it by a stand-alone wget.
So I did:

cd /lib/firmware/brcm/ 
opkg install curl
curl -O -k https://ftp2.halpanet.org/source/_dev/linux-firmware.git/brcm/brcmfmac43362-sdio.bin
curl -O -k https://ftp2.halpanet.org/source/_dev/linux-firmware.git/brcm/brcmfmac43143-sdio.bin

I am using the packages from CC, however, due to the different kernel versions (4.4.13 vs. 4.4.13), the kernel packages do not work, and they are also not included in the image/archive.

Which means, I am struggling to install my additional USB wifi ...

But in the end, yes, cubietruck wifi is working.

Thanks,
         Zappel.

The discussion might have continued from here.