OpenWrt Forum Archive

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

The content of this topic has been archived between 13 Jun 2015 and 6 May 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Thank you. I will try. What do you think about links, thats i was posted? About  Bullet M? But theirs size is other, than tp-link's.

Hi,

alif wrote:

They differ only in flash? It possible to combine firmware 941n v5 and 841n v5? Any idea?)

Maybe the problem is this:

Just be warned that at some point the flash chip in these devices has changed.

It was a winbond chip identified by the kernel as s25sl032a

now it's an hynix 934A HY5DU561622FTP-5
Kernel sees this as
m25p80 spi0.0: unrecognized JEDEC id ef4016

How can I do?

The TL-WR941ND v4 should be working with the 'openwrt-ar71xx-tl-wr841nd-v5-squashfs-universal.bin' image. The problem is that you have used an old snapshot, and the support for the Winbond W25Q32BV flash chip has been added only with r19536. You should try a newer snapshot, or you should build your own image from a fresh checkout.

Regards,
Gabor

On tl-wr941nd V4, openwrt was instaled))
Thanks for all) With last trunk, we did it) (openwrt-ar71xx-tl-wr841nd-v5-initramfs-uImage.bin)
Starting kernel ...

Linux version 2.6.32.8 (admin@serversmb.localdomain) (gcc version 4.3
.3 (GCC) ) #1 Fri Feb 19 09:53:30 ALMT 2010
bootconsole [early0] enabled
CPU revision is: 00019374 (MIPS 24Kc)
Atheros AR7240 rev 2, CPU:400.000 MHz, AHB:200.000 MHz, DDR:400.000 MHz
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: rootfstype=squashfs,yaffs,jffs2 noinitrd console=ttyS0,115200 board=TL-WR741ND
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 64kB, VIPT, 4-way, linesize 32 bytes.
Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
Writing ErrCtl register=00000000
Readback ErrCtl register=00000000
Memory: 27352k/32768k available (2003k kernel code, 5416k reserved, 378k data, 2252k init, 0k highmem)
SLUB: Genslabs=7, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:56
Calibrating delay loop...
266.24 BogoMIPS (lpj=1331200)
Mount-cache hash table entries: 512
N
ET: Registered protocol family 16
MIPS: machine is TP-LINK TL-WR741ND

registering PCI controller with io_map_base unset
bio: create slab <bio-0> at 0

PCI: fixup device 0000:00:00.0
pci 0000:00:00.0: PME# supported from D0 D1 D3hot
pci 0000:00:00.0: PME# disabled
PCI: mapping irq 48 to pin1@0000:00:00.0
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
NET: Registered protocol family 1

squashfs: version 4.0 (2009/01/31) Phillip Lougher
Registering mini_fo version $Id$
JFFS2 ver
sion 2.2. (NAND) (SUMMARY)  \0xc2\0xa9 2001-2006 Red Hat, Inc.
yaffs Feb 19 2010 09:49:32 Installing.
msgmni has been set to 53
io scheduler noop registered
io scheduler deadline registered (default)
Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11) is a 16550A
console [ttyS0] enabled, bootconsole disabled
console [ttyS0] enabled, bootconsole disabled
Atheros AR71xx SPI Controller driver version 0.2.4
m25p80 spi0.0: w25q32 (4096 Kbytes)
Searching for RedBoot partition table in spi0.0 at offset 0x3fe000
Searching for RedBoot partition table in spi0.0 at offset 0x3ff000
No RedBoot partition table detected in spi0.0
spi0.0: no WRT160NL signature found
Creating 5 MTD partitions on "spi0.0":
0x000000000000-0x000000020000 : "u-boot"
0x000000020000-0x000000160000 : "kernel"
0x000000160000-0x0000003f0000 : "rootfs"
mtd: partition "rootfs" set to be root filesystem
split_squashfs: no squashfs found in "spi0.0"
0x0000003f0000-0x000000400000 : "art"
0x000000020000-0x0000003f0000 : "firmware"
ag71xx_mdio: probed
eth0: Atheros AG71xx at 0xba000000, irq 5

eth1: Atheros AG71xx at 0xb9000000, irq 4

Atheros AR71xx hardware watchdog driver version 0.1.0
TCP westw
ood registered
NET: Registered protocol family 17
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
Freeing unused kernel memory: 2252k freed

gpio-buttons driver version 0.1.2
input: gpio-buttons as /devices/platform/gpio-buttons/inp
ut/input0
Button Hotplug driver version 0.3.1
eth0: link up (1000Mbps/Full duplex)
- preinit -
Registered led device: tl-wr741nd:green:system
Registered led device: tl-wr741nd:green:qss
Press Press f<ENTER> to enter failsafe mode

