Support for WAVE 300 Wi-Fi chip

lukasz92 · 2020-02-24T13:45:59.748Z

Could you share speed of upload/download on 19.07.1?

I remember that there was an option, to allow wifi interface to be bridged to br-lan:
iwpriv wlan0 sBridgeMode=1

@ahmar16 a script is needed to link /etc/config/wireless with wave300 driver, example can be found here: https://sourceforge.net/p/netiaspotwrt/trunk/38541/tree//branches/attitude_adjustment/target/linux/lantiq/base-files/lib/wifi/mtlk.sh , but it worked on OpenWRT 12.09 - not sure if any modifications are needed to 19.07.

ahmar16 · 2020-02-24T19:19:49.606Z

lukasz92:

Could you share speed of upload/download on 19.07.1

To be clear I'm not using WAVE300 driver at the moment. To compile the driver I'll need OpenWrt source and atm my laptop is not in a good shape to go for that.

I'll need a couple of weeks to get a new HDD for my laptop and then I'll possibly check the script myself. If I remember correctly, the WiFi speeds may have been provided above in the topic somewhere but they also were implemented with another set of patches from @pc2005.

Smim0 · 2020-02-25T08:41:11.320Z

Hello ahmar16,

I'm trying to compile pc2005 driver but I get the following error message after exitting "make menuconfig"

make[3]: *** No rule to make target '../../../../../tools/mtidl/.deps/mtidl_ini_parser.Po'.  Stop.
make[3]: Leaving directory '/home/moha/src/wave300/builds/ugw5.4-vrx288/tools/shared/linux'
Makefile:455: recipe for target 'install-recursive' failed
make[2]: *** [install-recursive] Error 1
make[2]: Leaving directory '/home/moha/src/wave300/builds/ugw5.4-vrx288/tools/shared'
Makefile:519: recipe for target 'install-recursive' failed
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory '/home/moha/src/wave300/builds/ugw5.4-vrx288'
Makefile:21: recipe for target 'all' failed
make: *** [all] Error 2

I don't know where does "../../../" come from but it is the source of the error I think

Do you remember what changes did you make?

BTW: vittorio88/wave300 compiles successfully even with v18.06.7 (kernel 4.14)

Thanks

Smim0 · 2020-02-25T12:09:52.532Z

here you have the sources

https://repo.or.cz/wave300.git

ahmar16 · 2020-02-25T19:01:53.450Z

You need to execute make distclean in wave300 sources directory. It will clear any errors and then set your OpenWrt source and make the modules.

Edit: I am having the same issue on v18.06.7. @pc2005 Can you please check the wave300 sources?

suleiman · 2020-02-25T20:31:56.415Z

I have some good news.

For the livebox users you don't need to recompile openwrt with MSI if you modify the driver to not use MSI which is pretty easy.
I back-ported the rflib version 3.5 to work with driver version 03.02.03.01.25 which has a working sta_upper.bin firmware and now wifi scanning works.
I managed to make the hostapd_08x patches compile with the latest hostapd package from openwrt 19.07.

I will post my sources and results soon.

suleiman · 2020-02-25T20:41:41.321Z

The only version that worked for me initially is version 3.4 from https://repo.or.cz/wave300.git. Read the README file for instructions.

Version 3.1 and 3.2 just hanged then crashed the router but I was able to find the fix and backport it from 3.4 to 3.2 because 3.2 has a working station mode firmware.

suleiman · 2020-02-25T20:47:11.848Z

The steps to enable MSI should be the same with kernel 4.9 too, but I will publish my patches for driver version 3.2 where I removed the part that allocates an IRQ with MSI and now it works with stock openwrt no recompilation needed.

ahmar16 · 2020-02-26T17:14:31.664Z

These days I have limited internet with my mobile data and I'm not home. I'll need a few more days until I get home and then I can actually start working on this driver and try to fix it as much as I can so it is compatible with v18.06 and v19.07.

ahmar16 · 2020-03-09T15:10:33.012Z

I have started working on the driver and I am finding it really hard to build it. It seems (to me) the driver is selecting everything and trying to build it, not just the driver. Although only the driver is selected in the config, with default options as suggested by @pc2005.

