OpenWrt Forum Archive

Topic: Quallcomm qca9558/TP-Link WDR7500 support

The content of this topic has been archived between 1 May 2014 and 7 May 2018. Unfortunately there are posts – most likely complete pages – missing.

Hi,

Before I do something I might regret later,
Is it ok if I upgrade my current firmware : 3.13.29 Build 130126 Rel.50426n  for the wdr7500 v2 chinese version with this one:

wdr7500v2-20131024.bin  that I downloaded via a post from this thread,

via the web interface?

Thanks.-

xbsd wrote:

Hi,

I bought Archer C7 V2 (Korean Ver.) and opened it up.
It's using QCA9880 v2 and have 16MB flash.

W9751G6KB-25 * 2 / Winbond 25Q128FVSG
QCA9558-AT4A / AR8327N-BL1A / QCA9880-BR4A

Is it safe to try openwrt-ar71xx-generic-archer-c7-v1-squashfs-factory.bin snapshot?
Will I be able to return to original firmware?

Thanks.

Were there any changes to the packaging or box compared to v1.0 and v1.1?
Any way at all to see from outside the box that it is a v2.0?

Jakkvurt wrote:

Were there any changes to the packaging or box compared to v1.0 and v1.1?
Any way at all to see from outside the box that it is a v2.0?

There's model name with version number in small S/N label located at the bottom of box.
No big V2 sticker or anything like that, but since they didn't sold v1.0/1.1 here, they didn't need to advertise about version.

What's the difference between qca9880 and qca9882. I want to replace it with qca9882 v2 which I can get this chip from market.

QCA9882 is a 2-stream version. Maximum theoretical bandwidth is 867 Mbps instead of 1300 Mbps.

Just got myself Archer C7 V2 today, what OpenWRT firmware should I use? Is there exist V2 thread?

I see Newegg has the Archer v2 in stock now.

Has anyone spotted the v2 in Europe yet?

There is the source code for archer C7 v1 .http://www.tp-link.com/resources/gpl/Archer_C7_1.0.tar.gz
Can anyone extract the QCA9880 v1 driver into openwrt firmware?

The v1 driver is not open source, so it is not in the archive.

snk wrote:

The v1 driver is not open source, so it is not in the archive.

my god.
No wonder i can not find the option in the menuconfig after  download the sources and make menuconfig .

It is that nobody  get the V1 sources ?

I have a tenda N60 yet ,it's  BCM43236 5G WIFI chip and BCM53125 Giga switch .I don't understand the openwrt can not support it at persent,but the Tomato can.

Hello,
I just got the chinese version of the WDR7500 router, and strangely enough, because from what I read, it is supposed to be a powerful
router, however my speeds dropped from 10mbs to 3mbs compared to my old Dlink router? using the exact same installation nothing was changed except a router swap and initial configuration.
I did a firmware upgrade form the web interface from the original version 130126 to this one: wdr7500v2_cn_3_13_34_up_boot(140225)_2014-02-26_14.55.53
without any change in the performance! So before I write the router off as a lemon and send it back, I might as well try the openwrt firmware, I found from nosferatu's repository this one: ( thank you smile ) :openwrt-r38298-tl-wdr7500-v2-squashfs-factory.bin  Before I proceed it it safe to perform a web GUI update of the openwrt firmware? if not would  this firmware openwrt-r38298-archer-c7-v1-squashfs-factory.bin safe to flash through the web gui in that case?
I realize my questions are quite basic , thank you for bearing with me, better be safe than sorry.
Regards,
John

snk wrote:
wiraone wrote:

Just got myself Archer C7 V2 today, what OpenWRT firmware should I use? Is there exist V2 thread?

See https://forum.openwrt.org/viewtopic.php … 03#p226603

Is there any easy way for me to compile the V1 into V2 firmware? Looking at the wiki, the only two differences are the flash and WIFI, it is now 16MB instead of 8MB. I'm in need VLAN feature for my ISP, I've got a beta firmware from TPLink which has VLAN but it does't work on my setup.

