Topic: TP-Link TD-W8960N and OpenWRT

Hi everyone

I'd love to have a play around with OpenWRT and see what it can do, however I notice my router (TD-W8960N) is listed in the "Possible, but not being worked on" section of the supported hardware list.

Given that I have compiled a version of Backfire with what looks like the correct targets for the chipsets in the machine, what would then prevent this from being recognised as a valid image by the router's webUI? Has anyone ever had any luck getting OpenWRT onto this model of router? I was hoping to save tftp for debricking the router when I inevitably do something stupid to it, but would that be a more reliable method of flashing it in the first instance?

Looking through the supported hardware list, I notice that the DSL2740 has *very* similar specifications. Would that make it a good candidate for attempting a flash?

Thanks for any suggestions.

PS - please don't put me in with the Stupids on Common Mistakes.

Re: TP-Link TD-W8960N and OpenWRT

http://wiki.openwrt.org/doc/howto/generic.flashing

Re: TP-Link TD-W8960N and OpenWRT

openwrt ran on this router but not working properly.

I have described here some logs from the run openwrt on the router.
http://openrouter.info/forum/viewtopic.php?f=18&t=582
http://openrouter.info/index.php?option … ;Itemid=55

first problem is not detecting the flash memory.

0x80010000/2609160 0x8028d008/167336 Entry at 0x80206970
Closing network.
Closing DMA Channels.
Starting program at 0x80206970
Linux version 2.6.37.6 (rcichosz@ubuntu) (gcc version 4.5.2 (Linaro GCC 4.5-2011.02-0) ) #1 Thu May 5 19:58:06 CEST 2011
Detected Broadcom 0x6358 CPU revision a1
CPU frequency is 300 MHz
32MB of RAM installed
registering 40 GPIOs
board_bcm963xx: CFE version: unknown
bootconsole [early0] enabled
CPU revision is: 0002a010 (Broadcom BMIPS4350)
board_bcm963xx: board name: 96358VW2
Determined physical RAM map:
memory: 02000000 @ 00000000 (usable)
Initrd not found or empty - disabling initrd
Zone PFN ranges:
Normal   0x00000000 -> 0x00002000
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0x00000000 -> 0x00002000
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 8128
Kernel command line:  root=/dev/mtdblock2 rootfstype=squashfs,jffs2 noinitrd console=ttyS0,115200
PID hash table entries: 128 (order: -3, 512 bytes)
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Primary instruction cache 32kB, VIPT, 2-way, linesize 16 bytes.
Primary data cache 16kB, 2-way, VIPT, cache aliases, linesize 16 bytes
Memory: 29648k/32768k available (2045k kernel code, 3120k reserved, 340k data, 164k init, 0k highmem)
NR_IRQS:128
Calibrating delay loop... 299.00 BogoMIPS (lpj=598016)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
NET: Registered protocol family 16
registering PCI controller with io_map_base unset
bio: create slab at 0
pci 0000:00:01.0: BAR 0: assigned [mem 0x30000000-0x30003fff]
pci 0000:00:01.0: BAR 0: set to [mem 0x30000000-0x30003fff] (PCI address [0x30000000-0x30003fff])
Switching to clocksource MIPS
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
audit: initializing netlink socket (disabled)
type=2000 audit(0.220:1): initialized
squashfs: version 4.0 (2009/01/31) Phillip Lougher
JFFS2 version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
msgmni has been set to 57
io scheduler noop registered
io scheduler deadline registered (default)
gpiodev: gpio device registered with major 254
bcm63xx_uart.0: ttyS0 at MMIO 0xfffe0100 (irq = 10) is a bcm63xx_uart
console [ttyS0] enabled, bootconsole disabled
console [ttyS0] enabled, bootconsole disabled
bcm963xx-flash bcm963xx-flash.0: 0x00400000 at 0x1fc00000
bcm963xx-flash bcm963xx-flash.0: failed to probe using CFI
bcm963xx-flash: probe of bcm963xx-flash.0 failed with error -5
bcm63xx_enet MII bus: probed
bcm63xx-wdt bcm63xx-wdt.0:  started, timer margin: 30 sec
TCP westwood registered
NET: Registered protocol family 17
802.1Q VLAN Support v1.8 Ben Greear
All bugs added by David S. Miller
VFS: Cannot open root device "mtdblock2" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

