Topic: TP-Link TL-WR941N WR941ND - Atheros AP81 platform, USB port

8 Jan 2009, 19:10

IMPORTANT: This thread is old and out of date, read the most recent messages in the thread and ignore this opening post

-==============

Atheros AP81 routers that run u-boot that are now working with OpenWRT. However, this router has proven difficult to date given a highly modified u-boot that is crippled.

This router has some interesting hardware:

-- Common Atheros AP81 specifications: 400mhz CPU, 32MB of RAM, 4MB of FLASH. U-boot says 8MB of flash, but it is not true on actual hardware.
-- Atheros AR9103 802.11n radio chip has 3x3 MIMO with external antennas
-- USB port header has been discovered on the motherboard, even a punch-out on the plastic case.
-- BAD: the rs232 port on the router requires you to bridge one tiny surface mount pad jumpers/bridge.
-- 20 pin JTAG port identified, J9 on motherboard

===================
The wiki is running like crap the past months, so putting some stuff here. This s the default factory firmare boot, 9600 bps:

U-Boot 1.1.4 (May  1 2008 - 19:25:20)

AP81 (ar7100) U-boot
DRAM:  
sri
32 MB
id read 0x100000ff
flash size 8MB, sector count = 128
Flash:  8 MB
Using default environment

In:    serial
Out:   serial
Err:   serial
Net:   ag7100_enet_initialize...
No valid address in Flash. Using fixed address
eth0: 00:03:7f:09:0b:ad
eth0 up
eth0
Autobooting in 1 seconds, press "tp" to stop
## Booting image at bf020000 ...
   Uncompressing Kernel Image ... OK

Starting kernel ...

The bps rate then goes to 115200:

Linux version 2.6.15--LSDK-6.1.1.40 gcc version 3.4.4 #37 Wed Apr 23 17:03:39 CST 2008
flash_size passed from bootloader = 8
CPU revision is: 00019374
Determined physical RAM map:
 memory: 02000000 @ 00000000 (usable)
User-defined physical RAM map:
 memory: 02000000 @ 00000000 (usable)
Built 1 zonelists
Kernel command line: console=ttyS0,115200 root=/dev/mtdblock2 rootfstype=squashfs init=/sbin/init mtdparts=ar7100-nor0:128k(u-boot),1024k(kernel),2816k(rootfs),64k(config),64k(art) mem=32M
Primary instruction cache 64kB, physically tagged, 4-way, linesize 32 bytes.
Primary data cache 32kB, 4-way, linesize 32 bytes.
Synthesized TLB refill handler (20 instructions).
Synthesized TLB load handler fastpath (32 instructions).
Synthesized TLB store handler fastpath (32 instructions).
Synthesized TLB modify handler fastpath (31 instructions).
Cache parity protection disabled
PID hash table entries: 256 (order: 8, 4096 bytes)
Using 200.000 MHz high precision timer.
Console: colour dummy device 80x25
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 29700k/32768k available (1753k kernel code, 3052k reserved, 354k data, 116k init, 0k highmem)
Mount-cache hash table entries: 512
Checking for 'wait' instruction...  available.
NET: Registered protocol family 16
Jumpstart button pressed.
AR7100 GPIOC major 0
squashfs: version 3.3 (2007/10/31) Phillip Lougher
Initializing Cryptographic API
io scheduler noop registered
io scheduler deadline registered
Serial: 8250/16550 driver $Revision: #1 $ 1 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x0 (irq = 19) is a 16550A
RAMDISK driver initialized: 1 RAM disks of 8192K size 1024 blocksize
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
PPP MPPE Compression module registered
NET: Registered protocol family 24
5 cmdlinepart partitions found on MTD device ar7100-nor0
Creating 5 MTD partitions on "ar7100-nor0":
0x00000000-0x00020000 : "u-boot"
0x00020000-0x00120000 : "kernel"
0x00120000-0x003e0000 : "rootfs"
0x003e0000-0x003f0000 : "config"
0x003f0000-0x00400000 : "art"
NET: Registered protocol family 2
IP route cache hash table entries: 512 (order: -1, 2048 bytes)
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
ar7100wdt_init: Registering WDT success
VFS: Mounted root (squashfs filesystem) readonly.
Freeing unused kernel memory: 116k freed
init started:  BusyBox v1.01 (2008.04.22-03:29+0000) multi-call binary
Algorithmics/MIPS FPU Emulator v1.5
ip_conntrack version 2.4 (256 buckets, 5120 max) - 236 bytes per conntrack
flash_id is 0X10215
Now flash open!
Now flash open!

 (none) mips #37 Wed Apr 23 17:03:39 CST 2008 (none)
