User Tools

Site Tools


toh:linksys:ea3500

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
toh:linksys:ea3500 [2018/05/17 11:26]
wutje Use datatable for device info
toh:linksys:ea3500 [2018/07/25 08:49] (current)
tmomas ↷ Links adapted because of a move operation
Line 1: Line 1:
 ====== Linksys EA3500 ====== ====== Linksys EA3500 ======
 {{:​media:​linksys:​ea3500.png?​350|}} {{:​media:​linksys:​ea3500.png?​350|}}
 +
 ===== Supported Versions ===== ===== Supported Versions =====
 ---- datatable ---- ---- datatable ----
-cols    : Brand, Model, Versions, Supported Current Rel, OEM device homepage URL_url, Forum Topic URL_url, Device Techdata_pageid+cols    : Brand, Model, Versions, Supported Current Rel, OEM device homepage URL_url, ​OWrt Forum Topic URL_url, Device Techdata_pageid
 headers : Brand, Model, Version, Current Release, OEM Info, Forum Topic, Technical Data headers : Brand, Model, Version, Current Release, OEM Info, Forum Topic, Technical Data
 align   : c,​c,​c,​c,​c,​c,​c,​c align   : c,​c,​c,​c,​c,​c,​c,​c
Line 9: Line 10:
 filter ​ : Model=EA3500 filter ​ : Model=EA3500
 ---- ----
 +
 ===== Hardware Highlights ===== ===== Hardware Highlights =====
 ---- datatable ---- ---- datatable ----
Line 19: Line 21:
  
 ===== Installation ===== ===== Installation =====
 +---- datatable ----
 +cols    : Model, Versions, Supported Current Rel, Firmware OpenWrt Install URL_url, Firmware OpenWrt Upgrade URL_url, Firmware OEM Stock URL_url
 +headers : Model, Version, Current Release, Firmware OpenWrt Install, Firmware OpenWrt Upgrade, Firmware OEM Stock
 +align   : c,c,c
 +filter ​ : Model=EA3500
 +----
  
-==Generic Information on installing OpenWRT== +-[[docs:​guide-user:​installation:​generic.flashing|Install OpenWrt ​(generic explanation)]]
-  ​→ [[:​downloads|Obtain firmware]] +
-  - → [[docs:​guide-user:​installation:​generic.flashing|Install OpenWrt]] +
-  - → [[:​downloads|Latest OpenWrt release]]+
  
-====Introduction====+==== Introduction ====
  
 The EA3500 is very similar to the [[toh:​linksys:​ea4500| Linksys EA4500]] in design, but less horsepower under the hood. Like the EA4500, the EA3500 has a dual firmware layout: working and backup partitions. Unless you manually choose which partition by doing a manual uboot/tftp install, firmware flashes occur on the backup partition and the EA3500 shall reboot from the backup partition following from a firmware flash. The backup partition becomes the new working partition when the reboot was successful. The former working partition becomes the new backup partition. The EA3500 is very similar to the [[toh:​linksys:​ea4500| Linksys EA4500]] in design, but less horsepower under the hood. Like the EA4500, the EA3500 has a dual firmware layout: working and backup partitions. Unless you manually choose which partition by doing a manual uboot/tftp install, firmware flashes occur on the backup partition and the EA3500 shall reboot from the backup partition following from a firmware flash. The backup partition becomes the new working partition when the reboot was successful. The former working partition becomes the new backup partition.
  
-Below all firmware versions that have worked to some degree on the EA3500 are listed for historical purposes, however **trunk ​is definitely ​the only recommended option**. The latest buildbot images will always ​be at https://downloads.openwrt.org/​snapshots/​trunk/​kirkwood/​generic/​As always with trunk though, they can be unstable, ​have non-standard featuresand are bare minimum builds with no Luci web GUI.+As of LEDE 17.01 no special build is needed. However ​the LEDE 17.01 release cannot directly be upload to the stock firmware. The OpenWRT 15.05 needs to be uploaded first, see [[https://bugs.openwrt.org/​index.php?​do=details&​task_id=505| this LEDE forum post]]. 
 + 
 +Note that the 17.01 does not have the kmod-gpio-button-hotplug package included by defaultmaking it impossible to activate fail safe mode. It is therefore highly recommended to install kmod-gpio-button-hotplug. Later versions have this package included by default. 
 + 
 +Below all firmware versions that have worked to some degree on the EA3500 ​are listed for historical purposes
  