- regular preinit -

Please press Enter to activate this console.
device eth0 entered promiscuous mode
br-lan: port 1(eth0) entering forwarding state

eth1: link up (100Mbps/Full duplex)

Generic kernel compatibility enabled based on linux-next next-20100113

cfg80211: Calling CRDA to update world regulatory domain

SCSI subsystem initialized

cfg80211: World regulatory domain updated:
    (start_freq - end_freq @ bandwidt
h), (max_antenna_gain, max_eirp)
    (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)

usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub

usbcore: registered new device driver usb

Registered led device: ath9k-phy0::radio
Registered led device: ath9k-phy0::assoc
Registere
d led device: ath9k-phy0::tx
Registered led device: ath9k-phy0::rx
phy0: Atheros AR9280 Rev:2 mem=0xb0000000, irq=48
cfg80211: Calling CRDA for country: US
cfg80211: Regulatory domain changed to country: US
    (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
    (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
    (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)

PPP generic driver version 2.4.2
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004
Max Krasnyansky <maxk@qualcomm.com>
ip_tables: (C) 2000-2006 Netfilter Core Team

nf_conntrack version 0.5.0 (462 buckets, 1848 max)

ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver




BusyBox v1.15.3 (2010-02-19 09:28:45 ALMT) built-in shell (ash)
Enter 'help' for a lis
t of built-in commands.

  _______                     ________        __
|       |.-----.-----.-----.|  |  |  |.----.|  |_
|   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
|_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
KAMIKAZE (bleeding edge, r19725) ------------------
  * 10 oz Vodka       Shake well with ice and strain
  * 10 oz Triple sec  mixture into 10 shot glasses.
  * 10 oz lime juice  Salute!
---------------------------------------------------
root@OpenWrt:/#

(Last edited by alif on 19 Feb 2010, 19:25)

(5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
(5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)

Is it true, for my device?

good news!!
you may get further test

the wireless and the led lights
do they work well??

(Last edited by 69350 on 20 Feb 2010, 10:58)

Yes, led lights work well. Wireless will test after 1-2 hours. How to disable update from internet before compile?
This one not work on 941nd v4 http://downloads.openwrt.org/snapshots/ … versal.bin (17/02/2010)

iwconfig wlan0 mode Master
Error for wireless request "Set Mode" (8B06) :

And settings are not saved on device(

(Last edited by alif on 19 Feb 2010, 22:42)

Ok. wireless work is good)) But how to save all settings?) I am searching.

My WR-941ND v2 sports a 2x5 pin serial header instead of the 4 pin 1-line header that is found on the wiki (at least I hope it is the serial port). Did somebody figure out its pinout? Is the same resistor to bridge?

Yes, that's it, thank you very much for the pointer.
Although it is not entirely clear from the post how lark counts the pin numbers: when he mentions pins 1...5, is he referring to the top row starting from the marked pin or is it in zig-zag as in the standard (?) pin numbering scheme?

How could use with the USB host ?
My hardware is TL-WR941Nv4, run profile "WR941NDv4" well, which use "mach-tl-wr741nd.c" in the kernel.
And I had add function "ar71xx_add_device_usb();" at "tl_wr741nd_setup", so I can "lsusb" in console to got following message:

root@OpenWrt:/# lsusb
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

And I have solder [s]R278,R277,(updated, delete it)[/s]R185,R183, R713,R712,R711 directly.(Is it correct? I do not solder the resistor but short pass)
But the USB device can not find yet.
Is there any advice?

R713, R712, R185, R183, R711

(Last edited by arrowworld on 21 Feb 2010, 06:40)

arrowworld wrote:

And I have solder RR278,R277,R185,R183, R713,R712,R711 directly.(Is it correct? I do not solder the resistor but short pass)

TL-WR941Nv4 direct solder resistor should be R713, R712, R185, R183, R711(GND)
Then R713 connect to CPU pin of U74, R712 connect to CPU pin of U73.
But Here lack 5V Vcc, How could get 5V from 9V Vcc.
http://www.dd-wrt.com/phpBB2/viewtopic. … p;start=15

lark wrote:
I am also looking at the USB port's power supply circuit. It is 12v to 5v DC-DC converter, and yes it's not that complex as I thought before.

But here is not any update
Could someone help it ?

new progress on the usb about TL-WR941Nv4, I have got below message now -_-, connect as the last my post.
but, I use with a hard-disk which supply 5Vcc with another USB host.
So, How to get 5Vcc is the critical work.

usb 1-1: new full speed USB device using ar71xx-ohci and address 2
usb 1-1: configuration #1 chosen from 1 choice
scsi0 : SCSI emulation for USB Mass Storage devices
scsi 0:0:0:0: Direct-Access     Hitachi  HTS541640J9AT00  SB1O PQ: 0 ANSI: 0
sd 0:0:0:0: [sda] 78140160 512-byte logical blocks: (40.0 GB/37.2 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Assuming drive cache: write through
sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 sda9 >
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Attached SCSI disk
yaffs: dev is 8388609 name is "sda1"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 8.1, "sda1"
yaffs: dev is 8388609 name is "sda1"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 8.1, "sda1"
REISERFS (device sda1): found reiserfs format "3.6" with standard journal
REISERFS (device sda1): using ordered data mode
REISERFS (device sda1): journal params: device sda1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
REISERFS (device sda1): checking transaction log (sda1)
REISERFS (device sda1): replayed 1 transactions in 0 seconds
REISERFS (device sda1): Using r5 hash to sort names
yaffs: dev is 8388610 name is "sda2"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 8.2, "sda2"
yaffs: dev is 8388610 name is "sda2"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 8.2, "sda2"
REISERFS (device sda2): found reiserfs format "3.6" with standard journal
REISERFS (device sda2): using ordered data mode
REISERFS (device sda2): journal params: device sda2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
REISERFS (device sda2): checking transaction log (sda2)
REISERFS (device sda2): replayed 1 transactions in 0 seconds
REISERFS (device sda2): Using r5 hash to sort names
yaffs: dev is 8388611 name is "sda3"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 8.3, "sda3"
yaffs: dev is 8388611 name is "sda3"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 8.3, "sda3"
yaffs: dev is 8388612 name is "sda4"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 8.4, "sda4"
yaffs: dev is 8388612 name is "sda4"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 8.4, "sda4"
attempt to access beyond end of device
sda4: rw=0, want=18, limit=2
REISERFS warning (device sda4): sh-2006 read_super_block: bread failed (dev sda4, block 8, size 1024)
attempt to access beyond end of device
sda4: rw=0, want=130, limit=2
REISERFS warning (device sda4): sh-2006 read_super_block: bread failed (dev sda4, block 64, size 1024)
yaffs: dev is 8388613 name is "sda5"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 8.5, "sda5"
yaffs: dev is 8388613 name is "sda5"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 8.5, "sda5"
yaffs: dev is 8388614 name is "sda6"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 8.6, "sda6"
yaffs: dev is 8388614 name is "sda6"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 8.6, "sda6"
yaffs: dev is 8388615 name is "sda7"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 8.7, "sda7"
yaffs: dev is 8388615 name is "sda7"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 8.7, "sda7"
yaffs: dev is 8388616 name is "sda8"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 8.8, "sda8"
yaffs: dev is 8388616 name is "sda8"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 8.8, "sda8"
yaffs: dev is 8388617 name is "sda9"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 8.9, "sda9"
yaffs: dev is 8388617 name is "sda9"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 8.9, "sda9"
REISERFS (device sda9): found reiserfs format "3.6" with standard journal
REISERFS (device sda9): using ordered data mode
REISERFS (device sda9): journal params: device sda9, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
REISERFS (device sda9): checking transaction log (sda9)
REISERFS (device sda9): replayed 1 transactions in 0 seconds
REISERFS (device sda9): Using r5 hash to sort names

root@OpenWrt:/# lsusb
Bus 001 Device 002: ID 067b:2506 Prolific Technology, Inc.
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

root@OpenWrt:/mnt# mount
rootfs on / type rootfs (rw)
/dev/root on /rom type squashfs (ro,relatime)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,relatime,size=14796k)
tmpfs on /dev type tmpfs (rw,relatime,size=512k)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
/dev/mtdblock3 on /jffs type jffs2 (rw,relatime)
mini_fo:/jffs on / type mini_fo (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
none on /proc/bus/usb type usbfs (rw,relatime)
/dev/sda1 on /mnt/sda1 type reiserfs (rw,relatime)
/dev/sda2 on /mnt/sda2 type reiserfs (rw,relatime)
/dev/sda9 on /mnt/sda9 type reiserfs (rw,relatime)

(Last edited by arrowworld on 21 Feb 2010, 06:55)

ejcspii wrote:

Although it is not entirely clear from the post how lark counts the pin numbers

Should someone else be interested: my scope told me that the "zigzag" numbering is the right answer. Thanks again.

lark said: P1 is RX, P2 is TX. R356 is all you should need to bridge.
     just to short pass the R356,

Can you post photos, how you solder it?

I am sorry) I asked arroworld)

