Differences

This shows you the differences between two versions of the page.

toh:linksys:e3000 [2013/04/17 07:34]
codyps
toh:linksys:e3000 [2014/10/20 20:58] (current)
blubbfish
Line 1: Line 1:
====== Linksys E3000 ====== ====== Linksys E3000 ======
The Linksys E3000 is based on the same hardware as the [[.:WRT610N|Linksys WRT610N v2.0]] with changes to the CFE and a larger NVRAM block.  The E3000 is based on the Broadcom 4718 cpu running at 480MHz.  It has 8 MB flash (MX29LV640EBTI) and 64 MB SDRAM (H5PS5162FFR). The Linksys E3000 is based on the same hardware as the [[.:WRT610N|Linksys WRT610N v2.0]] with changes to the CFE and a larger NVRAM block.  The E3000 is based on the Broadcom 4718 cpu running at 480MHz.  It has 8 MB flash (MX29LV640EBTI) and 64 MB SDRAM (H5PS5162FFR).
-The WNICs are provided by the BCM4718 SoC (2.4GHz B, G and N) and a second constituent chip, the BCM4322 (5GHz A and N). The switch is a BCM53115 chip+The switch is a BCM53115 chip.
-The E3000 runs 802.11 A, B, G, and Draft N wireless protocols. It provides 4 gigabit LAN ports, 1 WAN port and a USB 2.0 'storage link' port.+
===== Supported Versions ===== ===== Supported Versions =====
^ Version/Model ^ S/N ^ OpenWrt Version Supported ^ Model Specific Notes ^ ^ Version/Model ^ S/N ^ OpenWrt Version Supported ^ Model Specific Notes ^
-| E3000 v1.0 | CVQ01 | *Not Fully Tested* r28295 w/ patches, trunk (untested, [[https://dev.openwrt.org/changeset/36099|r36099]]) | Integrated Wireless and Ethernet are supported in [[.:e3000#kernel.support|3.0 Kernel]] using Broadcom proprietary drivers|+| E3000 v1.0 | CVQ01 | 14.07 with limited wireless performance | Proprietary broadcom-wl driver can be tested for better performance |
===== Hardware Highlights ===== ===== Hardware Highlights =====
-^ CPU ^ Ram ^ Flash ^ Network ^ USB ^ Serial ^ JTag ^ +^ CPU ^ Ram ^ Flash ^ Network ^ Wireless ^ USB ^ Serial ^ JTag ^ 
-| BCM4718@480MHz | 64MiB | 8MiB | 4 x 1 | Yes | Yes | No/Yes* |+| BCM4718@480MHz | 64MiB | 8MiB | 1+4 x 1000 M | 2.4 GHz (SoC) + 5 GHz (BCM4322) | Yes (2.0) | Yes | No/Yes* |
===== Installation ===== ===== Installation =====
 +
 +  - Download https://downloads.openwrt.org/barrier_breaker/14.07/brcm47xx/generic/openwrt-e3000_v1-squashfs.bin
 +  - Install using the stock web interface
 +
==== Flash Layout ==== ==== Flash Layout ====
 +<code>Tot mem: 65536 KBytes
 +
 +CFE mem:    0x80700000 - 0x8079DAC0 (645824)
 +Data:      0x80732A20 - 0x80737080 (18016)
 +BSS:        0x80737080 - 0x80737AC0 (2624)
 +Heap:      0x80737AC0 - 0x8079BAC0 (409600)
 +Stack:      0x8079BAC0 - 0x8079DAC0 (8192)
 +Text:      0x80700000 - 0x80732A1C (207388)</code>
==== OEM installation using the TFTP method ==== ==== OEM installation using the TFTP method ====
Line 19: Line 30:
-==== 3.0 Kernel Support ==== 
-  - There is a set of patches to allow support for the E3000 switch and WIFI under 3.0.4 kernel builds written by George Kashperko et.al. 
-  - => See the [[http://www.znau.edu.ua/temp/asus-rt-n16/openwrt-bcm4716-README.txt|README]]. 
-  - Patchset has not yet been incorporated into OpenWrt main development tree 
-  - a RAMDISK Image of OpenWrt trunk r28295 + the patchset was successfully booted, see => [[.:e3000:3.0.4_bootlog]]. 
- 
-**Caveats** 
-  * Only the WNIC contained in the SoC works at this time with the proprietary Broadcom drivers 
-  * USB support is not 100%.  Overcurrent on port error messages have intermittently been seen. 
-  * **Use At Your Own Risk** 
Line 65: Line 66:
The CFE installed on the E3000 locates itself at 0x80700000.  This can cause conflicts with the standard VMLINUX_LOAD_ADDRESS for BCM47XX devices, 0x80001000 when the image size is > 7335936 bytes.  It is not known at this time how much this will hamper development efforts.  It is possible to modify the VMLINUX_LOAD_ADDRESS in arch/mips/bcm47xx/Platform to allow larger ramdisk enabled images to be tested.  A setting of 0x81001000 has been successful with tftp loading of large ramdisk based firmware image. The CFE installed on the E3000 locates itself at 0x80700000.  This can cause conflicts with the standard VMLINUX_LOAD_ADDRESS for BCM47XX devices, 0x80001000 when the image size is > 7335936 bytes.  It is not known at this time how much this will hamper development efforts.  It is possible to modify the VMLINUX_LOAD_ADDRESS in arch/mips/bcm47xx/Platform to allow larger ramdisk enabled images to be tested.  A setting of 0x81001000 has been successful with tftp loading of large ramdisk based firmware image.
-{{tag>802.11abgn 802.11abgn_simultan 2Radio bcm4718}}+{{tag>802.11abgn 802.11abgn_simultan 2WNIC bcm4718}} 
 + 
 +===== WRT610N v2 ===== 
 +Both wireless adapters work on trunk, however you will need to use broadcom-wl to achieve full speed, and make use of both adapters, as on the open source driver only one adapter works at 24mbit.

Back to top

toh/linksys/e3000.1366176853.txt.bz2 · Last modified: 2013/04/17 07:34 by codyps