TP-LINk Archer C7 V2 TCP connections

[jrnetsupport]

I am intending to use gargoyle firmware in Archer C7 V2 and as per specs, the hardware can handle approx 30,000 simulatneous TCP connections as per : http://www.smallnetbuilder.com/tools/ch ... simul-conn ( not sure if this is accurate).

My question is if Gargoyle firmware has number of tcp connection limitations that would prevent the hardware from reaching its limit ? Thanks you

[Lantis]

It doesn't have a limitation like that. You'd have to check if openwrt has a limitation (it's probably on the wiki). I've seen one as high as 16000.

Gargoyle sets a limit of 8000 but it is changeable.

[jrnetsupport]

Thanks Lantis for your quick response. I just received my Archer C7 V2. Downloaded Gargoyle 1.9.0 factory.bin and followed the instructions. I am getting no response to 192.168.1.1 . I will start to dig the "bricked" forum to see if I can recover.

[tapper]

Thanks Lantis for your quick response. I just received my Archer C7 V2. Downloaded Gargoyle 1.9.0 factory.bin and followed the instructions. I am getting no response to 192.168.1.1 . I will start to dig the "bricked" forum to see if I can recover.

Hi dude sorry to say the c7s are bricking because of a new flash chip.Its bin fixt in Openwrt trunk but not here yet best thing to do is send it back and get a new on sent to you just tel them it was DOA they will never know.

@Lantis I think we need to talk to eric and get the bins for the c7 taken down until we can get this fixt.

Heres a coppy of a email from the dev list:

Archer C7 V2.0 units from December 2015 onwards ( serials starting 215C
) have changed flash chips to the gd25q128 chip, this is supported in
trunk but not presently in 15.05. I would like stable support for this
version so I've back ported the required fix from trunk and removed a
conflicting patch from bcm53xx I've tested the patch it and I'm able to
install a build of 15.05.1 on a new Archer C7 device with this patch.

Signed-off-by: John Marrett <johnf@xxxxxxxxxx.ca>
---
.../patches-3.18/004-mtd-spi-nor-from-3.20.patch | 26 +++++++++-------------
...-mtd_GD25Q128B_support_backport_from_3.19.patch | 12 ++++++++++
2 files changed, 23 insertions(+), 15 deletions(-)
create mode 100644 target/linux/generic/patches-3.18/043-mtd_GD25Q128B_support_backport_from_3.19.patch

diff --git a/target/linux/bcm53xx/patches-3.18/004-mtd-spi-nor-from-3.20.patch b/target/linux/bcm53xx/patches-3.18/004-mtd-spi-nor-from-3.20.patch
index ab7b0bb..449e80f 100644
--- a/target/linux/bcm53xx/patches-3.18/004-mtd-spi-nor-from-3.20.patch
+++ b/target/linux/bcm53xx/patches-3.18/004-mtd-spi-nor-from-3.20.patch
@@ -1,14 +1,8 @@
---- a/drivers/mtd/spi-nor/spi-nor.c
-+++ b/drivers/mtd/spi-nor/spi-nor.c
-@@ -538,6 +538,7 @@ static const struct spi_device_id spi_no
- /* GigaDevice */
- { "gd25q32", INFO(0xc84016, 0, 64 * 1024, 64, SECT_4K) },
- { "gd25q64", INFO(0xc84017, 0, 64 * 1024, 128, SECT_4K) },
-+ { "gd25q128", INFO(0xc84018, 0, 64 * 1024, 256, SECT_4K) },
-
- /* Intel/Numonyx -- xxxs33b */
- { "160s33b", INFO(0x898911, 0, 64 * 1024, 32, 0) },
-@@ -564,14 +565,14 @@ static const struct spi_device_id spi_no
+Index: linux-3.18.29/drivers/mtd/spi-nor/spi-nor.c
+===================================================================
+--- linux-3.18.29.orig/drivers/mtd/spi-nor/spi-nor.c 2016-04-19 19:28:00.391762486 -0400
++++ linux-3.18.29/drivers/mtd/spi-nor/spi-nor.c 2016-04-19 19:29:03.220034573 -0400
+@@ -564,14 +564,14 @@
{ "mx66l1g55g", INFO(0xc2261b, 0, 64 * 1024, 2048, SPI_NOR_QUAD_READ) },

/* Micron */
@@ -31,7 +25,7 @@

/* PMC */
{ "pm25lv512", INFO(0, 0, 32 * 1024, 2, SECT_4K_PMC) },
-@@ -895,6 +896,45 @@ static int spansion_quad_enable(struct s
+@@ -895,6 +895,45 @@
return 0;
}

@@ -77,7 +71,7 @@
static int set_quad_mode(struct spi_nor *nor, struct flash_info *info)
{
int status;
-@@ -907,6 +947,13 @@ static int set_quad_mode(struct spi_nor
+@@ -907,6 +946,13 @@
return -EINVAL;
}
return status;
@@ -91,8 +85,10 @@
default:
status = spansion_quad_enable(nor);
if (status) {
---- a/include/linux/mtd/spi-nor.h
-+++ b/include/linux/mtd/spi-nor.h
+Index: linux-3.18.29/include/linux/mtd/spi-nor.h
+===================================================================
+--- linux-3.18.29.orig/include/linux/mtd/spi-nor.h 2016-04-19 19:28:00.391762486 -0400
++++ linux-3.18.29/include/linux/mtd/spi-nor.h 2016-04-19 19:28:00.387762470 -0400
@@ -56,6 +56,10 @@
/* Used for Spansion flashes only. */
#define SPINOR_OP_BRWR 0x17 /* Bank register write */
diff --git a/target/linux/generic/patches-3.18/043-mtd_GD25Q128B_support_backport_from_3.19.patch b/target/linux/generic/patches-3.18/043-mtd_GD25Q128B_support_backport_from_3.19.patch
new file mode 100644
index 0000000..b1bb3fb
--- /dev/null
+++ b/target/linux/generic/patches-3.18/043-mtd_GD25Q128B_support_backport_from_3.19.patch
@@ -0,0 +1,12 @@
+Index: linux-3.18.29/drivers/mtd/spi-nor/spi-nor.c
+===================================================================
+--- linux-3.18.29.orig/drivers/mtd/spi-nor/spi-nor.c 2016-04-19 20:30:41.535015813 -0400
++++ linux-3.18.29/drivers/mtd/spi-nor/spi-nor.c 2016-04-19 20:32:12.767454183 -0400
+@@ -510,6 +510,7 @@
+ /* GigaDevice */
+ { "gd25q32", INFO(0xc84016, 0, 64 * 1024, 64, SECT_4K) },
+ { "gd25q64", INFO(0xc84017, 0, 64 * 1024, 128, SECT_4K) },
++ { "gd25q128", INFO(0xc84018, 0, 64 * 1024, 256, SECT_4K) },
+
+ /* Intel/Numonyx -- xxxs33b */
+ { "160s33b", INFO(0x898911, 0, 64 * 1024, 32, 0) },
--
1.9.1
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailm ... nwrt-devel

[Lantis]

Done.

I have been working on a patch.

[Mike_Krüger]

I have been working on a patch.

Great to hear that! Let me know if you need a guinea pig.

I am getting no response to 192.168.1.1 . I will start to dig the "bricked" forum to see if I can recover.

I managed to get my C7 going again quite easily on Win7 with TFTD32/TFTD64, I liked it for its visual feedback. Didn't manage it on a Linux box, but I didn't try nor trouble-shoot all possibilities on Linux - I am sure it can be done though.

[tapper]

This thread is why i love Gargoyle!

[Lantis]

I've sent a version for testing to a user.

[Mike_Krüger]

I've sent a version for testing to a user.

Well, that's great news

I had a PM asking for more information on how to unbrick the C7. As I already mentioned you can unbrick it quite easily using TFTP software. It's like an FTP-server, but the router actively asks for an image before it starts booting into its bricked state. It's like a pre-loader or BIOS on a PC if you're looking for a comparable situation. You have to set up the IP-addresses and the file name quite carefully though.

The procedure is described quite well on the OpenWRT wiki-page, so I will just include a link to that page here.

You can restore to TP-Link firmware, to an OpenWRT image or (once it's released) to the new Gargoyle factory firmware. Just make certain that the file is renamed to ArcherC7v3_tp_recovery.bin. From there, you can flash the various images as per the usual.