I have set up the v18.06.8 and building the driver against it. @pc2005 can you please have a look at the driver? Also I have created a new Github repo for the driver because the original repo is not hosted on the Github. If someone wants to have write-access to the code for development then please send me a PM and I'll add you as a collaborator. The repo contains much information to compile the driver and how to use it.

ple91 · 2020-03-10T00:30:02.415Z

Hey, have anyone tried to use this driver (even on OpenWRT v18) on other hardware then Livebox?

I'm thinking about TP-Link TD-W9980 family. As I can see they also use Lantiq XWAY WAVE300.

Even if there are only Livebox users, do you see any chance of making 5GHz usable on TD-Wx980 with this driver?

ahmar16 · 2020-03-10T03:50:39.532Z

Livebox users came a few days ago. First testing was done on TP-Link TD-W8980 and possibly VR200(?).

The driver has been tested on v18.06.2 successfully but OpenWrt has changed implementation from python2 to python3 so building that version has some issues due to python differences. I am trying to build it with v18.06.8 so hopefully it will be available for testing soon. I may provide testable kernel modules and then xrx200 family devices can use it.

Mandrake-Lee · 2020-03-19T19:55:24.005Z

Dear @suleiman,
Thank you very much for your detailed answer. That has regained the interest I had in this bitchy driver (where again I'm spending so many hours).

In fact I was waiting or aiming for a major update in the PCIe system and MSI interrupts. I believe this is the major roadblock to get the driver working. In this regards, I see the work of @xdarklight very promising for the Lantiq xrx200 platform. Also the irruption of the Lantiq UGW sources has been of great interest.

But coming to the topic; I've followed your instructions and:

The devicetree needed some changes, but I'm stuck now in following message
[4294855112] mtlk3(_mtlk_mmb_wait_chi_magic:2371): Wait for CHI Magic failed (wait_res=1 value=0xbeadfeed)
The option of avoiding MSI by IRQ polling has been tried with no succes. This is the message.
[ 177.390407] [4294844596] mtlk3(_mtlk_mmb_send_hw_dep_cfg:2465): FW set HW dependent configuration failed (err=-4)

So still no luck although getting closer

Peace and love brother

Mandrake-Lee · 2020-03-19T20:07:47.858Z

Dear @ahmar16,
Thank you very much for the initiative of publishing all the scattered information into github.

I followed your instructions recently and they are very detailed and understandable.

As I stated before, I haven't been succesful on bringing up the driver but I'm afraid is something with my device Livebox 2.1 and the PCIe connection that it has. Bad luck.

I'd like to help the community; thereforeI have uploaded into the following link the firmware files that I have collected from different sources, mainly strips from images. I believe this can be shared.

Please note that some files have to be renamed and sometimes a cocktail of sources is to be taken.

Take care you all

Wave300 Firmware files -UPDATED-

EDIT: I've found more firmwares, even the latest to 3.4.2 although sta_upper.bin is missing here. As I said, the best we can do is a good cocktail.

ahmar16 · 2020-03-19T20:21:21.315Z

How were you able to successfully build the driver? I myself have not been able to build the driver with v18.06.8 with the above sources that I put together on Github. I believe there's something wrong with the makefiles or the configuration of some sort that fails the process.

Thank you for the firmware files. I'll put them on Github when I can.

Mandrake-Lee · 2020-03-20T17:09:19.443Z

Hello @ahmar16,

Yes I did build the driver but it was based on a git clone I had from @Smim0 's link; that was before summer.

So I have cloned your github and I have found the troubles you mention. Now I recall I had the same issues. Basically some files (Makefile.in and *.Po) went astray... god knows why.

The point is that I was able to put back all the files from my working copy, probably from UGW sources, and now it works like a charm. I have sent you a pull request to your github, which I'd like to be the central repository of WAVE300 driver.

Please try it and let us know.

Keep in touch!

pc2005 · 2020-03-21T10:54:41.549Z

Ok once again I'm back (but still without a time). I've read the whole chat and good work everyone ;-).

I've tried to compile a whole new openwrt snapshot and it seems wave300 doesn't support v5 kernel build system (it originates from v2.6). So openwrt testing kernel won't work. The last kernel which works is 4.19 (I think, = the non testing variant). I've tried to fix the problem and I couldn't found a way to fix that it is too obscure.