(none) login: device eth0 entered promiscuous mode
br0: port 1(eth0) entering learning state
br0: topology change detected, propagating
br0: port 1(eth0) entering forwarding state
ath_hal: module license 'Proprietary' taints kernel.
ath_hal: 0.9.17.1 (AR5416, DEBUG, REGOPS_FUNC, WRITE_EEPROM, 11D)
wlan: 0.8.4.2 (Atheros/multi-bss)
ath_rate_atheros: Copyright (c) 2001-2005 Atheros Communications, Inc, All Rights Reserved
ath_dev: Copyright (c) 2001-2007 Atheros Communications, Inc, All Rights Reserved
ath_ahb: 0.9.4.5 (Atheros/multi-bss)
COEXIST is defined.
Howl Revision ID 0xb5 <6>No MBSSID aggregation support<6>wifi0: Atheros AR9100 WiSoC: mem=0xb80c0000, irq=2
wlan: mac acl policy registered
ieee80211_ioctl_setmode: CHH Mode: 11NGHT40MINUS
ath_set_config: Setting ATH parameter
ath_set_config: Setting ATH parameter
ath_set_config: Setting ATH parameter
ieee80211_ioctl_setparam: CHH Calling ieee80211_open
ieee80211_ioctl_setparam: CHH Calling ieee80211_open
ieee80211_ioctl_setparam: CHH Calling ieee80211_open
ieee80211_ioctl_setparam: CHH Calling ieee80211_open
device eth0 left promiscuous mode
br0: port 1(eth0) entering disabled state
device ath0 entered promiscuous mode
device eth0 entered promiscuous mode
br0: port 2(eth0) entering learning state
br0: topology change detected, propagating
br0: port 2(eth0) entering forwarding state
--AP ar5416InitUserSettings ahp->ah_miscMode 0xc
ar5416Reset Setting CFG 0x10a
Country ie is US 
ar5416StopDmaReceive: dma failed to stop in 10ms
AR_CR=0x00000024
AR_DIAG_SW=0x40000020
--AP ar5416InitUserSettings ahp->ah_miscMode 0xc
ar5416Reset Setting CFG 0x10a
br0: port 1(ath0) entering learning state
br0: topology change detected, propagating
br0: port 1(ath0) entering forwarding state
ath_netdev_stop: The stopping of the running
ar5416StopDmaReceive: dma failed to stop in 10ms
AR_CR=0x00000024
AR_DIAG_SW=0x40000020
br0: port 1(ath0) entering disabled state
ieee80211_ioctl_setparam: CHH Calling ieee80211_open
--AP ar5416InitUserSettings ahp->ah_miscMode 0xc
ar5416Reset Setting CFG 0x10a
Country ie is US 
br0: port 1(ath0) entering learning state
br0: topology change detected, propagating
br0: port 1(ath0) entering forwarding state

 TL-WR941N mips #37 Wed Apr 23 17:03:39 CST 2008 (none)
TL-WR941N login: ap71


BusyBox v1.01 (2008.04.22-03:29+0000) Built-in shell (msh)
Enter 'help' for a list of built-in commands.

$ 
$ cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00020000 00010000 "u-boot"
mtd1: 00100000 00010000 "kernel"
mtd2: 002c0000 00010000 "rootfs"
mtd3: 00010000 00010000 "config"
mtd4: 00010000 00010000 "art"
$ 
$ #press the qss button on front of router
$ Jumpstart button pressed.
registered routine return 1
$ cat /proc/interrupts
           CPU0       
  2:       5352            MIPS  wifi0
  4:        153            MIPS  eth0
  6:          0            MIPS  cascade
  7:      99060            MIPS  timer
 18:          0     AR7100 MISC  cascade
 19:        532     AR7100 MISC  serial
 35:          0     AR7100 GPIO  RESTORE_FACTORY_DEFAULT
 39:          4     AR7100 GPIO  SW_JUMPSTART

ERR:          0
$ cat /proc/iomem
00000000-01ffffff : System RAM
  00060000-00216587 : Kernel code
  00216588-0026f0bf : Kernel data