alif wrote:

I am sorry) I asked arroworld)

For here is no camera, I capture a photo with my thinkpad-x200, seems not clearly([s]refer to attached image::I'm finding how to attach it[/s]).
The CPE did not stable while short pass all of the resistor, it will reset the device,(e.g. the DM9601 net device)
So I solder 0.1Ohm resistor to R713 and R712, then solder 100pF capacity to R278 and R277, now my DM9601 net card is so stable. (short pass for I have no resistor before, I bought some equipment for research the wrt these days, e.g. digital multimeter)
Oh, so sad, I have not found out any way to post it, fail on flickr.com yet.
The picture could not show with me, maybe anyother could show it?
http://www.flickr.com/photos/47810639@N03/4381491507/
(I'd like if anyone tell me how to post a picture for wiki of openwrt)

(Last edited by arrowworld on 23 Feb 2010, 17:02)

Now, I have make out a 5V power supply with LM2576t-5(made by motorola), sit on another board, and connect the USB connector's VCC,GND to the power-board.
the datasheet is at: http://www.datasheetcatalog.com/datashe … 6T-5.shtml, the layout referrence at page 22.

Hello!

I'm trying to get the USB port of my WR941ND working, but didn't succeed yet. I have a V 3.0 device, hardware revision 1.2.

I soldered 33 Ohm resistors for impedance matching to R1000 and R1001, added a 7805 and a 100uF capacitor to provide +5V to the USB port. Power supply works well. I suppose that D100 and D101 are some kind of surge protection, so I omitted them.

Then I checked the data lines with a multimeter. Between R1000 and GND I measured 0.7V dc and an ac value of about 1.2V which looks promising to me, as it shows that there is a pulsing signal on the line.

I repeated the same test for R1001 and measured 3.3V dc and 0V ac, which looks more like the high level of a gpio line than an USB data signal. I checked all connections twice, but didn't found anything: no shortcuts, no missing components.

As I don't have a datasheet of the AR9132, I don't no if there is any kind of i/o-pin-sharing, which requires a pull-up / pulldown resistor to be set in order to connect the USB data signal to the corresponding i/o-pin.

The kernel is already modified, too. I added scsi_mod, nls_base, usbcore, ehci_hcd, ohci_hcd and usb-storage. In order to get the usb-controller be recognized by the kernel, I had to add 2 lines to the source file mach-tl-wr941nd.c. First an additional header-file must be included:

#include "dev-usb.h"

Second the initialization routine of the usb-controller must be called:

static void __init tl_wr941nd_setup(void)
{
    u8 *mac = (u8 *) KSEG1ADDR(0x1f01fc00);
    u8 *eeprom = (u8 *) KSEG1ADDR(0x1fff1000);

    ar71xx_set_mac_base(mac);

    ar71xx_add_device_mdio(0x0);

    ar71xx_eth0_data.phy_if_mode = PHY_INTERFACE_MODE_RMII;
    ar71xx_eth0_data.phy_mask = 0x0;
    ar71xx_eth0_data.speed = SPEED_100;
    ar71xx_eth0_data.duplex = DUPLEX_FULL;

    ar71xx_add_device_eth(0);

    ar71xx_add_device_usb();

    ar71xx_add_device_dsa(0, &tl_wr941nd_dsa_data);

    ar71xx_add_device_m25p80(&tl_wr941nd_flash_data);

    ar71xx_add_device_leds_gpio(-1, ARRAY_SIZE(tl_wr941nd_leds_gpio),
                    tl_wr941nd_leds_gpio);

    ar71xx_add_device_gpio_buttons(-1, TL_WR941ND_BUTTONS_POLL_INTERVAL,
                    ARRAY_SIZE(tl_wr941nd_gpio_buttons),
                    tl_wr941nd_gpio_buttons);
    ar913x_add_device_wmac(eeprom, mac);
}

The syslog output looks quite good so that I'm pretty sure that nothing is missing.

Jan  1 00:00:13 OpenWrt user.notice kernel: SCSI subsystem initialized
Jan  1 00:00:13 OpenWrt user.info kernel: usbcore: registered new interface driver usbfs
Jan  1 00:00:13 OpenWrt user.info kernel: usbcore: registered new interface driver hub
Jan  1 00:00:13 OpenWrt user.info kernel: usbcore: registered new device driver usb
Jan  1 00:00:15 OpenWrt user.info kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jan  1 00:00:15 OpenWrt user.info kernel: ar71xx-ehci ar71xx-ehci: Atheros AR91xx built-in EHCI controller
Jan  1 00:00:15 OpenWrt user.info kernel: ar71xx-ehci ar71xx-ehci: new USB bus registered, assigned bus number 1
Jan  1 00:00:15 OpenWrt user.info kernel: ar71xx-ehci ar71xx-ehci: irq 3, io mem 0x1b000000
Jan  1 00:00:15 OpenWrt user.info kernel: ar71xx-ehci ar71xx-ehci: USB 2.0 started, EHCI 1.00
Jan  1 00:00:15 OpenWrt user.info kernel: usb usb1: configuration #1 chosen from 1 choice
Jan  1 00:00:15 OpenWrt user.info kernel: hub 1-0:1.0: USB hub found
Jan  1 00:00:15 OpenWrt user.info kernel: hub 1-0:1.0: 1 port detected
Jan  1 00:00:16 OpenWrt user.info kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jan  1 00:00:16 OpenWrt user.info kernel: Initializing USB Mass Storage driver...
Jan  1 00:00:16 OpenWrt user.info kernel: usbcore: registered new interface driver usb-storage
Jan  1 00:00:16 OpenWrt user.info kernel: USB Mass Storage support registered.

The usb filesystem is mounted, too.

root@OpenWrt:/sys/bus/usb/drivers/usbfs# mount
rootfs on / type rootfs (rw)
/dev/root on /rom type squashfs (ro,relatime)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,relatime,size=14796k)
tmpfs on /dev type tmpfs (rw,relatime,size=512k)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
/dev/mtdblock3 on /jffs type jffs2 (rw,relatime)
mini_fo:/jffs on / type mini_fo (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
none on /proc/bus/usb type usbfs (rw,relatime)

But when I connect a USB-Stick to the port, nothing happens. The activity led of the stick does not start to flash, as it does when I connect the stick to the USB port of my USR5461. It seems there is no activity on the bus.

root@OpenWrt:/# ls -l /proc/bus/usb
dr-xr-xr-x    2 root     root            0 Jan  1 00:00 001
-r--r--r--    1 root     root            0 Jan  1 00:00 devices 

root@OpenWrt:/# ls -l /sys/bus/usb/devices/ 
lrwxrwxrwx    1 root     root            0 Jan  1 00:01 1-0:1.0 -> ../../../devices/platform/ar71xx-ehci/usb1/1-0:1.0
lrwxrwxrwx    1 root     root            0 Jan  1 00:01 usb1 -> ../../../devices/platform/ar71xx-ehci/usb1

Anybody out there who knows what's wrong?

(Last edited by Mausi on 27 Mar 2010, 03:59)

Hello!

I'm still trying to get the USB-port of my WR941ND working. As the board of the V3 is different than the one of the V4 I need some additional information. Could anyone who has applied the modifications describe the circuit a little bit more, please?

According to the post R712 and R713 connect the USB-header to the CPU. Is that correct?

As R711 connects to GND, it seems to be a pull-down resistor. Is it connected to the CPU, too? (Which pin?)

Soldering a capacitor to a resistor's pad (R277 and R278) seems weird to me? Does anybody know a little bit more of the function of this components? To which other components are they connected? Are they related to the power supply ciruit?

What is the function of R183 and R185? Are they pull-ups or pull-downs?

Thanks in advance!

Sincerely,

Mausi

Hi,

I just received a WR941ND it has version nr v4.1
What image can I use to flash it? Anyone tried to flash V4.1 ?

Many tnx.

beone wrote:

Hi,

I just received a WR941ND it has version nr v4.1
What image can I use to flash it? Anyone tried to flash V4.1 ?

Many tnx.

Have the same question ....

Anyone?

Brgds,
S.

sergejk wrote:
beone wrote:

Hi,

I just received a WR941ND it has version nr v4.1
What image can I use to flash it? Anyone tried to flash V4.1 ?

Many tnx.

Have the same question ....

Anyone?

Brgds,
S.

I have standard TP-LINK firmware and i want it to upgrade with openwrt firmware.
As i can see from:
http://downloads.openwrt.org/snapshots/ … actory.bin

Is it going to work if i flash it over webUI with openwrt-ar71xx-tl-wr941nd-v4-squashfs-factory.bin file?

Brgds,
S.