Latest version of firmware?

(Last edited by crissvalicos on 6 Oct 2011, 21:35)

TL-WR1043ND (DE) Ver.1.0

ATTITUDE ADJUSTMENT (bleeding edge, r28385)

-----------------------------------------------------
root@OpenWrt:~# iw list
Wiphy phy0
        Band 1:
                Capabilities: 0x104e
                        HT20/HT40
                        SM Power Save disabled
                        RX HT40 SGI
                        No RX STBC
                        Max AMSDU length: 3839 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 8 usec (0x06)
                HT TX/RX MCS rate indexes supported: 0-15
                Frequencies:
                        * 2412 MHz [1] (27.0 dBm)
                        * 2417 MHz [2] (27.0 dBm)
                        * 2422 MHz [3] (27.0 dBm)
                        * 2427 MHz [4] (27.0 dBm)
                        * 2432 MHz [5] (27.0 dBm)
                        * 2437 MHz [6] (27.0 dBm)
                        * 2442 MHz [7] (27.0 dBm)
                        * 2447 MHz [8] (27.0 dBm)
                        * 2452 MHz [9] (27.0 dBm)
                        * 2457 MHz [10] (27.0 dBm)
                        * 2462 MHz [11] (27.0 dBm)
                        * 2467 MHz [12] (disabled)
                        * 2472 MHz [13] (disabled)
                        * 2484 MHz [14] (disabled)
                Bitrates (non-HT):
                        * 1.0 Mbps
                        * 2.0 Mbps (short preamble supported)
                        * 5.5 Mbps (short preamble supported)
                        * 11.0 Mbps (short preamble supported)
                        * 6.0 Mbps
                        * 9.0 Mbps
                        * 12.0 Mbps
                        * 18.0 Mbps
                        * 24.0 Mbps
                        * 36.0 Mbps
                        * 48.0 Mbps
                        * 54.0 Mbps
        max # scan SSIDs: 4
        max scan IEs length: 2257 bytes
        Coverage class: 0 (up to 0m)
        Available Antennas: TX 0x7 RX 0x7
        Configured Antennas: TX 0x7 RX 0x7
        Supported interface modes:
                 * IBSS
                 * managed
                 * AP
                 * AP/VLAN
                 * WDS
                 * monitor
                 * mesh point
                 * P2P-client
                 * P2P-GO
        software interface modes (can always be added):
                 * AP/VLAN
                 * monitor
        interface combinations are not supported
        Supported commands:
                 * new_interface
                 * set_interface
                 * new_key
                 * new_beacon
                 * new_station
                 * new_mpath
                 * set_mesh_params
                 * set_bss
                 * authenticate
                 * associate
                 * deauthenticate
                 * disassociate
                 * join_ibss
                 * join_mesh
                 * remain_on_channel
                 * set_tx_bitrate_mask
                 * action
                 * frame_wait_cancel
                 * set_wiphy_netns
                 * set_channel
                 * set_wds_peer
                 * connect
                 * disconnect
        Supported TX frame types:
                 * IBSS: 0x0000 0x0010 0x0020 0x0030 0x0040 0x0050 0x0060 0x0070 0x0080 0x0090 0x00a0 0x00b0 0x00c0 0x00d0 0x00e0 0x00f0
                 * managed: 0x0000 0x0010 0x0020 0x0030 0x0040 0x0050 0x0060 0x0070 0x0080 0x0090 0x00a0 0x00b0 0x00c0 0x00d0 0x00e0 0x00f0
                 * AP: 0x0000 0x0010 0x0020 0x0030 0x0040 0x0050 0x0060 0x0070 0x0080 0x0090 0x00a0 0x00b0 0x00c0 0x00d0 0x00e0 0x00f0
                 * AP/VLAN: 0x0000 0x0010 0x0020 0x0030 0x0040 0x0050 0x0060 0x0070 0x0080 0x0090 0x00a0 0x00b0 0x00c0 0x00d0 0x00e0 0x00f0
                 * mesh point: 0x0000 0x0010 0x0020 0x0030 0x0040 0x0050 0x0060 0x0070 0x0080 0x0090 0x00a0 0x00b0 0x00c0 0x00d0 0x00e0 0x00f0
                 * P2P-client: 0x0000 0x0010 0x0020 0x0030 0x0040 0x0050 0x0060 0x0070 0x0080 0x0090 0x00a0 0x00b0 0x00c0 0x00d0 0x00e0 0x00f0
                 * P2P-GO: 0x0000 0x0010 0x0020 0x0030 0x0040 0x0050 0x0060 0x0070 0x0080 0x0090 0x00a0 0x00b0 0x00c0 0x00d0 0x00e0 0x00f0
        Supported RX frame types:
                 * IBSS: 0x00d0
                 * managed: 0x0040 0x00d0
                 * AP: 0x0000 0x0020 0x0040 0x00a0 0x00b0 0x00c0 0x00d0
                 * AP/VLAN: 0x0000 0x0020 0x0040 0x00a0 0x00b0 0x00c0 0x00d0
                 * mesh point: 0x00b0 0x00c0 0x00d0
                 * P2P-client: 0x0040 0x00d0
                 * P2P-GO: 0x0000 0x0020 0x0040 0x00a0 0x00b0 0x00c0 0x00d0
        Device supports RSN-IBSS.