18020000-18020fff : serial8250.0
1b000000-1bffffff : ar7100-ehci.0
1c000000-1cffffff : ar7100-ohci.0
$ ls /proc
1              310            52             execdomains    mtd
10             311            58             filesystems    net
11             312            6              fs             partitions
173            315            62             interrupts     self
174            316            672            iomem          simple_config
178            317            7              ioports        slabinfo
183            318            8              irq            stat
2              319            9              kallsyms       sys
201            320            buddyinfo      kcore          sysvipc
3              321            bus            kmsg           tty
300            322            cmdline        loadavg        uptime
302            332            cpuinfo        locks          version
303            4              crypto         meminfo        vmstat
304            49             devices        misc           zoneinfo
305            5              diskstats      modules
306            51             driver         mounts
$ cat /proc/modules
wlan_acl 4576 0 - Live 0xc019d000
wlan_wep 6112 0 - Live 0xc00dd000
wlan_tkip 13408 0 - Live 0xc01b1000
wlan_ccmp 8416 0 - Live 0xc0199000
wlan_xauth 1344 0 - Live 0xc0160000
ath_ahb 49344 0 - Live 0xc01c3000
ath_dev 109840 1 ath_ahb, Live 0xc01d6000
ath_rate_atheros 39792 1 ath_dev, Live 0xc01a6000
wlan 228576 8 wlan_acl,wlan_wep,wlan_tkip,wlan_ccmp,wlan_xauth,ath_ahb,ath_dev, Live 0xc0127000
ath_hal 203664 3 ath_ahb,ath_dev, Live 0xc0166000
flashid 1344 0 - Live 0xc0108000
ts_kmp 2048 0 - Live 0xc0106000
ts_bm 2240 0 - Live 0xc00f6000
ipt_STAT 87344 0 - Live 0xc010a000
ipt_TCPMSS 3808 1 - Live 0xc00ed000
ip_nat_pptp 5264 0 - Live 0xc00f3000
ip_conntrack_pptp 8944 1 ip_nat_pptp, Live 0xc00ef000
ip_nat_h323 6912 0 - Live 0xc00e3000
ip_conntrack_h323 48736 1 ip_nat_h323, Live 0xc00f9000
ipt_TRIGGER 3552 0 - Live 0xc00e8000
ipt_time 2624 0 - Live 0xc00e6000
iptable_filter 2304 1 - Live 0xc00d5000
iptable_nat 7920 1 - Live 0xc00e0000
ipt_string 1728 0 - Live 0xc00d9000
ipt_state 1472 2 - Live 0xc00d7000
ipt_multiport 2336 0 - Live 0xc00b6000
ipt_mac 1696 0 - Live 0xc00d3000
ipt_iprange 1568 0 - Live 0xc00c3000
ipt_conntrack 2304 0 - Live 0xc00c1000
ipt_comment 1312 1 - Live 0xc00b8000
ipt_MASQUERADE 2752 1 - Live 0xc00a3000
ip_nat_tftp 1312 0 - Live 0xc00b4000
ip_nat_ftp 2976 0 - Live 0xc009a000
ip_nat 16896 7 ip_nat_pptp,ip_nat_h323,ipt_TRIGGER,iptable_nat,ipt_MASQUERADE,ip_nat_tftp,ip_nat_ftp, Live 0xc00bb000
ip_conntrack_tftp 3376 1 ip_nat_tftp, Live 0xc00a1000
ip_conntrack_ftp 6512 1 ip_nat_ftp, Live 0xc009e000
ip_conntrack 48064 13 ip_nat_pptp,ip_conntrack_pptp,ip_nat_h323,ip_conntrack_h323,iptable_nat,ipt_state,ipt_conntrack,ipt_MASQUERADE,ip_nat_tftp,ip_nat_ftp,ip_nat,ip_conntrack_tftp,ip_conntrack_ftp, Live 0xc00c6000
ip_tables 22656 13 ipt_TCPMSS,ipt_TRIGGER,ipt_time,iptable_filter,iptable_nat,ipt_string,ipt_state,ipt_multiport,ipt_mac,ipt_iprange,ipt_conntrack,ipt_comment,ipt_MASQUERADE, Live 0xc00ad000
ag7100_mod 25824 0 - Live 0xc00a5000
$ cat /proc/partitions
major minor  #blocks  name

  31     0        128 mtdblock0
  31     1       1024 mtdblock1
  31     2       2816 mtdblock2
  31     3         64 mtdblock3
  31     4         64 mtdblock4
