| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision |
| toh:tp-link:tl-wr1043nd [2018/02/17 19:06] – ↷ Links adapted because of a move operation | toh:tp-link:tl-wr1043nd [2024/10/01 23:47] – [OpenVPN performance] delacor |
|---|
| ====== TP-Link TL-WR1043ND ====== | ====== TP-Link TL-WR1043ND ====== |
| One of the first cheap devices with an gigabit Ethernet switch. Manufacture advertised features: 3 removable omni antennas ([[wp>RP-SMA|RP-SMA connectors]]) and 24 dBm (251 mW, v1.x)/25 dBm (v2.x,v3.x) maximal TX power output. Note: maximal TX power and available channels are limited in some countries! | One of the first cheap devices with an gigabit Ethernet switch. Advertised features: 3 removable omni antennas ([[wp>RP-SMA|RP-SMA connectors]]) and 24 dBm (251 mW, v1.x)/25 dBm (v2.x, v3.x) maximal TX power output. Note: Maximal TX power and available channels are limited in some countries! |
| |
| **WARNING:** <del>These routers seem to have unstable wifi in Attitude Adjustment 12.09. They're hit by bugs [[https://dev.openwrt.org/ticket/9654|9654]], [[https://dev.openwrt.org/ticket/12372|12372]] and [[https://dev.openwrt.org/ticket/13966|13966]].</del> Fixed in Barrier Breaker 14.07 and later | ^ HW v1.x ^ HW v2.x ^ HW v3.x ^ HW v4.x ^ HW v5.x ^ |
| | | {{media:tplink:tl-wr1043:tl-wr1043nd-v1_profile.jpg?200|}} | {{media:tplink:tl-wr1043:tl-wr1043nd-v2_profile.jpg?200|}} | {{media:tplink:tl-wr1043:tl-wr1043nd-v2_profile.jpg?200|}} | {{media:tplink:tl-wr1043:tl-wr1043nd-v2_profile.jpg?200|}}|{{media:tplink:tl-wr1043:tl-wr1043nd-v2_profile.jpg?200|}} | |
| |
| ===== Supported Versions ===== | ===== Supported Versions ===== |
| This router has the following versions/models. | <!-- ToH: { |
| | "source": "json", |
| | "dom": "t", |
| | "paging": false, |
| | "rotate": true, |
| | "shownColumns": ["brand", "model", "version", "supportedcurrentrel", "oemdevicehomepageurl", "owrt_forum_topic_url", "deviceid"], |
| | "filterColumns": {"brand": "^TP-Link$", "model": "^TL-WR1043ND$" } |
| | } --> |
| |
| | ++++Historic information| |
| ^ Version/Model ^ S/N ^ Release Date ^ Bootloader Date ((U-Boot 1.1.4 if not stated otherwise.)) ((''grep U-Boot /dev/mtd0ro'')) ^ Supported since version ((The earliest OpenWrt release to be supported. Subsequent releases should be supported unless otherwise stated.)) ^ Model Specific Notes ^ | ^ Version/Model ^ S/N ^ Release Date ^ Bootloader Date ((U-Boot 1.1.4 if not stated otherwise.)) ((''grep U-Boot /dev/mtd0ro'')) ^ Supported since version ((The earliest OpenWrt release to be supported. Subsequent releases should be supported unless otherwise stated.)) ^ Model Specific Notes ^ |
| | v1.0 | - | | | Backfire 10.03.1 | Similar, German WebUI | | | v1.0 | - | | | Backfire 10.03.1 | Similar, German WebUI | |
| | v3.0 | - | | - | [[http://downloads.openwrt.org/chaos_calmer/15.05.1/ar71xx/generic/|Chaos Calmer 15.05.1]] | Same HW as v2.x [[https://fccid.io/document.php?id=2644079|FCC ID: TE7WR1043NDV3]] | | | v3.0 | - | | - | [[http://downloads.openwrt.org/chaos_calmer/15.05.1/ar71xx/generic/|Chaos Calmer 15.05.1]] | Same HW as v2.x [[https://fccid.io/document.php?id=2644079|FCC ID: TE7WR1043NDV3]] | |
| | v4.0 | - | | 2016-03-03 | v4 Snapshot from 2017-02-19 was working without problems| New UI and HW changes. Got QCA9563 + 16MB internal flash (QCA9563+QCA8337N+25Q128FVSG+A3R12E40CBF-8E) [[https://fccid.io/TE7WR1043NDV4|FCC ID: TE7WR1043NDV4]] | | | v4.0 | - | | 2016-03-03 | v4 Snapshot from 2017-02-19 was working without problems| New UI and HW changes. Got QCA9563 + 16MB internal flash (QCA9563+QCA8337N+25Q128FVSG+A3R12E40CBF-8E) [[https://fccid.io/TE7WR1043NDV4|FCC ID: TE7WR1043NDV4]] | |
| | | v5.0 | - | | - | [[https://git.lede-project.org/?p=source.git;a=commit;h=673793d753717dc49e5a6f9b1bba52658cae63fc|Since commit 673793d753717dc49e5a6f9b1bba52658cae63fc]] | Model name shortened to TL-WR1043N | |
| ^ HW v1.x ^ HW v2.x ^ HW v3.x ^ HW v4.x ^ | ++++ |
| | {{media:tplink:tl-wr1043:tl-wr1043nd-v1_profile.jpg?200|}} | {{media:tplink:tl-wr1043:tl-wr1043nd-v2_profile.jpg?200|}} | {{media:tplink:tl-wr1043:tl-wr1043nd-v2_profile.jpg?200|}} | {{media:tplink:tl-wr1043:tl-wr1043nd-v2_profile.jpg?200|}} | | |
| |
| |
| ===== Hardware Highlights ===== | ===== Hardware Highlights ===== |
| | <!-- ToH: { |
| | "source": "json", |
| | "dom": "t", |
| | "paging": false, |
| | "rotate": true, |
| | "shownColumns": ["model", "version", "cpu", "cpumhz", "flashmb", "rammb", "wlanhardware", "wlan24ghz", "wlan50ghz", "ethernet100mports", "ethernet1gports", "modem", "usbports"], |
| | "filterColumns": {"brand": "^TP-Link$", "model": "^TL-WR1043ND$" } |
| | } --> |
| |
| These devices are listed in the [[toh:start|Table of Hardware]]: | See paragraphs [[#Hardware]] or [[#Tags]] for more details. |
| ---- datatable ---- | |
| cols : Model, Version, Platform, CPU MHz, Flash MB_mbflashs, RAM MB_mbram, WLAN Hardware, WLAN 2.4Ghz, Ethernet GBit ports_, USB ports_, Serial, JTAG,Supported Current Rel,Device Techdata_pageid | |
| header : Model,Version,SoC,CPU MHz,Flash/MB,RAM/MB,WiFi Hardware,WiFi 2.4,GBit ports,USB,Serial,JTAG,OpenWrt (latest),View/Edit | |
| align : l,l,l,r,r,r,l,l,r,l,l,l,l,l | |
| filter : Brand=TP-Link | |
| filter : Model=~TL-WR1043ND | |
| sort : Version | |
| ---- | |
| | |
| FIXME: merge these into the device database: | |
| ^ HW Version ^ CPU ^ Ram ^ Flash ^ Network ^ Wireless ^ Switch ^USB ^ Serial ^ JTag ^ Wiki ^ FCC ^ | |
| | 1.x | Atheros AR9132@400MHz | 32MB | 8MB | 1x WAN 4x LAN (Gbit) | AR9103 [bgn 3x3:2] | RTL8366RB | Yes | Yes | Yes | [[https://wikidevi.com/wiki/TP-LINK_TL-WR1043ND_v1.x|here]] | [[https://fcc.io/TE7/WR1043NX|here]] | | |
| | 2.x | Qualcomm Atheros QCA9558@720MHz | 64MB | 8MB | 1x WAN 4x LAN (Gbit) | QCA9558 [bgn 3x3:3] | QCA8327N | Yes | Yes | No | [[https://wikidevi.com/wiki/TP-LINK_TL-WR1043ND_v2.x|here]] | [[https://fcc.io/TE7/WR1043NDV2|here]] | | |
| | 3.x | Qualcomm Atheros QCA9558@720MHz | 64MB | 8MB | 1x WAN 4x LAN (Gbit) | QCA9558 [bgn 3x3:3] | QCA8327N | Yes | Yes | No | [[https://wikidevi.com/wiki/TP-LINK_TL-WR1043ND_v3.x|here]] | [[https://fcc.io/TE7/WR1043NDV3|here]] | | |
| | 4.x | Qualcomm Atheros QCA9563@750MHz | 64MB | 16MB | 1x WAN 4x LAN (Gbit) | QCA9563 [bgn 3x3:3] | QCA8337N | Yes | Yes | No | [[https://wikidevi.com/wiki/TP-LINK_TL-WR1043ND_v4.x|here]] | [[https://fcc.io/TE7/WR1043NDV4|here]] | | |
| | |
| See paragraphs [[toh/tp-link/tl-wr1043nd#Hardware]] or [[toh/tp-link/tl-wr1043nd#Tags]] for more details. | |
| | |
| ===== Warnings / Gotchas ===== | |
| | |
| ==== USB 3G Modems ==== | |
| | {{:meta:icons:tango:48px-emblem-important.svg.png?nolink}} | The TL-WR1043ND v1.x does **not** deliver enough power for most USB 3G modems, which can lead to erratic behavior such as dropped/failed connections. If a 3G USB modem is to be used, consider other routers with a USB port that delivers enough amperes (e.g. the [[:toh:buffalo:wzr-hp-ag300h|Buffalo WZR-HP-AG300H]]). | | |
| | |
| === USB 3G modems confirmed working with TL-WR1043ND v1: === | |
| * Huawei E303 | |
| * Huawei E303c | |
| * Huawei E3131 | |
| * Huawei E3272 | |
| * Huawei E3531 | |
| * Huawei E3533 (via usb-tethering) | |
| * ZTE MF823L | |
| * ZTE MF190 | |
| * ZTE MF193 | |
| * ZTE MF626 | |
| * ZTE MF667 (via usb-tethering, bad connection) | |
| | |
| === USB 3G modems confirmed working with TL-WR1043ND v2: === | |
| * TCT Mobile One Touch X500D | |
| * TCT Mobile X220L | |
| * ZTE MF632 | |
| * Vodafone K3765 (Huawei) | |
| * Huawei E160E | |
| * Huawei E3531 | |
| | |
| ==== Connection quality drops after a few hours, latency/ping/lag spikes ==== | |
| | |
| Still reproductible with release 15.05.1; gone in LEDE 17.01.4: | |
| If wireless performance becomes awful after a few hours and ping times to the router over wifi increase up to half a second or more, there's a good chance you're experiencing [[https://dev.openwrt.org/ticket/12372]] | |
| | |
| Restarting wireless with the "wifi" command makes the issue temporarily go away for the next few hours. Disabling ANI (Adaptive Noise Immunity) with the following command makes the issue go away until the next reboot | |
| '' | |
| echo 0 >/sys/kernel/debug/ieee80211/phy0/ath9k/ani | |
| '' | |
| | |
| For more details, including how to disable ANI at boot, see longer description of the same ANI issue on the [[toh:linksys:wrt160nl|Cisco WRT160NL]] page. | |
| |
| ===== Installation ===== | ===== Installation ===== |
| - [[doc:howto:obtain.firmware]] and [[about/latest|Latest OpenWrt Release]] - required image file is "[[http://downloads.openwrt.org/latest/ar71xx/generic/openwrt-ar71xx-generic-tl-wr1043nd-v1-squashfs-factory.bin|openwrt-ar71xx-generic-tl-wr1043nd-v1-squashfs-factory.bin]]" for v1.x routers, "openwrt-ar71xx-generic-tl-wr1043nd-v2-squashfs-factory.bin" for v2.x routers. Files can be found in the "ar71xx" directory. You can use the quick links from the table below. **If you have "Please choose a file to upgrade" message again and again, filename is probably too long and you have to rename image to for example firmware.bin.** | |
| - [[docs:user-guide:generic.flashing]] Now write this firmware-file onto the flash-chip of your device | |
| |
| :!: **''NOTE:''** If case you have a revision > v1.10 (but not v2.x), you need to flash an elder OEM firmware release first, and only then flash OpenWrt; tested and works [[http://forum.lowyat.net/topic/2481658/all|credits go to sayboon]] for his tutorial | <!-- ToH: { |
| | "source": "json", |
| | "dom": "t", |
| | "paging": false, |
| | "rotate": true, |
| | "shownColumns": ["model", "version", "supportedcurrentrel", "firmwareopenwrtinstallurl", "firmwareopenwrtupgradeurl", "firmwareoemstockurl"], |
| | "filterColumns": {"brand": "^TP-Link$", "model": "^TL-WR1043ND$" } |
| | } --> |
| | - **If you have "Please choose a file to upgrade" message again and again, filename is probably too long and you have to rename image to for example ''firmware.bin''.** |
| | - [[docs:guide-user:installation:generic.flashing]] Now write this firmware-file onto the flash-chip of your device |
| |
| | :!: **''NOTE:''** In case you have a revision > v1.10 (but not v2.x), you need to flash an elder OEM firmware release first, and only then flash OpenWrt; tested and works [[http://forum.lowyat.net/topic/2481658/all|credits go to sayboon]] for his tutorial. |
| |
| ==== Installation on HW rev.3 ==== | |
| |
| {{page>meta:infobox:cleanup&noheader&nofooter&noeditbtn}} | |
| |
| For revision **v3.0**, stock FW 3.16.9 build **150514**: With the current stock TP-Link firmware it's not possible to flash the current stable OpenWrt Chaos Calmer 15.05.1 release for v2 routers. The web interface keeps complaining, that filename and version do not match. Since the hardware of v3 is basically identical to v2, the only problem is the version check during the firmware upgrade. But there is an easy workaround: | ==== Installation on HW rev.5 ==== |
| |
| - Install the current OpenWrt trunk version for v3 via the TP-Link web interface | * Normaly installing trought WEB interface |
| - (after the reboot) Via scp upload the current OpenWrt Chaos Calmer 15.05.1 stable release for v2 to "/tmp/**filename**", (e.g. with WinScp). After the reboot the router will have the ip-address 192.168.1.1 and the default OpenWrt user and password. | * Or you can use TFTP server: Rename OpenWrt or original firmware to **WR1043v5_tp_recovery.bin** Set static IP of your PC to *192.168.0.66/24* Router will obtain IP 192.168.0.86 for a few seconds while loading, when reset button pressed at power On. |
| - Log in via ssh (e.g. putty) and then execute ''sysupgrade -n -F /tmp/**filename**''. The sysupgrade will also complain about version mismatch (v2 vs. v3). But the ''-F'' switch forces it to flash the image anyway. | * If something goes wrong you always can use UART |
| - Wait for the process to finish with a reboot and be happy with Chaos Calmer 15.05.1 stable. :) | |
| |
| Needed OpenWrt Downloads: | ==== UART on HW rev.5 ==== |
| | trunk version for v3 | [[https://downloads.openwrt.org/snapshots/trunk/ar71xx/generic/openwrt-ar71xx-generic-tl-wr1043nd-v3-squashfs-factory.bin | openwrt-ar71xx-generic-tl-wr1043nd-v3-squashfs-factory.bin]]| | |
| | Chaos Calmer 15.05.1 stable for v2 | [[https://downloads.openwrt.org/chaos_calmer/15.05.1/ar71xx/generic/openwrt-15.05.1-ar71xx-generic-tl-wr1043nd-v2-squashfs-sysupgrade.bin | openwrt-15.05.1-ar71xx-generic-tl-wr1043nd-v2-squashfs-sysupgrade.bin]] | | |
| |
| Or, if you are familiar with a hex editor, you can change the file version in the v2 factory file. For an explanation how to do this, see below. | Before soldering the connector |
| | You need to solder the jumper between resistor and RX pin |
| |
| | {{:media:tplink:tl-wr1043:1043-v5-with-jumper.jpg?600|}} |
| |
| ==== How to install Chaos Calmer (15.05) on the V3 version with the V2 OpenWrt factory image ==== | |
| Since there is another TP-Link software installed on the V3 version of the router which does not accept the firmware file for the V2 version it is not possible to install CC on it.\\ | |
| But there is a little trick to install it anyways. | |
| |
| - Download the v**2** 15.05 factory image as shown [[https://downloads.openwrt.org/chaos_calmer/15.05/ar71xx/generic/openwrt-15.05-ar71xx-generic-tl-wr1043nd-v2-squashfs-factory.bin]] | |
| - With an Hex editor, change the version number in the header of the file from 02 to 03 and save the file. It is located in byte 43.\\ {{:media:tplink:tl-wr1043:tl-wr1043nd_version_nr_in_bin_header.jpg?200|}}\\ command-line version for linux: <code> echo -e "\003" | dd seek=67 bs=1 count=1 conv=notrunc of=firmware_file.bin</code> | |
| - Rename the file to ''wr1043v3_tp_recovery.bin'' and flash it via tftp as described above | |
| |
| |
| ==== Downloads for TL-WR1043ND v1.x ==== | |
| |
| ^ Branch ^ Type ^ Download link ^ | |
| | **Stable** (Chaos Calmer) | **Factory** | https://downloads.openwrt.org/chaos_calmer/15.05.1/ar71xx/generic/openwrt-15.05.1-ar71xx-generic-tl-wr1043nd-v1-squashfs-factory.bin | | |
| | ::: | **Upgrade** | https://downloads.openwrt.org/chaos_calmer/15.05.1/ar71xx/generic/openwrt-15.05.1-ar71xx-generic-tl-wr1043nd-v1-squashfs-sysupgrade.bin | | |
| | **Trunk** (Designated Driver) | **Factory** | https://downloads.openwrt.org/snapshots/trunk/ar71xx/generic/openwrt-ar71xx-generic-tl-wr1043nd-v1-squashfs-factory.bin | | |
| | ::: | **Upgrade** | https://downloads.openwrt.org/snapshots/trunk/ar71xx/generic/openwrt-ar71xx-generic-tl-wr1043nd-v1-squashfs-sysupgrade.bin | | |
| |
| ==== Downloads for TL-WR1043ND v2.x ==== | |
| |
| ^ Branch ^ Type ^ Download link ^ | |
| | **Stable** (Chaos Calmer) | **Factory** | https://downloads.openwrt.org/chaos_calmer/15.05.1/ar71xx/generic/openwrt-15.05.1-ar71xx-generic-tl-wr1043nd-v2-squashfs-factory.bin | | |
| | ::: | **Upgrade** | https://downloads.openwrt.org/chaos_calmer/15.05.1/ar71xx/generic/openwrt-15.05.1-ar71xx-generic-tl-wr1043nd-v2-squashfs-sysupgrade.bin | | |
| | **Trunk** (Designated Driver) | **Factory** | https://downloads.openwrt.org/snapshots/trunk/ar71xx/generic/openwrt-ar71xx-generic-tl-wr1043nd-v2-squashfs-factory.bin | | |
| | ::: | **Upgrade** | https://downloads.openwrt.org/snapshots/trunk/ar71xx/generic/openwrt-ar71xx-generic-tl-wr1043nd-v2-squashfs-sysupgrade.bin | | |
| |
| ==== Downloads for TL-WR1043ND v3.x ==== | |
| |
| ^ Branch ^ Type ^ Download link ^ | |
| | **Stable** (Chaos Calmer) | **Factory** | - | | |
| | ::: | **Upgrade** | - | | |
| | **Trunk** (Designated Driver) | **Factory** | https://downloads.openwrt.org/snapshots/trunk/ar71xx/generic/openwrt-ar71xx-generic-tl-wr1043nd-v3-squashfs-factory.bin| | |
| | ::: | **Upgrade** | https://downloads.openwrt.org/snapshots/trunk/ar71xx/generic/openwrt-ar71xx-generic-tl-wr1043nd-v3-squashfs-sysupgrade.bin| | |
| |
| ==== Flash Layout ==== | ==== Flash Layout ==== |
| Please read the article [[doc:techref:Flash.Layout]] for a better understanding. It contains a couple of explanations. Then let's have a quick view at flash layout of this particular device: | Please read the article [[docs:techref:flash.layout]] for a better understanding. It contains a couple of explanations. Then let's have a quick view at flash layout of this particular device: |
| |
| ^ TP-Link WR1043ND Flash Layout stock firmware ^^^^^^ | ^ TP-Link WR1043ND Flash Layout stock firmware ^^^^^^ |
| ^ Layer2 | | mtd1 **//kernel//** 1280KiB | mtd2 **//rootfs//** 6720KiB || | | ^ Layer2 | | mtd1 **//kernel//** 1280KiB | mtd2 **//rootfs//** 6720KiB || | |
| ^ <color magenta>mountpoint</color> | | | <color magenta>''/''</color> || | | ^ <color magenta>mountpoint</color> | | | <color magenta>''/''</color> || | |
| ^ filesystem | | | [[doc:techref:filesystems#overlayfs|overlayfs]] || | | ^ filesystem | | | [[docs:techref:filesystems#overlayfs|overlayfs]] || | |
| ^ Layer3 | | | 1536KiB | mtd3 **//rootfs_data//** 5184KiB | | | ^ Layer3 | | | 1536KiB | mtd3 **//rootfs_data//** 5184KiB | | |
| ^ <color magenta>mountpoint</color> | //none// | //none// | <color magenta>''/rom''</color> | <color magenta>''/overlay''</color> | //none// | | ^ <color magenta>mountpoint</color> | //none// | //none// | <color magenta>''/rom''</color> | <color magenta>''/overlay''</color> | //none// | |
| ^ filesystem | //none// | //none// | [[doc:techref:filesystems#SquashFS]] | [[doc:techref:filesystems#JFFS2]] | //none// | | ^ filesystem | //none// | //none// | [[docs:techref:filesystems#SquashFS]] | [[docs:techref:filesystems#JFFS2]] | //none// | |
| |
| ART = Atheros Radio Test - it contains mac addresses and calibration data for the wifi (EEPROM). If it is missing or corrupt, ath9k won't come up anymore. | ART = Atheros Radio Test - it contains mac addresses and calibration data for the wifi (EEPROM). If it is missing or corrupt, ath9k won't come up anymore. |
| |
| ==== Firmware flashing ==== | ==== Firmware flashing ==== |
| | |
| | <WRAP center round info 60%> |
| | This is an older device with multiple versions. These instructions have been written over the years and versions of devices. When following these instructions note that the IP address may be different for different versions of hardware and boot loader. |
| | |
| | Ensure that you are using the firmware version appropriate for your device. |
| | </WRAP> |
| |
| === Flashing / Recovery using tftp only (without serial console) === | === Flashing / Recovery using tftp only (without serial console) === |
| * Install a tftp server. This is host computer OS specific. | * Install a tftp server. This is host computer OS specific. |
| * On Mac OS X, you can start the built-in tftp server with ''$ sudo launchctl load -w /System/Library/LaunchDaemons/tftp.plist'' | * On Mac OS X, you can start the built-in tftp server with ''$ sudo launchctl load -w /System/Library/LaunchDaemons/tftp.plist'' |
| * Download a desired firmware (openwrt *factory.bin or the original firmware wr1043nv1_*_boot*.bin) and rename the *.bin file to wr1043v1_tp_recovery.bin in the tftpboot directory (if you use Tftpd check log viewer for read request from your router, to make sure your rename is correct). The v4 file needs to be named wr1043ndv4_tp_recovery.bin. | * Download a desired firmware (openwrt *factory.bin or the original firmware wr1043nv1_*_boot*.bin) and rename the *.bin file to wr1043nv1_tp_recovery.bin in the tftpboot directory (if you use Tftpd check log viewer for read request from your router, to make sure your rename is correct. It's good to mention here that if you use tftpd64 on Windows 11 it's possible that the log viewer may be empty. The log viewer was empty in my case under Windows 11, so probably the tftpd64 author should update his program). The v4 file needs to be named wr1043ndv4_tp_recovery.bin. |
| * On Mac OS X, copy the renamed file to /private/tftpboot/ | * On Mac OS X, copy the renamed file to /private/tftpboot/ |
| * Use a pin or paper clip to press down the reset button (in the hole besides the power adapter hole) and connect the power, while holding down the reset button for a few seconds | * Use a pin or paper clip to press down the reset button (in the hole besides the power adapter hole) and connect the power, while holding down the reset button for a few seconds |
| |
| **For v2.1 hardware:** | **For v2.1 hardware:** |
| | |
| The tftp server must be listening on 192.168.1.100:69 (Version 2.1 with U-Boot 1.1.4 (Jul 17 2015 - 14:31:22)) | The tftp server must be listening on 192.168.1.100:69 (Version 2.1 with U-Boot 1.1.4 (Jul 17 2015 - 14:31:22)) |
| |
| cp.b 0x80060000 0x9f020000 ${filesize} | cp.b 0x80060000 0x9f020000 ${filesize} |
| boot.m 0x9f020000 | boot.m 0x9f020000 |
| | </code> |
| | |
| | **For v3.x hardware:** |
| | |
| | The TFTP server must be listening on 192.168.0.66, file requested will be wr1043v3_tp_recovery.bin. |
| | <code> |
| | TFTP from server 192.168.0.66; our IP address is 192.168.0.86 |
| | Filename 'wr1043v3_tp_recovery.bin'. |
| | Load address: 0x80800000 |
| | Loading: ################################################################# |
| </code> | </code> |
| |
| |
| ==== Upgrading OpenWrt ==== | ==== Upgrading OpenWrt ==== |
| -> [[docs:user-guide:generic.sysupgrade]] | -> [[docs:guide-user:installation:generic.sysupgrade]] |
| |
| ==== Back to original firmware ==== | ==== Back to original firmware ==== |
| -> [[doc:howto:generic.uninstall]] | -> [[docs:guide-user:installation:generic.uninstall]] |
| |
| {{page>meta:infobox:dangerous&noheader&nofooter&noeditbtn}} | {{page>meta:infobox:dangerous&noheader&nofooter&noeditbtn}} |
| You should transfer the firmeware image to the /tmp folder and revert back to original firmware (if availlable you can flash the firmware via the webinterface as well): | You should transfer the firmeware image to the /tmp folder and revert back to original firmware (if availlable you can flash the firmware via the webinterface as well): |
| |
| Via the safer method using sysupgrade: | Via the safer method using sysupgrade (the `-n` makes sure that no leftover configs are preserved from openwrt): |
| <code> | <code> |
| sysupgrade /tmp/tplink.bin | sysupgrade -n /tmp/tplink.bin |
| </code> | </code> |
| |
| </code> | </code> |
| |
| This has been confirmed by [[https://forum.openwrt.org/viewtopic.php?pid=110583#p110583|supertom64]] (for the V1), and by [[https://forum.openwrt.org/viewtopic.php?pid=232448#p232448|akirkby]] (for the V2, flashing using the webinterface) | This has been confirmed by [[https://forum.openwrt.org/viewtopic.php?pid=110583#p110583|supertom64]] (for the V1), and by [[https://forum.openwrt.org/viewtopic.php?pid=232448#p232448|akirkby]] (for the V2, flashing using the webinterface). Also confirmed Feb 29, 2020 by darkspot for V1 and TL-WR*V1_140319. Back to stock can be necessary to enable freifunk when coming from pure openwrt. |
| |
| OEM TP-Link firmware for the TL-WR1043nd with the **//boot part removed//** to revert to the original OEM firmware: | As of Apr 04 2020 is also confirmed to work on TL-WR1043ND V2 on OpenWRT 19.07.02 installation: upload the **stripped** firmware on LuCi and check the force option - the router will come back on 192.168.**0**.1. |
| * TL-WR1043nd **//V1//** [[https://drive.google.com/uc?export=download&id=0B-pEMb4uQtg8eUN5RVFWekFIbFk|TL-WR1043ND-V1-stripped.zip]] | |
| * TL-WR1043nd **//V2//** [[https://drive.google.com/uc?export=download&id=0B-pEMb4uQtg8U0lRYWs5dVBTOHc|TL-WR1043ND-V2-stripped.zip]] | |
| * TL-WR1043nd **//V3//** [[http://www.xup.in/dl,79323997/wr1043nd_v3_stripped.zip/|TL-WR1043ND-V3-stripped.zip]] | |
| | ===== Warnings / Gotchas ===== |
| | |
| | ==== USB 3G Modems ==== |
| | | {{:meta:icons:tango:48px-emblem-important.svg.png?nolink}} | The TL-WR1043ND v1.x does **not** deliver enough power for most USB 3G modems, which can lead to erratic behavior such as dropped/failed connections. If a 3G USB modem is to be used, consider other routers with a USB port that delivers enough amperes (e.g. the [[:toh:buffalo:wzr-hp-ag300h|Buffalo WZR-HP-AG300H]]). | |
| | |
| | === USB 3G modems confirmed working with TL-WR1043ND v1: === |
| | * Huawei E303 |
| | * Huawei E303c |
| | * Huawei E3131 |
| | * Huawei E3272 |
| | * Huawei E3531 |
| | * Huawei E3533 (via usb-tethering) |
| | * ZTE MF823L |
| | * ZTE MF190 |
| | * ZTE MF193 |
| | * ZTE MF626 |
| | * ZTE MF667 (via usb-tethering, bad connection) |
| | |
| | === USB 3G modems confirmed working with TL-WR1043ND v2: === |
| | * TCT Mobile One Touch X500D |
| | * TCT Mobile X220L |
| | * ZTE MF632 |
| | * Vodafone K3765 (Huawei) |
| | * Huawei E160E |
| | * Huawei E3531 |
| | |
| | ==== Connection quality drops after a few hours, latency/ping/lag spikes ==== |
| | |
| | Still reproductible with release 15.05.1; gone in LEDE 17.01.4: |
| | If wireless performance becomes awful after a few hours and ping times to the router over wifi increase up to half a second or more, there's a good chance you're experiencing [[https://dev.openwrt.org/ticket/12372]] |
| | |
| | Restarting wireless with the "wifi" command makes the issue temporarily go away for the next few hours. Disabling ANI (Adaptive Noise Immunity) with the following command makes the issue go away until the next reboot |
| | '' |
| | echo 0 >/sys/kernel/debug/ieee80211/phy0/ath9k/ani |
| | '' |
| | |
| | For more details, including how to disable ANI at boot, see longer description of the same ANI issue on the [[toh:linksys:wrt160nl|Cisco WRT160NL]] page. |
| |
| ===== Basic configuration ===== | ===== Basic configuration ===== |
| After flashing, proceed with [[doc:howto:basic.config|Basic configuration]].\\ | After flashing, proceed with [[docs:guide-quick-start:checks_and_troubleshooting|Basic configuration]].\\ |
| Set up your Internet connection, configure wireless, configure USB port, etc. | Set up your Internet connection, configure wireless, configure USB port, etc. |
| |
| |
| ==== Failsafe mode ==== | ==== Failsafe mode ==== |
| See [[doc:howto:generic.failsafe|OpenWrt Failsafe Mode]] for general information. | See [[docs:guide-user:troubleshooting:failsafe_and_factory_reset|OpenWrt Failsafe Mode]] for general information. |
| |
| * Power up your router. When the 'SYS' LED starts to blink, press the //QSS// push button repeatedly until the blinking of 'SYS' LED gets faster. **Done** = You made OpenWrt **boot into OpenWrt failsafe mode.** Proceed with [[doc:howto:generic.failsafe#in.failsafe.mode|In OpenWrt Failsafe Mode]] | * Power up your router. When the 'SYS' LED starts to blink, press the //QSS// push button repeatedly until the blinking of 'SYS' LED gets faster. **Done** = You made OpenWrt **boot into OpenWrt failsafe mode.** Proceed with [[docs:guide-user:troubleshooting:failsafe_and_factory_reset#in.failsafe.mode|In OpenWrt Failsafe Mode]] |
| |
| ==== WiFi: Using other country regulations ==== | ==== WiFi: Using other country regulations ==== |
| Per default the WLan-"Country Code" is set to US. That means users of OpenWrt worldwide are limited to Channel 1-11. | Per default the [[:docs:guide-user:network:wifi:wifi_countrycode|WLan-"Country Code"]] is set to US. That means users of OpenWrt worldwide are limited to Channel 1-11. |
| |
| To unlock the specific channels of your country, it is possible to [[doc:start#building.openwrt|compile]] OpenWrt with "ATH_USER_REGD" set (recommended), or by patching the kernel modules (see: [[http://luci.subsignal.org/~jow/reghack/]]). | To unlock the specific channels of your country, it is possible to [[docs:guide-developer:toolchain:use-buildsystem|compile]] OpenWrt with "ATH_USER_REGD" set (recommended, and enabled by default in recent OpenWRT versions). |
| |
| WARNING: Do this only if you know what you're doing! Using the wrong frequencies can result in interfering with other radio services. | WARNING: Do this only if you know what you're doing! Using the wrong frequencies can result in interfering with other radio services. |
| ==== Get the usb working ==== | ==== Get the usb working ==== |
| |
| -> [[:doc:howto:usb.essentials]]\\ | -> [[:docs:guide-user:storage:usb-installing]]\\ |
| -> [[:doc:howto:usb.storage]] | -> [[docs:guide-user:storage:usb-drives]] |
| |
| On 14.07 the following packages were installed to let the usb work (Those are basically the packages described in the two pages linked above): | On 14.07 the following packages were installed to let the usb work (Those are basically the packages described in the two pages linked above): |
| TP-Link naming scheme is, that numbers behind the comma, refer to changes in the firmware only, the hardware is identical. | TP-Link naming scheme is, that numbers behind the comma, refer to changes in the firmware only, the hardware is identical. |
| |
| ^ Type ^ HW ver. 1.x ^ HW ver. 2.x ^ | ^ Type ^ HW ver. 1.x ^ HW ver. 2.x ^ HW ver. 5.x ^ |
| | **[[wp>Instruction set]]:** | [[wp>MIPS_instruction_set#MIPS32|MIPS32]] || | | **[[wp>Instruction set]]:** | [[wp>MIPS_instruction_set#MIPS32|MIPS32]] ||| |
| | **Vendor:** | [[wp>Qualcomm Atheros]] || | | **Vendor:** | [[wp>Qualcomm Atheros]] ||| |
| | **[[doc:techref:Bootloader]]:** | [[doc:techref:bootloader:uboot|U-Boot]] 1.1.4 || | | **[[docs:techref:bootloader]]:** | [[docs:techref:bootloader:uboot|U-Boot]] 1.1.4 || |
| | **[[doc:hardware:soc|System-On-Chip]]:** | AR9132 rev 2 | QCA9558 | | | **[[docs:techref:hardware:soc|System-On-Chip]]:** | AR9132 rev 2 | QCA9558 | |
| | **[[doc:hardware:cpu|CPU]]/Frq** | 24Kc V7.4 400 MHz | 74Kc V5.0 720 MHz | | | **[[docs:techref:hardware:cpu|CPU]]/Frq** | 24Kc V7.4 400 MHz | 74Kc V5.0 720 MHz | |
| | **Target name** | {{tagpage>ar71xx}} || | | **Target name** | {{tagpage>ar71xx}} ||| |
| | **Flash-Chip:** | [[http://www.spansion.com/Support/Datasheets/S25FL064P_00.pdf|ST 25P64V6P]] | [[http://www.nexflash.com/hq/enu/ProductAndSales/ProductLines/FlashMemory/SerialFlash/W25Q64FV.htm|Winbond 25Q64FV]] | | | **Flash-Chip:** | [[https://web.archive.org/web/20221021210048/https://www.infineon.com/dgdl/Infineon-S25FL064P_64-Mbit_3.0_V_SPI_Flash_Memory-DataSheet-v11_00-EN.pdf?fileId=8ac78c8c7d0d8da4017d0ed4dcb1535c&utm_source=cypress&utm_medium=referral&utm_campaign=202110_globe_en_all_integration-files|ST 25P64V6P]] | [[http://www.nexflash.com/hq/enu/ProductAndSales/ProductLines/FlashMemory/SerialFlash/W25Q64FV.htm|Winbond 25Q64FV]] | [[https://www.winbond.com/resource-files/w25q128fv%20rev.m%2005132016%20kms.pdf|Winbond 25Q128FVSG]] | |
| | **Flash size:** | 8192 KiB || | | **Flash size:** | 8192 KiB ||| |
| | **RAM:** | 32 MiB | 64 MiB | | | **RAM:** | 32 MiB | 64 MiB | |
| | **Wireless:** | Atheros AR9103 2.4 GHz 802.11bgn | QCA9558 2.4 GHz 802.11bgn | | | **Wireless:** | Atheros AR9103 2.4 GHz 802.11bgn | QCA9558 2.4 GHz 802.11bgn | |
| | **Wireless Power:** | 24 dBm (251 mW) | 25 dBm(316 mW)| | | **Wireless Power:** | 24 dBm (251 mW) | 25 dBm(316 mW) | |
| | **802.11n:** | 3 x 3 : 2 | 3 x 3 : 3 | | | **802.11n:** | 3 x 3 : 2 | 3 x 3 : 3 | |
| | **[[doc:hardware:Switch]]:** | [[http://realtek.info/pdf/rtl8366_8369_datasheet_1-1.pdf|RealTek RTL8366RB]] | [[http://wikidevi.com/files/Atheros/specsheets/AR8327_AR8327N.pdf|Atheros AR8327N-BL1A]] | | | **[[docs:techref:hardware:switch]]:** | [[http://realtek.info/pdf/rtl8366_8369_datasheet_1-1.pdf|RealTek RTL8366RB]] | [[http://wikidevi.com/files/Atheros/specsheets/AR8327_AR8327N.pdf|Atheros AR8327N-BL1A]] |[[https://github.com/Deoptim/atheros/raw/master/QCA8337-datasheet.pdf|Qualcomm Atheros QCA8337-AL3C]]| |
| | **[[doc/techref/swconfig]]:** | [[https://dev.openwrt.org/browser/trunk/target/linux/generic/files/drivers/net/phy/rtl8366rb.c|yes, rtl8366rb]] | [[https://dev.openwrt.org/browser/trunk/target/linux/generic/files/drivers/net/phy/ar8216.c|yes, ar8216]] | | | **[[docs:techref:swconfig]]:** | [[https://dev.openwrt.org/browser/trunk/target/linux/generic/files/drivers/net/phy/rtl8366rb.c|yes, rtl8366rb]] | [[https://dev.openwrt.org/browser/trunk/target/linux/generic/files/drivers/net/phy/ar8216.c|yes, ar8216]] | |
| | **USB:** | Yes 1 x 2.0 ([[wp>Open Host Controller Interface|OHCI]] platform; device name ''1-1'') || | | **USB:** | Yes 1 x 2.0 ([[wp>Open Host Controller Interface|OHCI]] platform; device name ''1-1'') || No | |
| | **Power:** | 12V DC 1.5A || | | **Power:** | 12V DC 1.5A || 9V DC 0.85A | |
| | **[[doc:hardware:port.serial|Serial]]:** | [[#Serial|Yes]] || | | **[[docs:techref:hardware:port.serial|Serial]]:** | [[#Serial|Yes]] ||| |
| | **[[doc:hardware:port.jtag|JTAG]]:** | [[#JTAG|Yes]] | [[#JTAG|No?]] | | | **[[docs:techref:hardware:port.jtag|JTAG]]:** | [[#JTAG|Yes]] | [[#JTAG|No?]] | |
| |
| ==== Performance ==== | ==== Performance ==== |
| * [[doc:hardware:performance|Filesystems & network performance]] results and [[doc:howto:performance]] howto for help on measuring. | * [[docs:techref:hardware:performance|Filesystems & network performance]] results and [[docs:guide-user:perf_and_log:performance]] howto for help on measuring. |
| * [[docs:user-guide:advanced:benchmark.usb|USB Benchmarks]] results. | * [[docs:guide-user:perf_and_log:benchmark.usb|USB Benchmarks]] results. |
| |
| * This router gets around 180 Megabits/s WAN to LAN throughput, tested using nuttcp. | * This router gets around 180 Megabits/s WAN to LAN throughput, tested using nuttcp. |
| Photos of v1.X PCB: | Photos of v1.X PCB: |
| |
| {{media:tplink:tl-wr1043:tl-wr1043nd-v14_pcb.jpg?400|PCB Board TP-Link TL-WR1043ND v1.4}} | {{media:tplink:tl-wr1043:tl-wr1043nd-v14_pcb.jpg?0x300|PCB Board TP-Link TL-WR1043ND v1.4}} |
| {{media:tplink:tl-wr1043:tl-wr1043nd-v16_pcb.jpg?400|PCB Board TP-Link TL-WR1043ND v1.6}} | {{media:tplink:tl-wr1043:tl-wr1043nd-v16_pcb.jpg?0x300|PCB Board TP-Link TL-WR1043ND v1.6}} |
| |
| |
| Photos of v2.X PCB: | Photos of v2.X PCB: |
| |
| {{media:tplink:tl-wr1043:tl-wr1043nd-v21_pcb.jpg?400|PCB TP-Link TL-WR1043ND v2.1}} | {{media:tplink:tl-wr1043:tl-wr1043nd-v21_pcb.jpg?0x300|PCB TP-Link TL-WR1043ND v2.1}} |
| {{media:tplink:tl-wr1043:tl-wr1043nd_images_board2.jpg?400|PCB TP-Link TL-WR1043ND v2.1}} | {{media:tplink:tl-wr1043:tl-wr1043nd_images_board2.jpg?0x300|PCB TP-Link TL-WR1043ND v2.1}} |
| |
| More photos of the v2 version: [[http://galeria.tech-blog.pl/TP-Link_TL-WR1043ND_v2/|TP-Link TL-WR1043ND v2]] | More photos of the v2 version: [[http://galeria.tech-blog.pl/TP-Link_TL-WR1043ND_v2/|TP-Link TL-WR1043ND v2]] |
| |
| ==== Serial ==== | ==== Serial ==== |
| -> [[doc:hardware:port.serial]] general information about the serial port, serial port cable, etc. | -> [[docs:techref:hardware:port.serial]] general information about the serial port, serial port cable, etc. |
| How to connect to Serial Port: | How to connect to Serial Port: |
| |
| |
| ==== JTAG ==== | ==== JTAG ==== |
| -> [[doc:hardware:port.JTAG]] general information about the JTAG port, JTAG cable, etc. | -> [[docs:techref:hardware:port.jtag]] general information about the JTAG port, JTAG cable, etc. |
| |
| {{media:tplink:tl-wr1043:tl-wr1043nd_jtagport.jpg?400|}} | {{media:tplink:tl-wr1043:tl-wr1043nd_jtagport.jpg?400|}} |
| |
| ==== GPIOs ==== | ==== GPIOs ==== |
| -> [[doc:hardware:port.GPIO]] | -> [[docs:techref:hardware:port.gpio]] |
| |
| The AR913x platform provides 22 GPIOs. Some of them are used by the router for status LEDs, buttons and to communicate with the RTL8366RB. The table below shows the results of some investigation: | The AR913x platform provides 22 GPIOs. Some of them are used by the router for status LEDs, buttons and to communicate with the RTL8366RB. The table below shows the results of some investigation: |
| | 19 | Clock line of the RTL8366RB ||||||| | | 19 | Clock line of the RTL8366RB ||||||| |
| | 20 | | GPIO20 | 3.3V | 0V | 1 | 0 | 1 | | | 20 | | GPIO20 | 3.3V | 0V | 1 | 0 | 1 | |
| | 21 | | | | | | | | | | 21 | USB PSU EN** | | | | | | | |
| |
| * USB power control for v1 hardware. GPIO 16 is for USB power enable and GPIO 15 is to check overcurrent, but resistors R706 and R708 must be soldered to use these GPIOs. | * USB power control for v1 hardware. GPIO 16 is for USB power enable and GPIO 15 is to check overcurrent, but resistors R706 and R708 must be soldered to use these GPIOs. |
| | ** USB power control for v2 hardware. GPIO 21 is for USB power enable, no hardware mods needed, works out of the box. |
| |
| To make the GPIOs available via sysfs, the required ones have to be exported to userspace, as it is explained on a page of the [[http://squidge.sourceforge.net/gpio/|Squidge-Project]]. Kernel modules occupying that resource need to be removed before (e.g. "leds-gpio" and "gpio-buttons"). In output-mode, voltage levels of the GPIOs were measured against GND, after the value 1 or 0 had been written to /sys/class/gpio/gpioX/value. In input-mode, the value of the file /sys/class/gpio/gpioX/value was read when the GPIO was floating (initial state), pulled to GND or pulled to Vcc. | To make the GPIOs available via sysfs, the required ones have to be exported to userspace, as it is explained on a page of the [[http://squidge.sourceforge.net/gpio/|Squidge-Project]]. Kernel modules occupying that resource need to be removed before (e.g. "leds-gpio" and "gpio-buttons"). In output-mode, voltage levels of the GPIOs were measured against GND, after the value 1 or 0 had been written to /sys/class/gpio/gpioX/value. In input-mode, the value of the file /sys/class/gpio/gpioX/value was read when the GPIO was floating (initial state), pulled to GND or pulled to Vcc. |
| |
| ==== LEDs ==== | ==== LEDs ==== |
| How to configure LEDs in general, see the LED section in the [[doc/uci/system]]. | How to configure LEDs in general, see the LED section in the [[docs:guide-user:base-system:led_configuration]]. |
| |
| The WR1043ND has 10 LEDs: | The WR1043ND has 10 LEDs: |
| |
| ==== Buttons ==== | ==== Buttons ==== |
| -> [[doc:howto:hardware.button]]. For custom action on pressing button [[doc:howto:hardware.button#using.atheros.00-button.uci|the easy way]] with ''00-button'' script works nicely. | -> [[docs:guide-user:hardware:hardware.button]]. For custom action on pressing button [[docs:guide-user:hardware:hardware.button#using.atheros.00-button.uci|the easy way]] with ''00-button'' script works nicely. |
| |
| The TP-Link TL-WR1043ND has two buttons: | The TP-Link TL-WR1043ND has two buttons: |
| The QSS button is located at the front and can be easily pressed with a finger. The Reset button is located at the back and cannot be pressed with a finger, you need a small item (pen typically) to push it in. | The QSS button is located at the front and can be easily pressed with a finger. The Reset button is located at the back and cannot be pressed with a finger, you need a small item (pen typically) to push it in. |
| |
| //:!: Note: you don't need to configure or activate buttons to get the [[toh:tp-link:tl-wr1043nd#failsafe.mode|Failsafe mode]] working, it will work by default.// | //:!: Note: you don't need to configure or activate buttons to get the [[#failsafe_mode|Failsafe mode]] working, it will work by default.// |
| |
| //:!: Note2: From versions 1.8 up to 2.x holding the reset button for more than 30' resets to OpenWrt initial settings.// | //:!: Note2: From versions 1.8 up to 2.x holding the reset button for more than 30' resets to OpenWrt initial settings.// |
| |
| ===== Debricking ===== | ===== Debricking ===== |
| -> [[docs:user-guide:generic.debrick]] | -> [[docs:guide-user:troubleshooting:generic.debrick]] |
| |
| **NOTE:** If you accidentally bricked your router by overwriting the bootloader, try the following: | **NOTE:** If you accidentally bricked your router by overwriting the bootloader, try the following: |
| |
| ===== Bootloader Mods ===== | ===== Bootloader Mods ===== |
| - you could read about [[doc:techref:bootloader]] in general and about [[doc:techref:bootloader:uboot|Das U-Boot]]/[[doc:techref:bootloader:uboot.config|Configuration of U-Boot]] in particular. | - you could read about [[docs:techref:bootloader]] in general and about [[docs:techref:bootloader:uboot|Das U-Boot]]/[[docs:techref:bootloader:uboot.config|Configuration of U-Boot]] in particular. |
| - the uboot version you find on the 1043 is a fork of mainline U-Boot version 1.1.4 from 2005-12-17 [[ftp://ftp.denx.de/pub/u-boot/|see here]]. You can / you cannot FIXME take a current mainline version of uboot and simply cross-compile it for WR1043ND! TP-Link-Version: [[http://www.tp-link.com/support/gpl.asp]]. It contains the file ''u-boot-ap83.tar.bz2'' which is about 6,06 MiB in size, deflate this as well. The deflated source code will occupy about 37MiB of space, start with reading the ''README''. | - the uboot version you find on the 1043 is a fork of mainline U-Boot version 1.1.4 from 2005-12-17 [[ftp://ftp.denx.de/pub/u-boot/|see here]]. You can / you cannot FIXME take a current mainline version of uboot and simply cross-compile it for WR1043ND! TP-Link-Version: [[http://www.tp-link.com/support/gpl.asp]]. It contains the file ''u-boot-ap83.tar.bz2'' which is about 6,06 MiB in size, deflate this as well. The deflated source code will occupy about 37MiB of space, start with reading the ''README''. |
| - also see [[ftp://ftp.denx.de/pub/u-boot/]] and compare the versions. | - also see [[ftp://ftp.denx.de/pub/u-boot/]] and compare the versions. |
| - you may be able to cross compile the code with the OpenWrt [[wp>toolchain]] [[http://buildroot.org/|Buildroot]]. See [[doc:howto:build]] for guidance. But you may need to use other toolchain to crosscompile, like the ELDK (Embedded Linux Development Kit). | - you may be able to cross compile the code with the OpenWrt [[wp>toolchain]] [[http://buildroot.org/|Buildroot]]. See [[docs:guide-developer:toolchain:start]] for guidance. But you may need to use other toolchain to crosscompile, like the ELDK (Embedded Linux Development Kit). |
| - :!: **''Problem:''** you cannot test your bootloader, because for some obscure reason, you don't have write access to the flash via [[#JTAG]]. | - :!: **''Problem:''** you cannot test your bootloader, because for some obscure reason, you don't have write access to the flash via [[#JTAG]]. |
| |
| ==== Making bootloader partition writable ==== | ==== Making bootloader partition writable ==== |
| | |
| | === Permanent method === |
| |
| Look at target/linux/ar71xx/files/arch/mips/ar71xx/mach-tl-wr1043nd.c (in trunk it's target/linux/ar71xx/files/drivers/mtd/tplinkpart.c) | Look at target/linux/ar71xx/files/arch/mips/ar71xx/mach-tl-wr1043nd.c (in trunk it's target/linux/ar71xx/files/drivers/mtd/tplinkpart.c) |
| for the partition named "u-boot" to make it writeable. | for the partition named "u-boot" to make it writeable. |
| |
| | === Temporary method === |
| | <code> |
| | opkg install kmod-mtd-rw |
| | insmod mtd-rw i_want_a_brick=1 |
| | dd if=./FILE of=/dev/mtdX |
| | </code> |
| ==== Change MAC Address ==== | ==== Change MAC Address ==== |
| |
| |
| ===== Hardware Mods ===== | ===== Hardware Mods ===== |
| As a beginner, you really should inform yourself about [[doc:hardware:soldering]] in general and then even obtain some experience! | As a beginner, you really should inform yourself about [[docs:techref:hardware:soldering]] in general and then even obtain some experience! |
| | |
| | ==== 64MB RAM Mod for v1 model ==== |
| | <WRAP center round info 60%> |
| | V2 Model uses DDR2 BGA chip: Zentel A3R12E40CBF |
| | </WRAP> |
| |
| ==== 64MB RAM Mod ==== | |
| The Device uses a DDR1 16Mbit x 16bit (16Mibit*16=256 mebibit. 256 mebibit/8=32MiByte) 400MHz chip. Replace it with any 32Mbit x 16bit chip. 333MHz instead of 400MHz also works fine. It's quite hard to find these chips. The best chance is to have a look at DDR-SODIMM. Since there are no 64Mbit x 16Bit DDR1 Chips available -> no 128 MB mod! | The Device uses a DDR1 16Mbit x 16bit (16Mibit*16=256 mebibit. 256 mebibit/8=32MiByte) 400MHz chip. Replace it with any 32Mbit x 16bit chip. 333MHz instead of 400MHz also works fine. It's quite hard to find these chips. The best chance is to have a look at DDR-SODIMM. Since there are no 64Mbit x 16Bit DDR1 Chips available -> no 128 MB mod! |
| |
| * Hynix HY5DU121622CTP-J (PC333 DDR RAM) | * Hynix HY5DU121622CTP-J (PC333 DDR RAM) |
| * Infineon HYB25D512160BE (From Infineon DDR-SODIMM 512 MB) | * Infineon HYB25D512160BE (From Infineon DDR-SODIMM 512 MB) |
| * Nanya NT5DS32M16BS-6K (From DDR-SODIMM 512 MB, 333MHz), update: restarting device fail every time, have to power un-replug. Plus the kernel still report 200Mhz RAM speed, and this feels RAM overclocking. Changing to Hynix DDR400 fix the restarting hang bug. | * EtronTech EM6AB160TSA-5G (PC400 200MHz) |
| | * Nanya NT5DS32M16BS-6K (From DDR-SODIMM 512 MB, 333MHz), update: restarting device fail every time, have to power un-replug. Plus the kernel still report 200MHz RAM speed, and this feels RAM overclocking. Changing to Hynix DDR400 fix the restarting hang bug. |
| |
| |
| </code> | </code> |
| |
| A more convenient way to add an I2C-bus to this router, without a modification of the internal hardware (and risking your warranty), is using the [[doc:howto:usb.i2c-tiny-usb|I²C Tiny-USB]] adapter. The downsides are, that it is not as cheap as the I²C-GPIO mod, and the longterm-stability is lower (temporary USB disconnects can occur randomly or due to EMI, but the I2C-subsystem is not designed for sudden disconnects). Remember this bus runs at 5V level, when connecting I²C-devices. | A more convenient way to add an I2C-bus to this router, without a modification of the internal hardware (and risking your warranty), is using the [[docs:guide-user:hardware:usb.i2c-tiny-usb|I²C Tiny-USB]] adapter. The downsides are, that it is not as cheap as the I²C-GPIO mod, and the longterm-stability is lower (temporary USB disconnects can occur randomly or due to EMI, but the I2C-subsystem is not designed for sudden disconnects). Remember this bus runs at 5V level, when connecting I²C-devices. |
| |
| ==== Flash Mod ==== | ==== Flash Mod ==== |
| | |
| | Update (2020. 02. 24.): |
| | The following instructions are working only with target: ar71xx, because ar71xx images automaticly correct the size of the overlay partition. |
| | The new ATH79 target currently (and propably later) miss this feature. |
| | Even updating modded unit result limited flash size (8Mb), and most propably lose of wifi (ART partition missplace). |
| | At the end of the tutorial you can read updated information how to migrate to ATH79 target. |
| | End of Update |
| | |
| You can install 16 MB flash Winbound 25Q128 | You can install 16 MB flash Winbound 25Q128 |
| |
| | Tested method on HW version 1, board version: 1.8: |
| | The board has SOP16 (16 pin) flash chip pin layout, BUT under it also a SOP8 (discovered during the update process :) ) |
| |
| | (I am windows guy mainly) |
| | |
| | 1. Backup "boot", and "ART" partition: |
| | list partitions: |
| | cat /proc/mtd |
| | |
| | backup: |
| | cat /dev/mtd0 > /tmp/mtd0.bin |
| | cat /dev/mtd4 > /tmp/mtd4.bin |
| | The 2 .bin file can be saved with winscp on windows, most easily. |
| | |
| | 2. Create "empty" file: |
| | You have to create image file, with the following layout: |
| | BOOT+"actual openwrt factory image"+"empty file"+ART |
| | The final image size have to match the size of the flash (16M), |
| | so you have to play with the size of the "empty file". |
| | |
| | under linux: |
| | dd if=/dev/zero bs=1 count=FILESIZE | tr "\000" "\377" > empty |
| | You HAVE TO set the FILESIZE |
| | |
| | 3. Create new flash file data (for flash programing): |
| | In windows: |
| | copy /B mtd0.bin+"actual openwrt factory image"+"empty file (wich means all FF)"+mtd4.bin final.bin |
| | |
| | 4. Flash with programmer. |
| | I had used one TL866II Plus. |
| | Don't buy "CH341A", it is garbage, voltages incorrect, ect. |
| | |
| | 5. Replace "U14" marked flash chip, and boot. |
| | The overlay partition size will autocorrect at the first boot. |
| | |
| | 6. Profit. |
| | |
| | SSH was not worked until seting the interfeace (to "lan"). (?) 18.06.1 specific? |
| | |
| | Wifi tested, working. |
| | |
| | Best of luck! |
| | |
| | 7. Update: Second mod with one SOP8 pinout flash confirmed to work. (HW version 1, Board version 1.8) |
| | |
| | ATH97 migration update (2020. 02. 24): |
| | |
| | As, you can read here: |
| | https://forum.openwrt.org/t/using-release-ath79-19-07-0-kernel-and-packages-on-hardware-modded-tp-link-wr703n-16mb-64mb-without-snapshot-compilation/54310/7 |
| | |
| | Another great user ([[https://forum.openwrt.org/u/Tarask1n/summary|Tarask1n]]) of the openwrt forum had simmilar problems with the Tp-Link WR-703n unit. |
| | Results of his great work, he created a script, which can patch the original kernel to utilize the full available flash (eg: 16M) |
| | |
| | The patch can be reached from here (With absolutely no warranty, you have the full responsibility!) |
| | https://1drv.ms/u/s!Agn0XLRpyDNbiMAf1ZuhQ_lfcGmkIg?e=PNttUU |
| | |
| | To make this script work you need to have an - openwrt patched - lzma utility. |
| | As a linux nooby (me), the easyest was (which was not easy), to clone the openwrt github repo, and compile/make menuconfig. |
| | On Ubuntu 18.04 LTS i had a ton of dependency problems, and most of them was not an easy google search. |
| | |
| | My succesful build was needed further editing of imagebuilder configuration files as the following: |
| | |
| | Edited: openwrt-imagebuilder-19.07.1-ath79-generic.Linux-x86_64\target\linux\ath79\image\common-tp-link.mk |
| | Add lines: |
| | |
| | define Device/tplink-16m |
| | $(Device/tplink) |
| | TPLINK_FLASHLAYOUT := 16M |
| | IMAGE_SIZE := 15872k |
| | endef |
| | |
| | Edited: openwrt-imagebuilder-19.07.1-ath79-generic.Linux-x86_64\target\linux\ath79\image\generic-tp-link.mk |
| | |
| | Search for: |
| | |
| | define Device/tplink_tl-wr1043nd-v1 |
| | $(Device/tplink-8m) |
| | ATH_SOC := ar9132 |
| | DEVICE_TITLE := TP-Link TL-WR1043N/ND v1 |
| | DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport |
| | TPLINK_HWID := 0x10430001 |
| | SUPPORTED_DEVICES += tl-wr1043nd |
| | endef |
| | TARGET_DEVICES += tplink_tl-wr1043nd-v1 |
| | |
| | Change it to (1 line change): |
| | |
| | define Device/tplink_tl-wr1043nd-v1 |
| | $(Device/tplink-16m) |
| | ATH_SOC := ar9132 |
| | DEVICE_TITLE := TP-Link TL-WR1043N/ND v1 |
| | DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport |
| | TPLINK_HWID := 0x10430001 |
| | SUPPORTED_DEVICES += tl-wr1043nd |
| | endef |
| | TARGET_DEVICES += tplink_tl-wr1043nd-v1 |
| | |
| | After build, i had: |
| | |
| | 16.253.928 byte long "...factory.bin" image >>> This image was not tested! |
| | |
| | 3.735.822 byte long "...sysupgrade.bin" image >>> This image was tested, and did proper ar71xx > ATH79 migration. Wifi was working, flash size was correct. |
| ===== Other models with the same hardware ===== | ===== Other models with the same hardware ===== |
| |
| * [[http://www.proware.com.cn/product-detail.asp?productId=1010195&t=4#info|Proware PW-RN611D/MH5-WR1043ND]] probably another clone... | * [[http://www.proware.com.cn/product-detail.asp?productId=1010195&t=4#info|Proware PW-RN611D/MH5-WR1043ND]] probably another clone... |
| * [[:toh:tp-link:tl-wdr7500|TP-Link TL-WDR7500]] TP-Link TL-WDR7500 / TP-Link Archer C7 AC1750 (similar hardware to v2.1) | * [[:toh:tp-link:tl-wdr7500|TP-Link TL-WDR7500]] TP-Link TL-WDR7500 / TP-Link Archer C7 AC1750 (similar hardware to v2.1) |
| * [[TP-Link TL-WR1045ND]] Looks similar to hardware V3 | * [[https://wikidevi.com/wiki/TP-LINK_TL-WR1045ND|TL-WR1045ND]] Looks similar to hardware V3 |
| | ==== OpenVPN performance ==== |
| | This was done with an v5 version. (775MHZ) |
| | |
| | <WRAP bootlog> |
| | root@OpenWrt:~# iperf3 -c 10.4.20.10 -p 5201 -t 10 |
| | Connecting to host 10.4.20.10, port 5201 |
| | [ 5] local 10.0.4.2 port 37506 connected to 10.4.20.10 port 5201 |
| | [ ID] Interval Transfer Bitrate Retr Cwnd |
| | [ 5] 0.00-1.00 sec 1.88 MBytes 15.7 Mbits/sec 0 142 KBytes |
| | [ 5] 1.00-2.00 sec 1.88 MBytes 15.7 Mbits/sec 0 233 KBytes |
| | [ 5] 2.00-3.00 sec 1.75 MBytes 14.7 Mbits/sec 0 326 KBytes |
| | [ 5] 3.00-4.00 sec 1.88 MBytes 15.7 Mbits/sec 0 421 KBytes |
| | [ 5] 4.00-5.00 sec 1.75 MBytes 14.7 Mbits/sec 18 339 KBytes |
| | [ 5] 5.00-6.00 sec 1.75 MBytes 14.7 Mbits/sec 0 390 KBytes |
| | [ 5] 6.00-7.00 sec 1.88 MBytes 15.7 Mbits/sec 0 430 KBytes |
| | [ 5] 7.00-8.00 sec 2.00 MBytes 16.8 Mbits/sec 0 455 KBytes |
| | [ 5] 8.00-9.00 sec 1.62 MBytes 13.6 Mbits/sec 0 469 KBytes |
| | [ 5] 9.00-10.00 sec 2.12 MBytes 17.8 Mbits/sec 0 476 KBytes |
| | - - - - - - - - - - - - - - - - - - - - - - - - - |
| | [ ID] Interval Transfer Bitrate Retr |
| | [ 5] 0.00-10.00 sec 18.5 MBytes 15.5 Mbits/sec 18 sender |
| | [ 5] 0.00-10.26 sec 18.6 MBytes 15.2 Mbits/sec receiver |
| | |
| | iperf Done. |
| | </WRAP>\\ |
| | |
| | ==== OEM bootlog from v5 ==== |
| | <WRAP bootlog> |
| | |
| | < uBOOT should be here > |
| | < GARBAGE from my raspi - Serial... > |
| | |
| | 20000-0x000000040000 : "u-boot" |
| | [ 0.480000] 0x000000040000-0x000000160000 : "uImage" |
| | [ 0.480000] 0x000000160000-0x000000ff0000 : "rootfs" |
| | [ 0.490000] mtd: partition "rootfs" set to be root filesystem |
| | [ 0.500000] 0x000000ff0000-0x000001000000 : "ART" |
| | [ 0.500000] flash_chrdev : flash_chrdev_init |
| | [ 0.640000] ag71xx_mdio: probed |
| | [ 0.650000] eth0: Atheros AG71xx at 0xb9000000, irq 4 |
| | [ 1.230000] eth0: Atheros AR8327 switch driver attached. |
| | [ 4.150000] ag71xx ag71xx.0: eth0: connected to PHY at ag71xx-mdio.0:00 [uid=004dd036, driver=Atheros AR8216/AR8236/AR8316] |
| | [ 4.170000] TCP cubic registered |
| | [ 4.170000] NET: Registered protocol family 17 |
| | [ 4.170000] Bridge firewalling registered |
| | [ 4.180000] 8021q: 802.1Q VLAN Support v1.8 |
| | [ 4.180000] ### of_selftest(): No testcase data in device tree; not running tests |
| | [ 4.200000] VFS: Mounted root (squashfs filesystem) readonly on device 31:3. |
| | [ 4.200000] Freeing unused kernel memory: 180k freed |
| | - preinit - |
| | - regular preinit - |
| | jffs2 not ready yet; using ramdisk |
| | - init - |
| | [ 6.460000] liblog: module license 'unspecified' taints kernel. |
| | [ 6.460000] Disabling lock debugging due to kernel taint |
| | [ 6.730000] NET: Registered protocol family 10 |
| | [ 6.870000] SCSI subsystem initialized |
| | [ 7.040000] Button Hotplug driver version 0.4.1 |
| | [ 7.120000] PPP generic driver version 2.4.2 |
| | [ 7.140000] tun: Universal TUN/TAP device driver, 1.6 |
| | [ 7.150000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com> |
| | [ 7.220000] PPP MPPE Compression module registered |
| | [ 7.230000] NET: Registered protocol family 24 |
| | [ 7.330000] L2TP core driver, V2.0 |
| | [ 7.340000] L2TP netlink interface |
| | [ 7.420000] IPv6 over IPv4 tunneling driver |
| | [ 7.460000] GRE over IPv4 demultiplexor driver |
| | [ 7.500000] GRE over IPv4 tunneling driver |
| | [ 7.550000] bonding: Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) |
| | [ 7.670000] ip_tables: (C) 2000-2006 Netfilter Core Team |
| | [ 7.840000] nf_conntrack version 0.5.0 (960 buckets, 3840 max) |
| | [ 8.070000] PPPoL2TP kernel driver, V2.0 |
| | [ 8.110000] PPTP driver version 0.8.5 |
| | [ 8.480000] xt_time: kernel timezone is -0000 |
| | [ 8.840000] nf_conntrack_rtsp v0.6.21 loading |
| | [ 8.860000] nf_nat_rtsp v0.6.21 loading |
| | [ 8.900000] Netfilter messages via NETLINK v0.30. |
| | [ 8.940000] ctnetlink v0.93: registering with nfnetlink. |
| | [ 9.200000] ssdk_plat_init start |
| | [ 9.200000] Register QCA PHY driver |
| | [ 9.320000] qca-ssdk module init succeeded! |
| | [ 9.470000] fuse init (API version 7.18) |
| | reloadconfig() begin: |
| | reloadconfig() end: |
| | mergeconfigbycountry() begin |
| | user has set country |
| | mergeconfigbycountry() do nothing end |
| | reload_profile() begin: |
| | reload_profile() end: |
| | |
| | Please press Enter to activate this console. [ 12.190000] ADDRCONF(NETDEV_UP): eth0: link is not ready |
| | GMT+00:00 |
| | Fri Jan 1 00:00:00 GMT 2016 |
| | [SWITCH DEBUG] Clear Port(0) PVID |
| | [SWITCH DEBUG] Clear Port(1) PVID |
| | [SWITCH DEBUG] Clear Port(2) PVID |
| | [SWITCH DEBUG] Clear Port(3) PVID |
| | [SWITCH DEBUG] Clear Port(4) PVID |
| | [SWITCH DEBUG] Clear Port(5) PVID |
| | [SWITCH DEBUG] Flush vlan entries. |
| | [SWITCH DEBUG] Create VLAN VID=1 |
| | [SWITCH DEBUG] Add tagged port(0) to VLAN(1) |
| | [SWITCH DEBUG] Add untagged port(1) to VLAN(1) |
| | [SWITCH DEBUG] Add untagged port(2) to VLAN(1) |
| | [SWITCH DEBUG] Add untagged port(3) to VLAN(1) |
| | [SWITCH DEBUG] Add untagged port(4) to VLAN(1) |
| | [SWITCH DEBUG] Set Port(0) PVID(1) |
| | [SWITCH DEBUG] Set Port(0) ingress to secure |
| | [SWITCH DEBUG] Set Port(1) PVID(1) |
| | [SWITCH DEBUG] Set Port(1) ingress to secure |
| | [SWITCH DEBUG] Set Port(2) PVID(1) |
| | [SWITCH DEBUG] Set Port(2) ingress to secure |
| | [SWITCH DEBUG] Set Port(3) PVID(1) |
| | [SWITCH DEBUG] Set Port(3) ingress to secure |
| | [SWITCH DEBUG] Set Port(4) PVID(1) |
| | [SWITCH DEBUG] Set Port(4) ingress to secure |
| | [SWITCH DEBUG] Create VLAN VID=4094 |
| | [SWITCH DEBUG] Add tagged port(0) to VLAN(4094) |
| | [SWITCH DEBUG] Add untagged port(5) to VLAN(4094) |
| | [SWITCH DEBUG] Set Port(0) PVID(4094) |
| | [SWITCH DEBUG] Set Port(0) ingress to secure |
| | [SWITCH DEBUG] Set Port(5) PVID(4094) |
| | [SWITCH DEBUG] Set Port(5) ingress to secure |
| | [SWITCH DEBUG] Set Port(0) PVID(0) |
| | [ 13.850000] device eth0 entered promiscuous mode |
| | [ 13.850000] ADDRCONF(NETDEV_UP): eth0.4094: link is not ready |
| | [ 14.220000] ADDRCONF(NETDEV_UP): lo: link is not ready |
| | [ 14.230000] ADDRCONF(NETDEV_UP): eth0: link is not ready |
| | [ 14.230000] ADDRCONF(NETDEV_UP): ip6tnl0: link is not ready |
| | [ 14.240000] ADDRCONF(NETDEV_UP): sit0: link is not ready |
| | [ 14.240000] ADDRCONF(NETDEV_UP): gre0: link is not ready |
| | [ 14.250000] ADDRCONF(NETDEV_UP): bond0: link is not ready |
| | [ 14.250000] ADDRCONF(NETDEV_UP): eth0.4094: link is not ready |
| | [ 14.370000] eth0: link up (1000Mbps/Full duplex) |
| | [ 14.380000] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready |
| | [ 14.400000] ADDRCONF(NETDEV_CHANGE): eth0.4094: link becomes ready |
| | [ 15.490000] ar8216_read_status_2991: eth0.4094 carrier off! |
| | Loading defaults |
| | Loading synflood protection |
| | Adding custom chains |
| | Loading zones |
| | Loading forwardings |
| | Loading rules |
| | Loading redirects |
| | Loading includes |
| | Optimizing conntrack |
| | Loading interfaces |
| | Loading tpcmd |
| | [ 19.740000] device eth0 left promiscuous mode |
| | [ 19.750000] del ct event: 2 dev_name: eth0.4094 |
| | [ 19.760000] start clean up ct iterate.. |
| | [ 19.770000] device eth0 entered promiscuous mode |
| | [ 19.800000] del ct event: 2 dev_name: eth0.1 |
| | [ 19.800000] start clean up ct iterate.. |
| | [ 19.820000] device eth0.1 entered promiscuous mode |
| | [ 19.820000] br-lan: port 1(eth0.1) entered forwarding state |
| | [ 19.830000] br-lan: port 1(eth0.1) entered forwarding state |
| | loading access_control |
| | loading basic_security |
| | [ 20.640000] ar8216_read_status_2991: eth0.1 carrier off! |
| | [ 20.650000] ar8216_read_status_2991: eth0.4094 carrier off! |
| | [ 20.650000] br-lan: port 1(eth0.1) entered disabled state |
| | [ 23.050000] start clean up ct iterate.. |
| | [ 23.080000] start clean up ct iterate.. |
| | conntrack v1.0.0 (conntrack-tools): connection tracking table has been emptied. |
| | [ 31.240000] start clean up ct iterate.. |
| | Normal env generate |
| | Flush nat forwarding chain |
| | loading administration management |
| | fw unload_local_mgnt |
| | loading parental_control |
| | |
| | SSDK Init OK![ 33.510000] enable:1 |
| | [ 33.510000] bg task init successfull! |
| | [ 33.520000] host_helper_init start |
| | [ 33.530000] /proc/qca_switch/nf_athrs17_hnat is created |
| | [ 33.530000] /proc/qca_switch/nf_athrs17_hnat_wan_type is created |
| | [ 33.540000] /proc/qca_switch/nf_athrs17_hnat_ppp_id is created |
| | [ 33.540000] /proc/qca_switch/nf_athrs17_hnat_udp_thresh is created |
| | [ 33.550000] /proc/qca_switch/nf_athrs17_hnat_wan_ip is created |
| | [ 33.560000] /proc/qca_switch/nf_athrs17_hnat_ppp_peer_ip is created |
| | [ 33.560000] /proc/qca_switch/nf_athrs17_hnat_ppp_peer_mac is created |
| | [ 33.570000] /proc/qca_switch/nf_athrs17_hnat_wan_mac is created |
| | [ 33.570000] /proc/qca_switch/nf_athrs17_hnat_ppp_id2 is created |
| | [ 33.580000] /proc/qca_switch/nf_athrs17_hnat_ppp_peer_mac is created |
| | [ 33.590000] Adding ACL rules 15 - upnp_ssdp_add_acl_rules |
| | [ 33.610000] ACL is not yet enabled. Enabling... |
| | [ 33.620000] Adding ACL rules 7 - ipv6_snooping_solicted_node_add_acl_rules |
| | [ 33.670000] Adding ACL rules 11 - ipv6_snooping_sextuple0_group_add_acl_rules |
| | [ 33.720000] Adding ACL rules 13 - ipv6_snooping_quintruple0_1_group_add_acl_rules |
| | [ 33.770000] Hello, nat helper module for 1.1! |
| | [ 33.790000] register inet_notifier### |
| | |
| | operate done. |
| | |
| | |
| | SSDK Init OK![ 33.800000] enable:0 |
| | [ 33.800000] unregister inet_notifier### |
| | [ 33.800000] /proc/qca_switch/nf_athrs17_hnat removed |
| | [ 35.790000] Goodbye, nat helper module! |
| | |
| | operate done. |
| | |
| | [ 40.520000] ****Address of trace_timer :8240a610 |
| | [ 40.860000] ath_hal: 0.9.17.1 (AR5416, AR9380, REGOPS_FUNC, WRITE_EEPROM, TX_DATA_SWAP, RX_DATA_SWAP, 11D) |
| | [ 40.920000] ath_rate_atheros: Copyright (c) 2001-2005 Atheros Communications, Inc, All Rights Reserved |
| | [ 41.000000] ath_dfs: Version 2.0.0 |
| | [ 41.000000] Copyright (c) 2005-2006 Atheros Communications, Inc. All Rights Reserved |
| | [ 41.030000] ath_spectral: Version 2.0.0 |
| | [ 41.030000] Copyright (c) 2005-2009 Atheros Communications, Inc. All Rights Reserved |
| | [ 41.050000] SPECTRAL module built on Oct 25 2016 11:22:49 |
| | [ 41.110000] ath_tx99: Version 2.0 |
| | [ 41.110000] Copyright (c) 2010 Atheros Communications, Inc, All Rights Reserved |
| | [ 41.300000] ath_dev: Copyright (c) 2001-2007 Atheros Communications, Inc, All Rights Reserved |
| | [ 43.490000] __ath_attach: Set global_scn[0] |
| | [ 43.500000] *** All the minfree values should be <= ATH_TXBUF-32, otherwise default value will be used instead *** |
| | [ 43.510000] ACBKMinfree = 48 |
| | [ 43.510000] ACBEMinfree = 32 |
| | [ 43.510000] ACVIMinfree = 16 |
| | [ 43.520000] ACVOMinfree = 0 |
| | [ 43.520000] CABMinfree = 48 |
| | [ 43.520000] UAPSDMinfree = 0 |
| | [ 43.530000] ATH_TXBUF=540 |
| | [ 43.540000] Enterprise mode: 0x03bda000 |
| | [ 43.540000] |
| | [ 43.540000] ART Version : -48.0.0 |
| | [ 43.550000] SW Image Version : -48.0.0.0.0 |
| | [ 43.550000] Board Revision : |
| | [ 43.560000] ar9300_attach: nf_2_nom -110 nf_2_max -60 nf_2_min -125 |
| | [ 43.560000] SPECTRAL : get_capability not registered |
| | [ 43.570000] HAL_CAP_PHYDIAG : Capable |
| | [ 43.570000] SPECTRAL : Need to fix the capablity check for RADAR (spectral_attach : 231) |
| | [ 43.580000] SPECTRAL : get_capability not registered |
| | [ 43.590000] HAL_CAP_RADAR : Capable |
| | [ 43.590000] SPECTRAL : Need to fix the capablity check for SPECTRAL |
| | [ 43.590000] (spectral_attach : 236) |
| | [ 43.600000] SPECTRAL : get_capability not registered |
| | [ 43.610000] HAL_CAP_SPECTRAL_SCAN : Capable |
| | [ 43.610000] SPECTRAL : get_tsf64 not registered |
| | [ 43.620000] spectral_init_netlink 65 NULL SKB |
| | [ 43.620000] SPECTRAL : No ADVANCED SPECTRAL SUPPORT |
| | [ 43.620000] SPECTRAL :----- module attached |
| | [ 43.630000] Green-AP : Green-AP : Attached |
| | [ 43.630000] |
| | [ 43.640000] ath_get_caps[6169] rx chainmask mismatch actual 7 sc_chainmak 0 |
| | [ 43.650000] ath_get_caps[6144] tx chainmask mismatch actual 7 sc_chainmak 0 |
| | [ 43.660000] band steering initialized for direct attach hardware |
| | [ 43.660000] ieee80211_bsteering_attach: Band steering initialized |
| | [ 43.670000] ath_attach_dfs[12687] dfsdomain 1 |
| | [ 43.690000] SPECTRAL : module already attached |
| | [ 43.690000] osif_wrap_attach:296 osif wrap attached |
| | [ 43.690000] osif_wrap_devt_init:916 osif wrap dev table init done |
| | [ 43.700000] ath_tx_paprd_init sc 82480000 PAPRD disabled in HAL |
| | [ 43.710000] wifi0: Atheros 956X: mem=0xb8100000, irq=47 |
| | [ 43.720000] ath_pci: SmartAntenna-DRT-0.1 (Atheros/multi-bss) |
| | [ 44.510000] ath_attach_dfs[12687] dfsdomain 1 |
| | [ 44.650000] wlan_vap_create : enter. devhandle=0x81c00380, opmode=IEEE80211_M_HOSTAP, flags=0x3 |
| | [ 44.660000] wlan_vap_create : exit. devhandle=0x81c00380, opmode=IEEE80211_M_HOSTAP, flags=0x3. |
| | [ 44.670000] VAP device ath0 created osifp: (83253380) os_if: (8249c000) |
| | [ 44.700000] Set freq vap 0 stop send + 8249c000 |
| | [ 44.700000] Set freq vap 0 stop send -8249c000 |
| | [ 44.840000] Set wait done --8249c000 |
| | [ 44.870000] WARNING: Fragmentation with HT mode NOT ALLOWED!! |
| | [ 44.890000] Set freq vap 0 stop send + 8249c000 |
| | [ 44.890000] Set freq vap 0 stop send -8249c000 |
| | [ 45.030000] Set wait done --8249c000 |
| | [ 45.130000] |
| | [ 45.130000] DES SSID SET= |
| | [ 45.140000] |
| | [ 45.140000] DES SSID SET=TP-LINK_70AC |
| | @@@@@@@@@@psk-mixed/tkip+aes |
| | [ 45.470000] ieee80211_ioctl_siwmode: imr.ifm_active=131712, new mode=3, valid=1 |
| | [ 45.480000] DEVICE IS DOWN ifname=ath0 |
| | [ 45.480000] DEVICE IS DOWN ifname=ath0 |
| | [ 45.750000] device ath0 entered promiscuous mode |
| | [ 45.940000] br-lan: port 2(ath0) entered forwarding state |
| | [ 45.940000] br-lan: port 2(ath0) entered forwarding state |
| | [ 45.960000] 8021q: adding VLAN 0 to HW filter on device ath0 |
| | [ 46.760000] fast-classifier: starting up |
| | [ 46.760000] fast-classifier: registered |
| | phyport start ....... |
| | [ 48.730000] mlme_create_infra_bss : Overriding HT40 channel with HT20 channel |
| | SETUP port (5) duplex: 1000 full autoneg: on! |
| | loading qos |
| | http://192.168.0.1/webpages/wan_error.html |
| | 192.168.0.1 |
| | http://192.168.0.1/webpages/wan_error.html |
| | 192.168.0.1 |
| | 3201 root 1772 S /usr/sbin/crond -c /etc/crontabs -l 5 |
| | |
| | |
| | </WRAP>\\ |
| |
| ===== Tags ===== | ===== Tags ===== |
| {{tag>GigabitEthernet 5Port 1NIC 1WNIC USB JTAG 802.11bgn ath9k 3Ant DetachableAntenna 32RAM 64RAM 8Flash 16Flash MIPS MIPS32 24Kc 74Kc QCA9558 QCA9563 JumboFrames vlan AR9132 ar71xx atheros-ap83}} | {{tag>ath79 ar71xx AR9132 QCA9558 QCA9563 8Flash 16Flash 32RAM 64RAM 5Port GigabitEthernet 1NIC 1WNIC USB JTAG 802.11bgn ath9k 3Ant DetachableAntenna MIPS MIPS32 24Kc 74Kc JumboFrames vlan atheros-ap83 usb 1usb usb2.0}} |