root@OpenWrt:~#

Greetings Schindi

I have got this new TX DMA Message
WR1043ND user.err kernel: ath: Failed to stop TX DMA, queues=00000005!

Does anyone have a build of the firmware for this router that includes the latest patches(Mainly the one that fixes Wifi stability issues). Right now, I'm running Gargoyle router, but it has a lot of stability issues. I want to go back to openwrt, but last time I ran it, it also had the wifi stability issues, which I see are resolved now.

if last Friday is sufficient: http://downloads.openwrt.org/snapshots/ … actory.bin

Hi. I've upgraded to that image, but my router still has wifi stability issues.
Over WiFi I get 300-1000ms pings to router, and it disconnects randomly.
logread:

Jan  1 02:46:35 OpenWrt daemon.info hostapd: wlan0: STA 3c:8b:fe:0c:66:b4 IEEE 802.11: disassociated due to inactivity
Jan  1 02:46:36 OpenWrt daemon.info hostapd: wlan0: STA 3c:8b:fe:0c:66:b4 IEEE 802.11: deauthenticated due to inactivity
Jan  1 02:50:22 OpenWrt daemon.info hostapd: wlan0: STA 00:17:31:3e:23:21 IEEE 802.11: deauthenticated due to local deauth request
...
Jan  1 02:50:38 OpenWrt daemon.info hostapd: wlan0: STA 00:17:31:3e:23:21 WPA: received EAPOL-Key 2/4 Pairwise with unexpected replay counter
...

Thank you, Shindi. My shows the same.

If you look here:  http://wiki.openwrt.org/toh/buyerguide#ghz

it clearly shows that in the EU channels 12 and 13 could be enabled as well. It's not the US and their restrictive laws, no, is the manufacturer who obliges all to submit to this restrictive regulations.

http://wiki.openwrt.org/doc/howto/wireless.overview
http://wiki.openwrt.org/doc/howto/wireless.utilities  (content soon to be found...)

(Last edited by Orca on 26 Oct 2011, 13:16)

Hello. I used the Image from Shibby because he compiled a custom kernel that supports an overlay-usb-device on usb out of the box.
Now i want to upgrade to the newest version from openwrt - does the standard/trunk-kernel has overlay-support out of the box now? i
How can i make a sysupgrade to the standard openwrt-trunk-version?

Many thanks

Does anyone know if the Samsung chip K4H510838C-TCCC 64Mb DDR1 @400MHz works at WR-TL1043ND 64Mb mod?
Thank you!

@rymn: http://wiki.openwrt.org/doc/howto/extroot
for sysupgrade, download/build an sysupgrade image (the small one with sysupgrade in the filename) and do the regular mtd command. the 1043 wiki page points it all out.

Thanks for reply. Can I also use the sysupgrad command instead of  "mtd -r write ...."? For my understanding: Actualy I have a usb-stick that holds the overlay-partition:

df -h

free:

i could simply download the latest snapshot-release http://downloads.openwrt.org/snapshots/ … pgrade.bin to /home and then upgrade.

after reboot upgrade and reboot the overlay-partition is still present?

Thanks.

Hello everyone,

it seems my USB port has stopped working , i have rebooted the device (currently running RC5 ) it doesnt detect
any usb device plugged in.

anyone knows which hardware components to check? it seems its a hardware problem but none of the chips seems to have visible damage so i am hopping its something that can be fixed without much problem.

it was working fine until 1 day ago. my usb port was used by a 16 GB usb flash which i used for torrents only, the flash seems fine and uncorrupted but the 1043 doesnt detect anything anymore.

thanks for any advice.
Miguel.

well....jein. the sysupgrade command probably does the same as mtd and might be used (I never did that, but I also never flashed a sysupgrade image, as well). But after doing such an upgrade, several things might not work any more and have to be reconfigured. Especially extroot has seen several changes during the last time (checking the history of that wiki page gives you some impression). Once I read that it is advised to just do sysupgrades within the same versions. So your overlay partition shouldn't be harmed, but you may need to edit fstab again to make it work again.

@miguel: is 5v supply voltage present? Is there a dmesg output if connecting a simple device, like a usb hub?

Hi MBS

About the 5v present ill check it and come back to you as for the dmesg output there is none
I have also tested with a self powered device and also no dmesg activity

EDIT yes 4.92V present on usb port

(Last edited by miguel.arce on 30 Oct 2011, 22:15)

thanks for reply. so is it better to flash the factory-image (i do not want to brick my device)? so i would make the config-stuff again. can i flash the factory-image also via mtd-command?

If all your custom configurations (besides extroot) are on the usb drive anyway, I would not see any reason against a factory image. If not, then a sysupgrade image would be a better choice (also backup all entries in rootfs_data). Even if it will hang for some reason of misconfiguration then, you can still enter failsafe and fix that.
Both kinds of images are flashable with mtd.

Ok. So personaly i would like to flash the factory-image.

I would download this file: http://downloads.openwrt.org/snapshots/ … actory.bin to the usb-stick
and then run this command:

mtd -r write openwrt-ar71xx-generic-tl-wr1043nd-v1-squashfs-factory.bin firmware

right?

Thanks!

ps. why is the factory.bin (8MB) so much bigger then the sysupgrade.bin (3MB)

cause it contains 5MB of empty rootfs_data. Have a look at the wiki page in section partition layout.

i wrote to TP-Link about the USB problem, i hope they will hint me what components to check for
failure, the chips in the pcb seem ok, it just doesnt work it even has power

any advice ? what chip in the pcb is the usb controller? the kernel module loads correctly without errors
it just doesnt detect anything anymore

i am right now advicing against using the usb port for torrent applications it seems the chip doesnt support
heavy use :'(

(Last edited by miguel.arce on 1 Nov 2011, 05:48)

Hi, anyone with expertise in electronics?

i found that the only component "loose" in the pcb ( 1.1 rev 1.7 ) is C618, but i dont know
what it is, and what should i replace it with.

could i look for a similar or identical one in old motherboards?

also dont know if that could be usb related.. but its the only damaged component i found, all the other ones seems physically ok.

best regards,
Miguel

Looks damn small on the picture I got. Probably just a few pF. Have a look into the datasheet of U20, there might be a recommendation.

Well, i took a paper clip, fixed it into my soldering iron's tip and with extreme care reinforced its soldering points,

i really dont know if it was usb related but, it must somehow as i now have usb port back

i am soo, sooo, soooooo happy

thanks MBS.

(Last edited by miguel.arce on 7 Nov 2011, 20:33)

hey, i upgraded to RC6, but something weird is happening to luci, it get stuck in the "collecting data.." phase of the network infomation for interfaces, active conections, etc.. everything related to network information luci only shows collecting data...

if i am in RC6 and want to get back at RC5 is as simple as flashing the RC5 sysupgrade?

best regardes,
Miguel.

Simply clear your browser cache.