$ cat /proc/iomem
00000000-01ffffff : System RAM
  00060000-00216587 : Kernel code
  00216588-0026f0bf : Kernel data
18020000-18020fff : serial8250.0
1b000000-1bffffff : ar7100-ehci.0
1c000000-1cffffff : ar7100-ohci.0
$ 
$ path_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
--AP ar5416InitUserSettings ahp->ah_miscMode 0xc
ar5416Reset Setting CFG 0x10a

===================
Info on the USB port from Lark on dd-wrt forum:
http://www.dd-wrt.com/phpBB2/viewtopic. … p;start=21

He was playing around with the factory firmware 2.6.15 and compiling modules for it:

0 Dec 2004 USB 2.0 'Enhanced' Host Controller (EHCI) Driver (AR7100_EHCI)
In ar7100_ehci_drv_probe
probing ehci...
hcd->regs is 0xbb000000
/home/TEW-652BRP/TEW-652BRP_GPL/platform/AR9100/kernels/mips-linux-2.6.15/drivers/usb/host/ehci-ar7100.c: starting AR7100 EHCI USB Controller...done. reset 0x0 usb config 0x2
ehci->caps is 0xbb000000
ehci->caps->hc_base is 0x42fa05
ar7100-ehci ar7100-ehci.0: AR7100 EHCI
ar7100-ehci ar7100-ehci.0: new USB bus registered, assigned bus number 1
ar7100-ehci ar7100-ehci.0: irq 3, io mem 0x1b000000
hcc_params addr 0xbb000008 val 0x10020001 hcs_params addr 0xbb000004 val 0x22
ar7100-ehci ar7100-ehci.0: USB 0.0 started, EHCI 0.42, driver 10 Dec 2004
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
...probing done
2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (ar7100_ohci)block sizes: ed 64 td 64
In ohci_hcd_ar7100_drv_probeprobing...
/home/TEW-652BRP/TEW-652BRP_GPL/platform/AR9100/kernels/mips-linux-2.6.15/drivers/usb/host/ohci-ar7100.c: starting AR7100 OHCI USB Controller...<6>ar7100-ohci ar7100-ohci.0: AR7100 OHCI
ar7100-ohci ar7100-ohci.0: new USB bus registered, assigned bus number 2
ar7100-ohci ar7100-ohci.0: irq 22, io mem 0x1c000000
ar7100-ohci ar7100-ohci.0: init err (00000000 0038)
/home/TEW-652BRP/TEW-652BRP_GPL/platform/AR9100/kernels/mips-linux-2.6.15/drivers/usb/host/ohci-ar7100.c: can't start ar7100_usb
ar7100-ohci ar7100-ohci.0: startup error -79
ar7100-ohci ar7100-ohci.0: USB bus 2 deregistered
/home/TEW-652BRP/TEW-652BRP_GPL/platform/AR9100/kernels/mips-linux-2.6.15/drivers/usb/host/ohci-ar7100.c: stopping ar7100 OHCI USB Controller
ar7100-ohci: probe of ar7100-ohci.0 failed with error -79

(Last edited by RoundSparrow on 10 Apr 2011, 07:18)

15 Jan 2009, 01:18

From dd-wrt forums, Pin Connection. UPDATE: I now confirm this all works correctly.

Pin, 3.3v serial
2 RX
3 TX
4 VCC (+3.3v)
5 Gnd

You only need RX, TX, Gnd. u-boot is at 9600-8N1, kernel is at 115200-8N1. Pin #1 is clearly marked P1 with a triangle.

Pin assignments:

----[]-->
9 7 5 3 1
A 8 6 4 2

This router is a pain due to need to bridge the R356 pad adjacent to the serial port. These are small surface mount pads and not real easy to solder or pencil. See the later photos in the thread.

(Last edited by RoundSparrow on 9 Feb 2009, 19:46)

16 Jan 2009, 19:43

Ok, in my early attempts I damaged the bridge solder pads for the rs232 and I've been trying my best to salvage them... but too late. I had it working for a few hours but was flaky and attempts to shore it up pretty much ended it for good. The router is still working, but no rs232 on this unit for me.

