BPI R2 LEDE(openwrt) source code

(gary) #62

The reason why we need the wmt_loader is that the driver of wifi(MT6625) is from Android system which is provided by vendor, and the tools(wmt_loader and stp_uart_launcher) are requried, and we don’t have enough resource to re-write the driver, so that both tools are still required under ubuntu and openwrt.

Please let me know if you have any question.

Thanks Gary


I try to get wifi working. But I fall. Here is the output and what i type in ssh.
I just try the first step. Is that ‘fall’ is normal? Or something wrong in my firmware?

root@LEDE:~# wmt_loader
init combo device
Opened combo device
get device id : 30243
set device id : 30243
do module init: 30243
failed to init module

The time when I type it in output is [59.080349]

minicom_2018-1-18_20-35-13.txt (48.9 KB)

(gary) #64

Please still try other commands, I don’t have enough time to fix the log of error.

(Frank W.) #65

The last failed is ok because gps is currently not working. ignore that and run the stp-launcher :slight_smile:


@frank-w @garywang I’m sorry. :disappointed_relieved: It works in client mode! But not ap mode. I can see interface “ap0” in “ip l”. But I can not get it up in luci->network->wireless. And once I use wpa_supplicant to create ap. I return a lot of errors and just reboot itself.

Here is the log and which i type in ssh
minicom-18_03_41.txt (59.5 KB)
sshtype.txt (3.4 KB)

Key time:

[    62.411966]    wmt_loader
[    74.955550]    stp_uart_launcher -p /etc/firmware/ &
[    86.949227]    echo A >/dev/wmtWifi
[  176.575491]    wpa_supplicant -Dnl80211 -iap0 -c/etc/wpa_supplicant.conf



(Frank W.) #67

do not use wpa_supplicant if you want to use AP-Mode…it must be deinstalled to get it working



I built me an image and copied it to R2. Now u-boot finds the image but cant boot…

Could me help someone?


(Frank W.) #69

how did you copied the image to SD-Card? did uboot not boot directly from sd-card? why do you enter the uboot-console?

try printenv in uboot-console search for the default boot-entry and use that command

in my images “boot”-command does also not work…but the “run bootx” works


after some more trys I got it working/booting


@garywang is anyone pushing your changes upstream to openwrt so that next release will include them?

I would like to see this happen, your tree is a bit behind already. Openwrt updated to the kernel 4.14. I don’t want to duplicate efforts but if nobody is doing this then let me know.


(gary) #73

Hi dsiq

We don’t have plan to push our changes to upstream, our goal is to make current openwrt release to be stable. You know that it will take serval weeks to support latest openwrt(kernel 4.14), I don’t think this is worth for us.

Thanks Gary