Re: TP-Link TD-W8960N and OpenWRT

Thanks rpc, sadly it is outside of my ability to even start thinking about getting OpenWrt to access the flash.

I guess my only option is to wait for someone else to do it, although if they haven't yet I'm guessing it's increasingly unlikely that anyone ever will.

Re: TP-Link TD-W8960N and OpenWRT

According to https://dev.openwrt.org/ticket/10666 td-w8960n is already supported.
Did anyone tried flashing the new builds? I would do that, but that's my only router and I would be alone on the debugging process.

Re: TP-Link TD-W8960N and OpenWRT

Ok... don't flash any build. My router bricked, I'm waiting for a serial ttl adapter to debug the device. bootloader still works (one ping response with ttl=100, but it doesn't accept any file via tftp).

7 (edited by TigTex 2012-09-26 18:18:54)

Re: TP-Link TD-W8960N and OpenWRT

A year after, w8960n isn't still supported. This is the latest log (kernel panic -> flash not detected)

CFE version 1.0.37-102.9 for BCM96358 (32bit,SP,BE)
Build Date: å  5 09:42:18 CST 2010 (root@localhost.localdomain)
Copyright (C) 2000-2009 Broadcom Corporation.

Serial flash device: name S25FL032A, id 0x0115, size 4096KB
CPU type 0x2A010: 300MHz, Bus: 133MHz, Ref: 64MHz
CPU running TP0
Total memory: 33554432 bytes (32MB)
Boot Address 0xbfc00000


Board IP address                  : 192.168.1.1:ffffff00
Host IP address                   : 192.168.1.100
Gateway IP address                :
Run from flash/host (f/h)         : f
Default host run file name        : vmlinux
Default host flash file name      : bcm963xx_fs_kernel
Boot delay (0-9 seconds)          : 1
Board Id (0-5)                    : 96358VW2
Number of MAC Addresses (1-32)    : 11
Base MAC Address                  : #####
PSI Size (1-64) KBytes            : 24
Main Thread Number [0|1]          : 0
Device Pin                        : "#####"

*** Press any key to stop auto run (1 seconds) ***
Auto run second count down: 0
Booting from only image (0xbfc10000) ...
Code Address: 0x80010000, Entry Address: 0x80010000
LZMA: Prossible old LZMA format, trying to decompress..
Decompression OK!
Entry at 0x80010000
Closing network.
Closing DMA Channels.
Starting program at 0x80010000
[    0.000000] Linux version 3.3.8 (fnord@tschunk) (gcc version 4.6.3 20120201 (prerelease) (Linaro GCC 4.6-2012.02) ) #1 Thu Aug 30 04:51:08 UTC 2012
[    0.000000] Detected Broadcom 0x6358 CPU revision a1
[    0.000000] CPU frequency is 300 MHz
[    0.000000] 32MB of RAM installed
[    0.000000] registering 40 GPIOs
[    0.000000] gpiochip_add: registered GPIOs 0 to 39 on device: bcm63xx-gpio
[    0.000000] board_bcm963xx: Boot address 0xbfc00000
[    0.000000] board_bcm963xx: CFE version: unknown
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU revision is: 0002a010 (Broadcom BMIPS4350)
[    0.000000] board_bcm963xx: board name: 96358VW2
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 02000000 @ 00000000 (usable)
[    0.000000] Initrd not found or empty - disabling initrd
[    0.000000] Zone PFN ranges:
[    0.000000]   Normal   0x00000000 -> 0x00002000
[    0.000000] Movable zone start PFN for each node
[    0.000000] Early memory PFN ranges
[    0.000000]     0: 0x00000000 -> 0x00002000
[    0.000000] Reserving 0MB of memory at 0MB for crashkernel
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 8128
[    0.000000] Kernel command line:  root=/dev/mtdblock2 rootfstype=squashfs,jffs2 noinitrd console=ttyS0,115200
[    0.000000] PID hash table entries: 128 (order: -3, 512 bytes)
[    0.000000] Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Primary instruction cache 32kB, VIPT, 2-way, linesize 16 bytes.
[    0.000000] Primary data cache 16kB, 2-way, VIPT, cache aliases, linesize 16 bytes
[    0.000000] Memory: 28968k/32768k available (2365k kernel code, 3800k reserved, 663k data, 204k init, 0k highmem)
[    0.000000] NR_IRQS:128
[    0.000000] Calibrating delay loop... 299.26 BogoMIPS (lpj=598528)
[    0.036000] pid_max: default: 32768 minimum: 301
[    0.040000] Mount-cache hash table entries: 512
[    0.048000] NET: Registered protocol family 16
[    0.060000] registering PCI controller with io_map_base unset
[    0.064000] registering PCI controller with io_map_base unset
[    0.080000] bio: create slab <bio-0> at 0
[    0.088000] PCI host bridge to bus 0000:00
[    0.092000] pci_bus 0000:00: root bus resource [mem 0x30000000-0x37ffffff]
[    0.096000] pci_bus 0000:00: root bus resource [io  0x8000000-0x8007fff]
[    0.112000] pci 0000:00:01.0: BAR 0: assigned [mem 0x30000000-0x30003fff]
[    0.116000] PCI host bridge to bus 0000:01
[    0.120000] pci_bus 0000:01: root bus resource [mem 0x38000000-0x3fffffff]
[    0.124000] pci_bus 0000:01: root bus resource [io  0x8008000-0x800ffff]
[    0.128000] pci 0000:01:1e.0: CardBus bridge to [bus 02-05]
[    0.132000] pci 0000:01:1e.0:   bridge window [io  0x0001-0x0000]
[    0.136000] pci 0000:01:1e.0:   bridge window [io  0x0001-0x0000]
[    0.140000] pci 0000:01:1e.0:   bridge window [mem 0x00000001-0x00000000]
[    0.144000] PCI: Enabling device 0000:01:1e.0 (0000 -> 0003)
[    0.148000] Switching to clocksource MIPS
[    0.160000] NET: Registered protocol family 2
[    0.164000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.172000] TCP established hash table entries: 1024 (order: 1, 8192 bytes)
[    0.180000] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    0.188000] TCP: Hash tables configured (established 1024 bind 1024)
[    0.192000] TCP reno registered
[    0.196000] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.204000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.208000] NET: Registered protocol family 1
[    0.220000] audit: initializing netlink socket (disabled)
[    0.224000] type=2000 audit(0.224:1): initialized
[    0.232000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.236000] JFFS2 version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.248000] msgmni has been set to 56
[    0.252000] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
[    0.260000] io scheduler noop registered
[    0.264000] io scheduler deadline registered (default)
[    0.272000] bcm63xx_uart.0: ttyS0 at MMIO 0xfffe0100 (irq = 10) is a bcm63xx_uart
[    0.280000] console [ttyS0] enabled, bootconsole disabled
[    0.280000] console [ttyS0] enabled, bootconsole disabled
[    0.304000] bcm63xx_enet MII bus: probed
[    0.308000] bcm63xx_enet bcm63xx_enet.0: attached PHY at address 1 [Broadcom BCM63XX (2)]
[    0.324000] bcm63xx-wdt bcm63xx-wdt:  started, timer margin: 30 sec
[    0.332000] TCP cubic registered
[    0.336000] NET: Registered protocol family 17
[    0.340000] Bridge firewalling registered
[    0.344000] 8021q: 802.1Q VLAN Support v1.8
[    0.352000] VFS: Cannot open root device "mtdblock2" or unknown-block(0,0)
[    0.360000] Please append a correct "root=" boot option; here are the available partitions:
[    0.368000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

I would like to help on this, but I need help from more users/developers. The latest oficial firmware from tplink has some serious bugs (tcp connections are closed randomly) and openwrt would be perfect on this device!

edit: I've updated the wiki page with all the info that I've learned from this router. You can see it here http://wiki.openwrt.org/toh/tp-link/td-w8960n

Re: TP-Link TD-W8960N and OpenWRT

What's the latest on this device? Still not working / bricking?
I have a hardware v4 of this and I would like to install OpenWRT in order to setup OpenVPN (default VPN for TP-Link software seems to only allow modem-to-modem VPN and no VPN client setup.

Thanks.

TP-Link WR1043ND  v1.8

9 (edited by Beeblebrox 2013-02-19 13:01:04)

Re: TP-Link TD-W8960N and OpenWRT

v4 Hardware seems different. Bootloader - BCM96345 / CPU - BCM63281 / Radio - BCM43227.
Full boot log output from serial below.

HELO
CPUI
L1CI
DRAM
----
PHYS
ZQDN
PHYE
DINT
LSYN
USYN
MSYN
LMBE
PASS
----
ZBSS
CODE
DATA
L12F
MAIN


CFE version 1.0.37-110.11 for BCM96328 (32bit,SP,BE)
Build Date: � 5�..  3 13:29:53 CST 2012 (root@localhost.localdomain)
Copyright (C) 2000-2009 Broadcom Corporation.

HS Serial flash device: name EN25P64, id 0x1c17 size 8192KB
Total Flash size: 8192K with 128 sectors
Light all CPU's LEDs for LED Test.
Chip ID: BCM6328B0, MIPS: 320MHz, DDR: 320MHz, Bus: 160MHz
Main Thread: TP0
Memory Test Passed
Total Memory: 67108864 bytes (64MB)
Boot Address: 0xb8000000

Board IP address                  : 192.168.1.1:ffffff00  
Host IP address                   : 192.168.1.100  
Gateway IP address                :   
Run from flash/host (f/h)         : f  
Default host run file name        : vmlinux  
Default host flash file name      : bcm963xx_fs_kernel  
Boot delay (0-9 seconds)          : 1  
Board Id (0-5)                    : 963281TAN  
Number of MAC Addresses (1-32)    : 11  
Base MAC Address                  : xxxxxxxxxxxx
PSI Size (1-64) KBytes            : 56  
Enable Backup PSI [0|1]           : 0  
System Log Size (0-256) KBytes    : 0  
Main Thread Number [0|1]          : 0  
Device Pin                        : "49407099"  

*** Press any key to stop auto run (1 seconds) ***
Auto run second count down: 0
Booting from only image (0xb8010000) ...
Code Address: 0x80010000, Entry Address: 0x802273f0
Decompression OK!
Entry at 0x802273f0
Closing network.
Disabling Switch ports.
Flushing Receive Buffers...
0 buffers found.
Closing DMA Channels.
Starting program at 0x802273f0
Linux version 2.6.30 (root@localhost.localdomain) (gcc version 4.4.2 (Buildroot 2010.02
HS Serial flash device: name EN25P64, id 0x1c17 size 8192KB
963281TAN prom init
CPU revision is: 0002a075 (Broadcom4350)
Determined physical RAM map:
 memory: 03f00000 @ 00000000 (usable)
Zone PFN ranges:
  DMA      0x00000000 -> 0x00001000
  Normal   0x00001000 -> 0x00003f00
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
    0: 0x00000000 -> 0x00003f00
On node 0 totalpages: 16128
free_area_init_node: node 0, pgdat 802bcec0, node_mem_map 81000000
  DMA zone: 32 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 4064 pages, LIFO batch:0
  Normal zone: 94 pages used for memmap
  Normal zone: 11938 pages, LIFO batch:1
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16002
Kernel command line: root=31:0 ro noinitrd console=ttyS0,115200
wait instruction: enabled
Primary instruction cache 32kB, VIPT, 4-way, linesize 16 bytes.
Primary data cache 32kB, 2-way, VIPT, cache aliases, linesize 16 bytes
NR_IRQS:128
PID hash table entries: 256 (order: 8, 1024 bytes)
console [ttyS0] enabled
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 60776k/64512k available (2164k kernel code, 3716k reserved, 581k data, 116k in)
Calibrating delay loop... 319.48 BogoMIPS (lpj=159744)
Mount-cache hash table entries: 512
--Kernel Config--
  SMP=0
  PREEMPT=0
  DEBUG_SPINLOCK=0
  DEBUG_MUTEXES=0
Broadcom Logger v0.1 Sep 12 2012 17:42:29
net_namespace: 812 bytes
NET: Registered protocol family 16
Total Flash size: 8192K with 128 sectors
registering PCI controller with io_map_base unset
registering PCI controller with io_map_base unset
bio: create slab <bio-0> at 0
pci 0000:01:00.0: PME# supported from D0 D3hot
pci 0000:01:00.0: PME# disabled
pci 0000:02:00.0: reg 10 64bit mmio: [0x000000-0x003fff]
pci 0000:02:00.0: supports D1 D2
pci 0000:01:00.0: PCI bridge, secondary bus 0000:02
pci 0000:01:00.0:   IO window: disabled
pci 0000:01:00.0:   MEM window: 0x10f00000-0x10ffffff
pci 0000:01:00.0:   PREFETCH window: disabled
PCI: Enabling device 0000:01:00.0 (0000 -> 0002)
PCI: Setting latency timer of device 0000:01:00.0 to 64
BLOG v3.0 Initialized
BLOG Rule v1.0 Initialized
Broadcom IQoS v0.1 Sep 12 2012 17:46:21 initialized
Broadcom GBPM v0.1 Sep 12 2012 17:46:21 initialized
NET: Registered protocol family 8
NET: Registered protocol family 20
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
NET: Registered protocol family 1
squashfs: version 4.0 (2009/01/31) Phillip Lougher
squashfs: version 4.0 with LZMA457 ported by BRCM
msgmni has been set to 118
io scheduler noop registered (default)
pcieport-driver 0000:01:00.0: device [14e4:6328] has invalid IRQ; check vendor BIOS
PCI: Setting latency timer of device 0000:01:00.0 to 64
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
NET: Registered protocol family 24
bcm963xx_mtd driver v1.0
File system address: 0xb8010100
brcmboard: brcm_board_init entry
SES: Button Interrupt 0x1 is enabled
SES: LED GPIO 0x8009 is enabled
irq.c: reset_fac_irq is set to low_trigger.
irq.c: reset_fac_irq is set to low_trigger.
Serial: BCM63XX driver $Revision: 3.00 $
Magic SysRq enabled (type ^ h for list of supported commands)
ttyS0 at MMIO 0xb0000100 (irq = 36) is a BCM63XX
ttyS1 at MMIO 0xb0000120 (irq = 47) is a BCM63XX
Total # RxBds=2416
bcmPktDmaBds_init: Broadcom Packet DMA BDs initialized

bcmxtmrt: Broadcom BCM6328B0 ATM/PTM Network Device v0.3 Sep 12 2012 17:45:46
GACT probability NOT on
Mirror/redirect action on
u32 classifier
    input device check on 
    Actions configured 
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 17
NET: Registered protocol family 15
Initializing MCPD Module
Ebtables v2.0 registered
ebt_time registered
ebt_ftos registered
ebt_wmm_mark registered
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
VFS: Mounted root (squashfs filesystem) readonly on device 31:0.
Freeing unused kernel memory: 116k freed
init started:  BusyBox v1.00 (2012.09.13-00:50+0000) multi-call binary


BusyBox v1.00 (2012.09.13-00:50+0000) Built-in shell (msh)
Enter 'help' for a list of built-in commands.


Loading drivers and kernel modules... 

bcm_ingqos: module license 'Proprietary' taints kernel.
Disabling lock debugging due to kernel taint
Broadcom Ingress QoS Module  Char Driver v0.1 Sep 12 2012 17:44:22 Registered<243>

Broadcom Ingress QoS ver 0.1 initialized
BPM: tot_mem_size=67108864B (64MB), buf_mem_size=10066329B (9MB), num of buffers=4802,6
Broadcom BPM Module Char Driver v0.1 Sep 12 2012 17:44:21 Registered<244>
[NTC bpm] bpm_set_status: BPM status : enabled 

Initialized fcache state
Broadcom Packet Flow Cache  Char Driver v2.2 Sep 12 2012 17:44:22 Registered<242>
Created Proc FS /procfs/fcache
Broadcom Packet Flow Cache registered with netdev chain
Broadcom Packet Flow Cache learning via BLOG enabled.
Constructed Broadcom Packet Flow Cache v2.2 Sep 12 2012 17:44:22
bcmxtmcfg: bcmxtmcfg_init entry
adsl: adsl_init entry
Broadcom BCM6328B0 Ethernet Network Device v0.1 Sep 12 2012 17:45:41
ETH Init: Ch:0 - 180 tx BDs at 0xa38da000
ETH Init: Ch:0 - 1920 rx BDs at 0xa38b4000
dgasp: kerSysRegisterDyingGaspHandler: bcmsw registered 
eth0: MAC Address: xxxxxxxxxxx
eth1: MAC Address: xxxxxxxxxxx
eth2: MAC Address: xxxxxxxxxxx
eth3: MAC Address: xxxxxxxxxxx
enter bcm3xx_enet_disable_port[NTC arl] arlEnable : Enabled ARL binding to Flow Cache
Broadcom Adress Resolution Logic Processor (ARL) Char Driver v0.1 Sep 12 2012 17:44:21>
PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
PCI: Setting latency timer of device 0000:02:00.0 to 64
wl: passivemode=1
wl: napimode=0
wl: allocskbmode=1
otp_read_pci: bad crc
wl:not strapped or invalid data
wl:srom not detected, using main memory mapped srom info(wombo board)
wl:loading /etc/wlan/bcm43227_map.bin
wl0: Broadcom BCMa8dc 802.11 Wireless Controller 5.100.123.0.cpe4.10L02.2
dgasp: kerSysRegisterDyingGaspHandler: wl0 registered 
Broadcom 802.1Q VLAN Interface, v0.1

===== Release Version 4.10L.02 (build timestamp 120912_1843) =====

interface atm0.1 does not exist!
SIOCGIFFLAGS: No such device
interface atm1.1 does not exist!
SIOCGIFFLAGS: No such device
interface atm2.1 does not exist!
SIOCGIFFLAGS: No such device
interface atm3.1 does not exist!
SIOCGIFFLAGS: No such device
interface atm4.1 does not exist!
SIOCGIFFLAGS: No such device
interface atm5.1 does not exist!
SIOCGIFFLAGS: No such device
interface atm6.1 does not exist!
SIOCGIFFLAGS: No such device
ip_tables: (C) 2000-2006 Netfilter Core Team
device eth0 entered promiscuous mode
device eth1 entered promiscuous mode
device eth2 entered promiscuous mode
device eth3 entered promiscuous mode
device wl0 entered promiscuous mode
br0: port 5(wl0) entering forwarding state
WLmngr Daemon is running
optarg=0 shmId=0 
BcmAdsl_Initialize=0xC00FDDA0, g_pFnNotifyCallback=0xC012E8A4
wlevt is ready for new msg...
pSdramPHY=0xA3FFFFF8, 0x0 0x20000000
*** PhySdramSize got adjusted: 0x7B024 => 0x90BB8 ***
AdslCoreSharedMemInit: shareMemAvailable=455712
AdslCoreHwReset: pLocSbSta=82940000 bkupThreshold=1600
AdslCoreHwReset:  AdslOemDataAddr = 0xA3F716C8
dgasp: kerSysRegisterDyingGaspHandler: dsl0 registered 
XTM Init: 480 rx BDs at 0xa291f000
XTM Init: 16 rx BDs at 0xa394bc80
ssk:15.443:rcl_wanPppConnObject:541:status OBJ NULL->Unconfigured, lastConnectionErrorE
monitor task is initialized pid= 228 
IPSec VPN daemon running!
optarg=0 shmId=0 
device wl0 left promiscuous mode
br0: port 5(wl0) entering disabled state
device wl0 entered promiscuous mode
br0: port 5(wl0) entering forwarding state
br0: port 5(wl0) entering disabled state
Setting SSID: "test"
Setting SSID: "wl0_Guest1"
Setting SSID: "wl0_Guest2"
Setting SSID: "wl0_Guest3"
Chanspec set to 0x2d08
device wl0 left promiscuous mode
br0: port 5(wl0) entering disabled state
device wl0 entered promiscuous mode
br0: port 5(wl0) entering forwarding state
UPnP daemon is ready to run
ssk:tplink:25.609:ssk_init:815:enable ports rx/tx
TP-Link WR1043ND  v1.8

10 (edited by Beeblebrox 2013-01-30 17:57:37)

Re: TP-Link TD-W8960N and OpenWRT

@Developers
As far as I can tell, the Broadcom components are all present in other devices - for example:
http://wiki.openwrt.org/toh/d-link/dsl-2741b
So the code already exists for the components, and it should be a matter of putting the components together into the file.bin, right?
What can I do, how can I help?
Thanks.

TP-Link WR1043ND  v1.8

Re: TP-Link TD-W8960N and OpenWRT

I have an interest in getting Open-Wrt on this router as well. I have a v1 (v1.6) and I'm not afraid to get my hands a dirty.

Re: TP-Link TD-W8960N and OpenWRT

@brianman23
step1. Build from source.
step2. Knowing how to do serial recovery.
step3. Flash the compiled bin to device, if you hose it recover by serial method
step4.  Start over: modify .config of the build and debug the next build.

Well, this is what I have as my road plan, whether it is wrong or not is another matter. I have step1 under control but step2 is not going so well.

TP-Link WR1043ND  v1.8

Re: TP-Link TD-W8960N and OpenWRT

Ok for your step 2 and step 3 - if you can upload an image of your routers board i will give it a try and describe you what you have to do that you can access the router over serial port.

At first you need a TTL Converter like this:
http://www.amazon.com/CP2102-Module-Dow … +converter

Re: TP-Link TD-W8960N and OpenWRT

stinger2k:  Sorry for extremely late reply - It seems I did not have the "mail alert" function enabled for this thread.  Since that post, I have my serial cable working and have in fact de-bricked a USR5451 maxg on which I had installed dd-wrt.

I had also contacted the developer list some time back and I received the response below - pretty clear I think... Please keep in mind that my device is Ver 4 and the hardware is considerably different:
RESPONSE FOR  MY QUESTION:  bcm963281 got some initial support, but even that goes as far as having a serial console -- no flash, no ethernet, no xdsl, no wifi. bcm96328b0 isn't mentioned anywhere, so i suppose the situation isn't any better. generally, bcm963xxx got working ethernet, NOR flash and some sort of support for the proprietary wifi driver -- which for now doesn't work if the ethernet driver is also loaded.
so all pretty useless for normal users, i guess.

This developer also stated that: "xDSL is only supported on Lantiq and TI AR7 chips for now."

At this point I think that:
1. Trying to get W8960N-ver-4 to work is a waste of time because it is an expert-level problem
2. I would rather spend my time trying to get the W8970 working since it has 2 usb ports, twice the ram/flash space and a faster chip.  Also the chip on this device is Lantiq, meaning ADSL will be supported.

Let me know if you think differently (for the ver4).
Regards.

TP-Link WR1043ND  v1.8

Re: TP-Link TD-W8960N and OpenWRT

I just noticed that on The Buyers Guide (http://wiki.openwrt.org/toh/buyerguide) the usual links to the purchasing sites now list this device, and display ADSL functionality in product specs (http://skinflint.co.uk/tp-link-td-w8960n-a531232.html).

Is this is an error or does it mean that the DSL problem for bcm96xx has been resolved?
Clarification please?
Regards.

TP-Link WR1043ND  v1.8

16

Re: TP-Link TD-W8960N and OpenWRT

Beeblebrox wrote:

I just noticed that on The Buyers Guide (http://wiki.openwrt.org/toh/buyerguide) the usual links to the purchasing sites now list this device, and display ADSL functionality in product specs (http://skinflint.co.uk/tp-link-td-w8960n-a531232.html).

Is this is an error or does it mean that the DSL problem for bcm96xx has been resolved?
Clarification please?
Regards.

That's an error. ADSL with Broadcom chipsets is not supported, and no one is working on it.