I am tempted to table this TP-Link for now. At least until someone else wants to work actively on porting OpenWRT to it. It is a nice AP81, but until the price is discounted or on sale here in the USA, I'll hold off. For similar price ($60) I can get the Planex router from Amazon.com that has a simpler to solder rs232, USB port attached, and 8MB of flash instead of 4MB. I expect the TP-Link will be more available (better product distribution, worldwide and with retailers in the USA) and go on discount prices - but not feeling a lot of rush. The $25 Trendnet with 2x2 MIMO seem like a good thing to focus on, and the Planex routers should satisfy the need to see how the 3x3 MIMO and USB works on this platform.

If anyone else is serious about OpenWRT on the TP-Link (we have to work out the way to flash, right now only working with ramdisk image and u-boot tftpboot) - let me know, and I may order a second on and get the rs232 soldering right with my now-gained experience.

(Last edited by RoundSparrow on 16 Jan 2009, 19:50)

9 Feb 2009, 08:06

Ok, I unboxed another one, I'm a glutton for punishment. Good news is I got the serial correct the first time!

Here is microscope photo of the surface mount pad you have to bridge. R356, the 3rd one down from top (or 2nd one up from the bottom). This is the ONLY one you need to bridge for the serial to work.

Now to bridge this, I used liquid metal. In the USA, the easiest way to get this is to go to a automotive parts store and buy a rear window defogger repair kit. Inside you will get a bottle of copper particles suspended in solvent. I used a fine point toothpick to drip a couple drops right between the pads, got it right the first time! It is easy to clean off excess after it dries (1 minute) with a clean toothpick tip.

Here is a picture with liquid copper applied, I did not clean this up any way, it is good enough for me Looks messy, but not touching any other pads.

I suppose the AMD overclocking pencil trick (graphite electronic conduit) would also work, but I didn't have any pencils around

(Last edited by RoundSparrow on 9 Feb 2009, 08:19)

9 Feb 2009, 08:54

interestingly, the u-boot is missing the 'saveenv' command, so I can't change the baud rate to 115200 to match Linux boot. Oh well.

If you boot the original vendor firmware (kernel 2.6.15 download .bin from TP-Link website)... you can login to get root with the username "ap71". Thank Lark for that information.

(Last edited by RoundSparrow on 9 Feb 2009, 19:57)

9 Feb 2009, 17:41

ugh, I've tried to use Lark's knowledge of reworking the original firmware to try and tftpboot OpenWRT. I just getting nothing after it says Starting Kernel.... it just dies. See here: http://download.lark.net.cn/wr941n/hack/

Anyone who knows a lot more than me about the Kernel on these MIPS, please chime in with tips and ideas

Pastebin with some dumps of factory (that works) and OpenWRT that hangs. http://openwrt.pastebin.com/f5fce4294 and http://openwrt.pastebin.com/f74dab33e

(Last edited by RoundSparrow on 9 Feb 2009, 17:54)

9 Feb 2009, 19:25

RoundSparrow wrote:

ugh, I've tried to use Lark's knowledge of reworking the original firmware to try and tftpboot OpenWRT. I just getting nothing after it says Starting Kernel.... it just dies. See here: http://download.lark.net.cn/wr941n/hack/
Anyone who knows a lot more than me about the Kernel on these MIPS, please chime in with tips and ideas
Pastebin with some dumps of factory (that works) and OpenWRT that hangs. http://openwrt.pastebin.com/f5fce4294 and http://openwrt.pastebin.com/f74dab33e

It is really good news you got this far! I was feeling guilty because my WR941ND was just sitting on the desk... I'm not as good as you with a soldering iron.

Sorry if this is a stupid suggestion, but it's not that the baudrate is different? I did this mistake once with redboot and linux on different baudrates and it looked like the kernel just died (in fact it booted perfectly of course).

Please tell me if I can help out in any way! I have 941 that I'm willing to risk.

9 Feb 2009, 19:33

_bbb_ wrote:

It is really good news you got this far! I was feeling guilty because my WR941ND was just sitting on the desk... I'm not as good as you with a soldering iron.
Sorry if this is a stupid suggestion, but it's not that the baudrate is different? I did this mistake once with redboot and linux on different baudrates and it looked like the kernel just died (in fact it booted perfectly of course).
Please tell me if I can help out in any way! I have 941 that I'm willing to risk.