I've just ordered one of the new V2's with the 16 MB flash and the QCA9880-BR4A from Newegg. Could arrive as soon as tomorrow.

Yes, I bought it knowing that OpenWRT is not yet ready for it.
No, I have no intention of actually using it on the factory garbage.
My network is going to remain on my WDR4300 until this new one is ready for action, at which point, the WDR4300 will be replacing my aging DIR-615b2 up north.

Reading back to page 2 post 30: https://forum.openwrt.org/viewtopic.php … 92#p203092 -- it is suggesting that, at least for the home-jimmied 16MB-soldered-onto-8MB-board, that it may require changes to partition offsets, kernel driver, and build scripts, but in actually looking back at OP's GIT, and in particular, this commit: https://github.com/qca9558/openwrt-wdr7 … 7131e15d2c -- I don't see anything in there actually referencing any of these.

Now it does appear that U-Boot has the flash size, and possibly even the partition table hard coded into it. See https://forum.openwrt.org/viewtopic.php … 76#p203076 -- that is the output of an 8MB U-Boot on a 16MB chip.
http://wiki.openwrt.org/toh/tp-link/tl-wdr7500 also.

Now presumably, the U-Boot on *this* device will be coded with the correct values for this device's partition layout?
Or is there somewhere that the partitions are being specified that I'm missing?
Maybe strictly the kernel commandline? https://forum.openwrt.org/viewtopic.php … 43#p201943

definesinsanity wrote:

Reading back to page 2 post 30: https://forum.openwrt.org/viewtopic.php … 92#p203092 -- it is suggesting that, at least for the home-jimmied 16MB-soldered-onto-8MB-board, that it may require changes to partition offsets, kernel driver, and build scripts, but in actually looking back at OP's GIT, and in particular, this commit: https://github.com/qca9558/openwrt-wdr7 … 7131e15d2c -- I don't see anything in there actually referencing any of these.

You need to make 16 MiB image to make the webUI to accept it, cf. https://dev.openwrt.org/changeset/36790. There is also a related recent patch https://dev.openwrt.org/changeset/40034.

Now it does appear that U-Boot has the flash size, and possibly even the partition table hard coded into it. See https://forum.openwrt.org/viewtopic.php … 76#p203076 -- that is the output of an 8MB U-Boot on a 16MB chip.
http://wiki.openwrt.org/toh/tp-link/tl-wdr7500 also.

Now presumably, the U-Boot on *this* device will be coded with the correct values for this device's partition layout?
Or is there somewhere that the partitions are being specified that I'm missing?
Maybe strictly the kernel commandline? https://forum.openwrt.org/viewtopic.php … 43#p201943

The boot arguments passed from U-Boot are not respected in OpenWrt.

snk wrote:

You need to make 16 MiB image to make the webUI to accept it, cf. https://dev.openwrt.org/changeset/36790. There is also a related recent patch https://dev.openwrt.org/changeset/40034.

Oooooh, that it just right there at the end, staring me in the face.
Thanks!

Ok... from what I can read, the partitions and offsets for tplink devices are actually calculated rather than pre-defined, so just changing that 8Mlzma to 16Mlzma should be all that is actually needed.

(Last edited by definesinsanity on 27 Mar 2014, 14:09)

Ok, so for the v2 add;

target/linux/ar71xx/generic/profiles/tp-link.mk:

define Profile/ARCHERC7v2
    NAME:=TP-LINK Archer C7 v2
    PACKAGES:=kmod-usb-core kmod-usb2 kmod-ledtrig-usbdev
endef

define Profile/ARCHERC7v2/Description
    Package set optimized for the TP-LINK Archer C7 v2.
endef
$(eval $(call Profile,ARCHERC7v2))

target/linux/ar71xx/image/Makefile:

$(eval $(call SingleProfile,TPLINK-LZMA,64kraw,ARCHERC7v2,archer-c7-v2,ARCHER-C7,ttyS0,115200,0x75000001,1,16Mlzma))