-==To New Users== +=== To New Users === 
-Especially with trunk images, building yourself takes a little longer, but is usually more reliable, produces higher quality firmware (crypto acceleration etc...), fully customizable,​ rewarding, educational,​ and a lot easier than it sounds. It is recommended you give it a shot before using the snapshots. Either way, if something goes wrong their should be a backup factory firmware partition (unless you previously flashed over it) to still give you a working router. Even if that gets nuked as well, getting down and dirty with uboot over a serial connection is not difficult either and the OpenWRT ​wiki has detailed instructions to walk you though. USB/TTL serial cables or breakout boards for that process are inexpensive but does require basic soldering skills and willingness to open up the case. However, don't let all this talk of possible issues with using trunk discourage you from using OpenWRT. The extra features and capabilities are well worth it.+Especially with trunk images, building yourself takes a little longer, but is usually more reliable, produces higher quality firmware (crypto acceleration etc...), fully customizable,​ rewarding, educational,​ and a lot easier than it sounds. It is recommended you give it a shot before using the snapshots. Either way, if something goes wrong their should be a backup factory firmware partition (unless you previously flashed over it) to still give you a working router. Even if that gets nuked as well, getting down and dirty with uboot over a serial connection is not difficult either and the OpenWrt ​wiki has detailed instructions to walk you though. USB/TTL serial cables or breakout boards for that process are inexpensive but does require basic soldering skills and willingness to open up the case. However, don't let all this talk of possible issues with using trunk discourage you from using OpenWrt. The extra features and capabilities are well worth it.
  
 To learn more about building images, check out: To learn more about building images, check out:
   -[[ docs:​guide-developer:​build-system:​start|OpenWrt'​s build system – About]]   -[[ docs:​guide-developer:​build-system:​start|OpenWrt'​s build system – About]]
-  -[[docs:​guide-developer:​build-system:​install-buildsystemOpenWrt ​build system – Installation]]+  -[[docs:​guide-developer:​build-system:​install-buildsystem|OpenWrt ​build system – Installation]]
   -[[docs:​guide-developer:​build-system:​start|OpenWrt build system – Usage]] ​   ​   -[[docs:​guide-developer:​build-system:​start|OpenWrt build system – Usage]] ​   ​
  
-====Versions====+==== Versions ====
  
-===Trunk- ​Recommended===+=== Trunk - Deprecated (use release 17.01 or later) ​===
   * Fully supported as of [[https://​dev.openwrt.org/​changeset/​47458|r47458]]   * Fully supported as of [[https://​dev.openwrt.org/​changeset/​47458|r47458]]
   * Build yourself or use snapshots   * Build yourself or use snapshots
Line 48: Line 57:
   * Upgrade from Openwrt image with ''​sysupgrade.tar''​ <color #​B35812>​**//​See Below!//​**</​color> ​     * Upgrade from Openwrt image with ''​sysupgrade.tar''​ <color #​B35812>​**//​See Below!//​**</​color> ​  
  
-==Build==+== Build ==
  
 This model is identified by the board codename "​Audi."​ This model is identified by the board codename "​Audi."​
Line 64: Line 73:
 The ''​factory.bin''​ image can be flashed from the Linksys interface. Upgrading between OpenWrt images is done with the ''​sysupgrade.tar''​ image. Of course TFTP is always an option :-) The ''​factory.bin''​ image can be flashed from the Linksys interface. Upgrading between OpenWrt images is done with the ''​sysupgrade.tar''​ image. Of course TFTP is always an option :-)
  