I really don't have much clue what I'm doing, I'm learning through trial and error and re-reading all the existing information I can find. Lark on dd-wrt forums really did the legwork here, but he put it aside in December and was really more focused on using the existing 2.6.15 kernel.

The key thing that baffles me:

1) You can download the firmware update for the router from TP-Link website. Intercept u-boot (serial connection required) and tftpboot the original firmware .bin file - and at least the kernel starts. Yes, the baud rate changes, but at 9600 you see the scrambled serial output. Switching baud rate to 115200 will get you the boot log (and see it crash, this file wasn't really made to be tftpboot, but it proves it is possible).

2) I try to create my own OpenWRT kernel using the same assembly steps that Lark put together - and it just produces NO OUTPUT of any kind. Switching baud rate to 115200 yields nothing.

So something is missing here or I'm doing something wrong.

P.S. On the soldering, there are only 3 wires to solder. I suggest using cat5/cat6 Ethernet wire (the inside wires), about 4 inch piece with a little bit of the insulator removed. You heat up the serial port solder pin pad and stick the solid wire in gently (so it doesn't bend). There is already spare solder on these pads, so it isn't that hard. Then you can connect your serial device to the other end of this solid Ethernet wire. As for the tiny R356 pads you have to bridge - I suggest the liquid copper and toothpick... as that's nearly impossible to solder Maybe enlist a local friend at a users group or something?

(Last edited by RoundSparrow on 9 Feb 2009, 19:40)

10 Feb 2009, 00:09

ok, so on tp-link firmware I notice:
Serial: 8250/16550 driver $Revision: #1 $ 1 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x0 (irq = 19) is a 16550A

On trendnet and d-link router I notice:
Serial: 8250/16550 driver $Revision: 1.1.1.1 $ 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x0 (irq = 19) is a 16550A

On Netgear WNR2000 I notice:
Serial: 8250/16550 driver $Revision: 1.90 $ 1 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11) is a 16550A

On the TP-Link, my console dies on kernel boot... it come to me that perhaps the serial port is the cause! As something weird with how tp-link chooses to go 9600bps on u-boot when all other AP81's use 115200. And the factory firmware emits a unique message that the other AP81's do not. Although the Netgear is unique too, and it works fine with OpenWRT kernel (but it runs forked OpenWRT white Russian for factory firmare).

Can I tell OpenWRT to not touch serial port for console?

11 Feb 2009, 16:13

Any progress?

Perhaps I could help by putting my router in the mail to one of the big guns? Gabor?

11 Feb 2009, 18:30

Hi,

_bbb_ wrote:

Any progress?

We are still fighting with it.

Perhaps I could help by putting my router in the mail to one of the big guns? Gabor?

That would be really nice.

Gabor

12 Feb 2009, 14:50

It's in the mail.

12 Feb 2009, 15:20

_bbb_ wrote:

It's in the mail.

Thank you!

Gabor

12 Feb 2009, 15:49

This router is proving to be nothing but a pain due to the crippled u-boot. Attempts to boot OpenWRT kernel have all failed. All OpenWRT users are encouraged to contact tp-link and request GPL source code for their changes to u-boot. So far, they have refused requests.

12 Feb 2009, 15:58

RoundSparrow wrote:

This router is proving to be nothing but a pain due to the crippled u-boot. Attempts to boot OpenWRT kernel have all failed.

I bet we will solve this sooner or later.

All OpenWRT users are encouraged to contact tp-link and request GPL source code for their changes to u-boot. So far, they have refused requests.

This is an additional reason why we should put OpenWrt onto this board.

Gabor

19 Feb 2009, 12:27

All OpenWRT users are encouraged to contact tp-link and request GPL source code for their changes to u-boot. So far, they have refused requests.

I just downloaded the gpl file for TL-WR941ND.It seems to be a new one from last night. See:
http://www.tp-link.com/support/gpl.asp

And there is an u-boot folder in it...
Not quite sure if there are all changes included, but i think it's worth a look.

Sebastian

(Last edited by prisma on 19 Feb 2009, 13:49)

22 Feb 2009, 17:19

Hi,

_bbb_ wrote:

It's in the mail.

I have got the packet yesterday. Thank you.

Regards,
Gabor

23 Feb 2009, 00:45

Gabor checked in preliminary changes to OpenWRT trunk! Thank you _bbb_ and Gabor.