Assuming that nothing else is different between the v1 and v2 besides the flash size and wifi card, should do it?

0x75000001,1

sure about this hwid in fw header?

nebbia88 wrote:

0x75000001,1

sure about this hwid in fw header?

Not in the least bit sure. But you're probably quite correct in pointing it out.
And guessing by other device revision changes by tplink... maybe 0x75000002,1

But I think that would be to let the existing firmware know that its ok to flash.

I would

1) not make a new profile, merely add kmod-ath10k to the old
2) add line

$(eval $(call MultiProfile,ARCHERC7,ARCHERC7V1 ARCHERC7V2))

to Makefile
3) change the old line

$(eval $(call SingleProfile,TPLINK-LZMA,64kraw,ARCHERC7,archer-c7-v1,ARCHER-C7,ttyS0,115200,0x75000001,1,8Mlzma))

to

$(eval $(call SingleProfile,TPLINK-LZMA,64kraw,ARCHERC7V1,archer-c7-v1,ARCHER-C7,ttyS0,115200,0x75000001,1,8Mlzma))

4) add line

$(eval $(call SingleProfile,TPLINK-LZMA,64kraw,ARCHERC7V2,archer-c7-v2,ARCHER-C7-v2,ttyS0,115200,0x75000002,1,16Mlzma))

note the changed HWID
5) Add

        *"Archer C7 v2")
                    name="archer-c7-v2"
                    ;;

to base-files/lib/ar71xx.sh

Edit: and of course then add archer-c7-v2 to all necessary files under base-files/etc.

(Last edited by snk on 27 Mar 2014, 16:12)

snk wrote:

I would

1) not make a new profile, merely add kmod-ath10k to the old
2) add line $(eval $(call MultiProfile,ARCHERC7,ARCHERC7V1 ARCHERC7V2)) to Makefile
3) change the old line $(eval $(call SingleProfile,TPLINK-LZMA,64kraw,ARCHERC7,archer-c7-v1,ARCHER-C7,ttyS0,115200,0x75000001,1,8Mlzma)) to $(eval $(call SingleProfile,TPLINK-LZMA,64kraw,ARCHERC7V1,archer-c7-v1,ARCHER-C7,ttyS0,115200,0x75000001,1,8Mlzma))
4) add line $(eval $(call SingleProfile,TPLINK-LZMA,64kraw,ARCHERC7V2,archer-c7-v2,ARCHER-C7-v2,ttyS0,115200,0x75000002,1,16Mlzma)) note the changed HWID
5) Add

        *"Archer C7 v2")
                    name="archer-c7-v2"
                    ;;

to base-files/lib/ar71xx.sh

Ok, I'll try that.
I've also just taken a look at the factory firmware for this device (downloaded from their website), looks like the hwid on the new one should be "0xc7000002". Interesting.

(Last edited by definesinsanity on 27 Mar 2014, 16:15)

definesinsanity wrote:

Ok, I'll try that.
I've also just taken a look at the factory firmware for this device (downloaded from their website), looks like the hwid on the new one should be "0xc7000002". Interesting.

Maybe the chinese WDR7500 v2.0 already uses 0x75000002?

snk wrote:
definesinsanity wrote:

Ok, I'll try that.
I've also just taken a look at the factory firmware for this device (downloaded from their website), looks like the hwid on the new one should be "0xc7000002". Interesting.

Maybe the chinese WDR7500 v2.0 already uses 0x75000002?

Seems possible.


How do you add a kmod to a device profile?

definesinsanity wrote:
snk wrote:
definesinsanity wrote:

Ok, I'll try that.
I've also just taken a look at the factory firmware for this device (downloaded from their website), looks like the hwid on the new one should be "0xc7000002". Interesting.

Maybe the chinese WDR7500 v2.0 already uses 0x75000002?

Seems possible.


How do you add a kmod to a device profile?

Just add "kmod-ath10k" to the end of

PACKAGES:=kmod-usb-core kmod-usb2 kmod-ledtrig-usbdev