So I've hacked together (mirror) a quick working configuration of source codes from 4.19 build. There were some really weird things (logging functions being generated from perl for every directory, a single source for userspace app and kernel driver). So I've had to hack many print outs to the standard pr_info. There is a lots of unused code, no configuration support, distclean is done manually by deleting all .o and .cmd files but it worked on v5 and I've seen the test network on my laptop (and packet dumps on tp-link modem).

Also the 4.19 kernel needs some patching so I will send patches when I will found my login keys to repo.cz .

I suggest to not use the original tree as it is nearly impossible to develop on and use this hacked version to develop fully new driver from scratch (it will cost less human power).

I've checked iwlwav soruce code and it seems the code is just an newer iteration of our wave300 repos and obviously it doesn't support wave300. Actually if I remember correctly the driver lost the ABI/API support of the firmware after the transition from v3.4 to v3.5 and soon after the hardware lookup (PCI VID/DID) for wave300 was removed completely.

Wait for CHI Magic failed
This means incompatible/missing firmware. CHI magic word should appear after uploading the firmware to the device and it is hardcoded in some parameters structure after initialization. Bad location or a different word will obviously fail (most likely 3.2 fw vs 3.4 driver )

ahmar16 · 2020-03-21T15:02:15.924Z

Welcome back @pc2005. Although I have not yet tested the new sources from @pc2005, and it may take me a couple of days to test them anyway, I think this is better than trying to fix the old driver.

That being said I have tested the (old) driver with v18.06.8 and sadly it crashes the kernel. I could not really see the error because my TTL adapter was behaving weird and missing output. Now that I have seen the above post, I believe it does not matter anymore. I personally think we should be working on a driver which supports next major version rather than trying to backport something that may not even work, or something like that.

I am going to let this slide for now and not make any changes to the Github unless we can properly test the new sources and see if it works.

Smim0 · 2020-05-04T12:50:06.275Z

Hello suleiman,

Can you share the patches and also a quick steps guide on how to get this driver working for Livebox 2.1?

Regards,

Smim0 · 2020-05-09T09:47:52.137Z

Hello all,

I managed to get the driver working in a LiveBox with ip connectivity, I tried to bridge the wlan0 with the option Iwpriv wlan0 sBridgeMode 1 and also added it to lan interface settings now when the it is up I see this in the log

Sat May  9 09:45:17 2020 kern.warn kernel: [ 2368.105122] [0002068032] mtlk0(mtlk_mbss_send_vap_activate:3228): CID-0000: mtlk_txmm_msg_send, MsgId = 0x453, ESSID = test-24ghz
Sat May  9 09:45:17 2020 kern.warn kernel: [ 2368.128877] [0002068056] mtlk0(mtlk_mbss_init:3471): CID-0000: mtlk_mbss_send_vap_activate returned successfully
Sat May  9 09:45:17 2020 kern.info kernel: [ 2368.233290] br-lan: port 2(wlan0) entered blocking state
Sat May  9 09:45:17 2020 kern.info kernel: [ 2368.237220] br-lan: port 2(wlan0) entered forwarding state
Sat May  9 09:45:17 2020 daemon.notice netifd: Network device 'wlan0' link is up

If I set up a manual ip adress I can get access to the router, the iperf results are:

[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-1.01   sec   977 KBytes  7.96 Mbits/sec                  
[  4]   1.01-2.01   sec   816 KBytes  6.68 Mbits/sec                  
[  4]   2.01-3.00   sec   217 KBytes  1.79 Mbits/sec                  
[  4]   3.00-4.00   sec   608 KBytes  4.98 Mbits/sec                  
[  4]   4.00-5.00   sec  1.03 MBytes  8.67 Mbits/sec                  
[  4]   5.00-6.00   sec  1.03 MBytes  8.60 Mbits/sec                  
[  4]   6.00-7.00   sec  1.29 MBytes  10.8 Mbits/sec                  
[  4]   7.00-8.00   sec   569 KBytes  4.67 Mbits/sec                  
[  4]   8.00-9.00   sec  1.11 MBytes  9.32 Mbits/sec                  
[  4]   9.00-10.00  sec  1.17 MBytes  9.78 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-10.00  sec  8.74 MBytes  7.33 Mbits/sec                  sender
[  4]   0.00-10.00  sec  8.58 MBytes  7.19 Mbits/sec                  receiver

iperf Done.