-==Downloadable Links==+== Downloadable Links ==
  
 Snapshots from https://​downloads.openwrt.org buildbots Snapshots from https://​downloads.openwrt.org buildbots
  
   *[[https://​downloads.openwrt.org/​snapshots/​trunk/​kirkwood/​generic/​openwrt-kirkwood-linksys-audi-squashfs-factory.bin|factory.bin]] - for installing from Linksys factory firmware, serial/​tftp,​ etc...   *[[https://​downloads.openwrt.org/​snapshots/​trunk/​kirkwood/​generic/​openwrt-kirkwood-linksys-audi-squashfs-factory.bin|factory.bin]] - for installing from Linksys factory firmware, serial/​tftp,​ etc...
-  *[[https://​downloads.openwrt.org/​snapshots/​trunk/​kirkwood/​generic/​openwrt-kirkwood-linksys-audi-squashfs-sysupgrade.tar|sysupgrade.tar]] - for upgrading existing ​OpenWRT ​firmware+  *[[https://​downloads.openwrt.org/​snapshots/​trunk/​kirkwood/​generic/​openwrt-kirkwood-linksys-audi-squashfs-sysupgrade.tar|sysupgrade.tar]] - for upgrading existing ​OpenWrt ​firmware
   *[[https://​downloads.openwrt.org/​snapshots/​trunk/​kirkwood/​generic/​sha256sums|SHA256 Hashsums]]   *[[https://​downloads.openwrt.org/​snapshots/​trunk/​kirkwood/​generic/​sha256sums|SHA256 Hashsums]]
  
-===Chaos Calmer- ​Depreciated===+=== Chaos Calmer - Deprecated ​===
   * Not fully supported   * Not fully supported
   * Build required   * Build required
Line 80: Line 89:
   * Issues with extroot and overlay   * Issues with extroot and overlay
  
-===Candyhouse- ​Depreciated===+=== Candyhouse - Deprecated ​===
   *.ssa is basically a package of all ubifs, ramdisk, etc... It is what the factory Linksys interface uses. Based on UBIFS   *.ssa is basically a package of all ubifs, ramdisk, etc... It is what the factory Linksys interface uses. Based on UBIFS
   * From Wolfteck Candyhouse Project, the first to release a working image for the EA3500/​EA4500   * From Wolfteck Candyhouse Project, the first to release a working image for the EA3500/​EA4500
Line 90: Line 99:
  
  
-====TFTP Flash====+==== TFTP Flash ====
  
 If you don't have the web ui (bricked,​old CC version without sysupgrade, etc...); or you simply prefer having more control over the flashing process, then flashing using TFTP is your answer. It is pretty straight forward and, especially now that the EA3500 is supported in trunk, easy without requiring a bunch of custom uboot environmental variables. If you don't have the web ui (bricked,​old CC version without sysupgrade, etc...); or you simply prefer having more control over the flashing process, then flashing using TFTP is your answer. It is pretty straight forward and, especially now that the EA3500 is supported in trunk, easy without requiring a bunch of custom uboot environmental variables.
Line 96: Line 105:
 For more info about TFTP flashing see ->  [[docs:​guide-user:​installation:​generic.flashing.tftp]] For more info about TFTP flashing see ->  [[docs:​guide-user:​installation:​generic.flashing.tftp]]
  
-[[ toh:​linksys:​ea3500#​serial|Below ]] is an image showing the pinouts to solder your cable for the USB/TTL serial connection. The serial port is marked **J7**, and Rx,Tx,and Ground is all that's needed (no +3.3v). If you choose, you can install a permanent serial port jack (like the 3.5mm minijack in the pictures below) to the router for quick access. Simply pushing the wires/​header pins in temporarily in the pinouts will work as well; provided you get good continuity. ​  +[[#​serial|Below]] is an image showing the pinouts to solder your cable for the USB/TTL serial connection. The serial port is marked **J7**, and Rx,Tx,and Ground is all that's needed (no +3.3v). If you choose, you can install a permanent serial port jack (like the 3.5mm minijack in the pictures below) to the router for quick access. Simply pushing the wires/​header pins in temporarily in the pinouts will work as well; provided you get good continuity. ​  
  
 To connect to the router with a serial terminal such as screen or GTKterm, use the settings: To connect to the router with a serial terminal such as screen or GTKterm, use the settings:
Line 126: Line 135:
 ''​ ''​
  
-Again, this is not common and will likely not happen unless you have previously performed several flashes. ​ The router'​s auto_recovery feature should return you to factory firmware if this happens, so don't let the potential problem keep you from trying out OpenWRT.  Once the initial flash is complete, a normal sysupgrade (with the -sysupgrade tarball, not the -factory bin!) will always work without problems.+Again, this is not common and will likely not happen unless you have previously performed several flashes. ​ The router'​s auto_recovery feature should return you to factory firmware if this happens, so don't let the potential problem keep you from trying out OpenWrt.  Once the initial flash is complete, a normal sysupgrade (with the -sysupgrade tarball, not the -factory bin!) will always work without problems. 
 ==== Chaos Calmer using Serial ==== ==== Chaos Calmer using Serial ====
 Current Chaos Calmer appears to be missing the necessary ramdisk image, so you'll need to build that in order to install using this method. Current Chaos Calmer appears to be missing the necessary ramdisk image, so you'll need to build that in order to install using this method.
Line 307: Line 317:
 ===== Hardware ===== ===== Hardware =====
 ==== Info ==== ==== Info ====
-| **[[wp>​Instruction set]]:**               | [[wp>ARM architecture|ARM]] ​ | +[[wp>​Instruction set]]               | [[wp>ARM architecture|ARM]] ​ | 
-| **Vendor:**                               | [[wp>​Marvell Technology Group|Marvell]] ​ | +Vendor ​                              | [[wp>​Marvell Technology Group|Marvell]] ​ | 
-| **[[docs:​techref:​bootloader]]:**           | [[docs:​techref:​bootloader:​uboot|U-Boot]] | +[[docs:​techref:​bootloader]] ​         | [[docs:​techref:​bootloader:​uboot|U-Boot]] | 
-| **[[docs:​techref:​hardware:​soc|System-On-Chip]]:**  | Feroceon 88F6282 | +[[docs:​techref:​hardware:​soc|System-On-Chip]] ​ | Feroceon 88F6282 | 
-| **[[docs:​techref:​hardware:​cpu|CPU]] @Frq**         | Feroceon A88FR131 @800MHz | +[[docs:​techref:​hardware:​cpu|CPU]] @Frq        | Feroceon A88FR131 @800MHz | 
-| **Flash size:**                 | 64 MiB | +Flash size                 | 64 MiB | 
-| **Flash Chip:**                 | Hynix NAND 64MiB 3,3V 8-bit | +Flash Chip                 | Hynix NAND 64MiB 3,3V 8-bit | 
-| **RAM size:**                   | 64 MiB   | +RAM size                   | 64 MiB   | 
-| **RAM Chip:**                   |   | +RAM Chip                   ​| ​  | 
-| **Wireless No1:**               | Marvell 88W8366 v48 for 2Ghz | +Wireless No1               | Marvell 88W8366 v48 for 2Ghz | 
-| **Wireless No2:**               | Marvell 88W8366 v48 for 5Ghz | +Wireless No2               | Marvell 88W8366 v48 for 5Ghz | 
-| **[[docs:​techref:​hardware:​switch]]:**    | Marvell 643xx (Gigabit, VLAN)  | +[[docs:​techref:​hardware:​switch]] ​   | Marvell 643xx (Gigabit, VLAN)  | 
-| **USB:**                        | Yes 1 x 2.0 | +USB                        | Yes 1 x 2.0 | 
-| **[[docs:​techref:​hardware:​port.serial|Serial]]:**  | [[#​Serial|Yes]] | +[[docs:​techref:​hardware:​port.serial|Serial]] ​ | [[#​Serial|Yes]] | 
-| **[[docs:​techref:​hardware:​port.jtag|JTAG]]:**      | [[#​JTAG|Yes]] ​  |+[[docs:​techref:​hardware:​port.jtag|JTAG]] ​     | [[#​JTAG|Yes]] ​  |
  
 ==== Photos ==== ==== Photos ====
Line 368: Line 378:
 Below is an illustration of a standard 3.5mm minijack being used as an external serial port connection. It fits nicely in a space by the power supply input on the back. I just picked up the female connection and a male connector at Radio Shack, however much better deals can be found online. Below is an illustration of a standard 3.5mm minijack being used as an external serial port connection. It fits nicely in a space by the power supply input on the back. I just picked up the female connection and a male connector at Radio Shack, however much better deals can be found online.
  
-{{ media:​linksys:​linksysea3500-serial-connector.png }}+{{ media:​linksys:​ea3500_serial-connector.png }}
  
 ==External Antennas== ​ ==External Antennas== ​
Line 374: Line 384:
 Each radio has 3 internal antennas with UFL jacks so adding some pigtails with RP-SMA jacks on the outside is straightforward. Here is the best location I found to mount them. Everything fist nicely. Each radio has 3 internal antennas with UFL jacks so adding some pigtails with RP-SMA jacks on the outside is straightforward. Here is the best location I found to mount them. Everything fist nicely.
    
-{{media:​linksys:​linksysea3500-board-mods.png }} +{{media:​linksys:​ea3500_board-mods.png }} 
-{{media:​linksys:​linksysea3500-external-ant-mod.png }}+{{media:​linksys:​ea3500_external-ant-mod.png }} 
 ==== JTAG ==== ==== JTAG ====
 -> [[docs:​techref:​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.
Line 389: Line 400:
     3. Repeat the top steps three times, and when the power light no longer turns off during boot up, the device should be reset to default firmware/ settings.     3. Repeat the top steps three times, and when the power light no longer turns off during boot up, the device should be reset to default firmware/ settings.
  
-Source: https://​forum.openwrt.org/​viewtopic.php?​id=66803+Source: ​[[https://​forum.openwrt.org/​viewtopic.php?​id=66803]]
  
-===== Bootloader Mods ===== 
-  - you could read about [[docs:​techref:​bootloader]] in general 
  
 ===== Bootlogs ===== ===== Bootlogs =====
Line 1069: Line 1078:
 ===== Tags ===== ===== Tags =====
 [[meta:​tags|How to add tags]] [[meta:​tags|How to add tags]]
-{{tag>​GigabitEthernet FastEthernet 4NIC 1WNIC 5Port USB kirkwood 64RAM 64Flash ARM}}+{{tag>​GigabitEthernet FastEthernet 4NIC 2WNIC 5Port USB kirkwood 64RAM 64Flash ARM}}
toh/linksys/ea3500.1526556378.txt.gz · Last modified: 2018/05/17 11:26 by wutje