Gabor reports that LAN and WAN are not yet working..

As for tftpboot, here is the trick: ar7100> tftp 0xa0060000 openwrt-ar71xx-vmlinux-initramfs.bin; go 0xa0060000

(Last edited by RoundSparrow on 23 Feb 2009, 01:28)

23 Feb 2009, 13:25

Gabor is quick! Ethernet devices should be working: https://dev.openwrt.org/changeset/14637/trunk

Comment: TP-Link opted to use only one of the Ethernet interfaces provided by the CPU and let the switch do the logical split between LAN and WAN port. I speculate... doing full duplex transfers between LAN and WAN, this means you could run into situations where the same CPU Ethernet interface (eth0) is used to traverse WAN to LAN... I mention this as some of the other AP81 routers using both ports have been benchmarked as capable of 95Mbps WAN to LAN (Trendnet TEW-652BRP). This particular router design may not do as well. I have not benchmarked the TP-Link, just pointing out the issue. I know some people have been seeking this platform for the 400Mhz CPU and capability to saturate the Ethernet.

(Last edited by RoundSparrow on 23 Feb 2009, 13:57)

24 Feb 2009, 23:16

juhosg wrote:

I have got the packet yesterday. Thank you.
Regards,
Gabor

You are more than welcome!

24 Feb 2009, 23:18

Any chance this device can be reflashed with openwrt from the tp-link webgui?

If so I'm getting another one to play with!

26 Feb 2009, 18:18

_bbb_ wrote:

Any chance this device can be reflashed with openwrt from the tp-link webgui?
If so I'm getting another one to play with!

It can now! Gabor just checked in his work for this today. Now I'd be a bit cautious... as not a recovery mode like the Trendnets - and nobody reports details of an AP81 JTAG recovery

I'm going to try mine out today.

27 Feb 2009, 17:31

RoundSparrow wrote:

_bbb_ wrote:
Any chance this device can be reflashed with openwrt from the tp-link webgui?
If so I'm getting another one to play with!
It can now! Gabor just checked in his work for this today. Now I'd be a bit cautious... as not a recovery mode like the Trendnets - and nobody reports details of an AP81 JTAG recovery
I'm going to try mine out today.

Excellent! I will order one right away.

Keep us posted!

27 Feb 2009, 17:40

_bbb_ wrote:

RoundSparrow wrote:
_bbb_ wrote:
Any chance this device can be reflashed with openwrt from the tp-link webgui?
If so I'm getting another one to play with!
It can now! Gabor just checked in his work for this today. Now I'd be a bit cautious... as not a recovery mode like the Trendnets - and nobody reports details of an AP81 JTAG recovery
I'm going to try mine out today.
Excellent! I will order one right away.
Keep us posted!

If you are in the USA or Japan, I strongly encourage you to spend the extra $15 on the Planex U-boot is healthy, flash is 2x the size, the LAN and WAN don't share a common network interface, the USB port is populated, and the serial port is easier to solder in.

PLUS, it has all the good aspects of the TP-Link

28 Feb 2009, 14:26

RoundSparrow wrote:

_bbb_ wrote:
RoundSparrow wrote:
It can now! Gabor just checked in his work for this today. Now I'd be a bit cautious... as not a recovery mode like the Trendnets - and nobody reports details of an AP81 JTAG recovery
I'm going to try mine out today.
Excellent! I will order one right away.
Keep us posted!
If you are in the USA or Japan, I strongly encourage you to spend the extra $15 on the Planex U-boot is healthy, flash is 2x the size, the LAN and WAN don't share a common network interface, the USB port is populated, and the serial port is easier to solder in.
PLUS, it has all the good aspects of the TP-Link

Good point. I'm in Sweden (EU country) though... The Swedish importer doesn't carry the exact Planex model that OpenWrt runs on.

Also, I don't really like the "stand up router" form factor. Is it possible to put the Planex down flat on its side? I mean does it have some sort of pads or something that makes is reasonable to place it flat?

How do you mean U-boot is healthy? Does it have U-boot recovery mode with reflash over http?

How well is OpenWrt working in the Planex? Is it as "plug and play" as the Trendnet TEW-632 or do I have to solder that serial port?

Is the wireless performance as good as the tp-link? I was really impressed with tp-link coverage/throughput (with original firmware)...