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
Next revisionBoth sides next revision
toh:linksys:ea3500 [2019/06/26 21:02] – [Introduction] wutjetoh:linksys:ea3500 [2020/12/19 18:56] – [Tags] danitool
Line 32: Line 32:
 ==== 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 it has less horsepower under the hood. 
  
-As of LEDE 17.01 no special build is needed. However the LEDE 17.01 release cannot directly be uploaded to the stock firmware. This [[https://archive.openwrt.org/snapshots/trunk/kirkwood/generic/openwrt-kirkwood-linksys-audi-squashfs-factory.bin | OpenWRT version 15.05]] needs to be uploaded first, see [[https://bugs.openwrt.org/index.php?do=details&task_id=505| this LEDE forum post]].+==== Dual firmware ====  
 + 
 +Like several other Linksys devices, 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. There is a useful Luci app that show which partition is currently booted: luci-app-advanced-reboot, see the [[https://github.com/openwrt/luci/blob/master/applications/luci-app-advanced-reboot/README.md | readme]] for more information. 
 + 
 +<del>As of LEDE 17.01 no special build is needed. However the LEDE 17.01 and later releases cannot directly be uploaded to the stock firmware. This [[https://archive.openwrt.org/snapshots/trunk/kirkwood/generic/openwrt-kirkwood-linksys-audi-squashfs-factory.bin | OpenWRT version 15.05]] needs to be uploaded first, see [[https://bugs.openwrt.org/index.php?do=details&task_id=505| this LEDE forum post]].</del> 
 + 
 +Current snapshot (Oct 23 2019) factory image can be flashed from stock firmware's web interface.
  
 Note that the 17.01 does not have the kmod-gpio-button-hotplug package included by default, making 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. Note that the 17.01 does not have the kmod-gpio-button-hotplug package included by default, making 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.
Line 64: Line 70:
      
 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 == 
- 
-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-sysupgrade.tar|sysupgrade.tar]] - for upgrading existing OpenWrt firmware 
-  *[[https://downloads.openwrt.org/snapshots/trunk/kirkwood/generic/sha256sums|SHA256 Hashsums]] 
  
 === Chaos Calmer - Deprecated === === Chaos Calmer - Deprecated ===
Line 93: Line 91:
 ==== 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, easy without requiring a bunch of custom uboot environmental variables.
  
 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]]
Line 104: Line 102:
   -Stop Bits: 1   -Stop Bits: 1
  
-Once connected, plug in the router and break uboot by pressing any key immediately at boot. Have a tftp server running on a machine with the //openwrt_image_factory.bin// in the correct directory for sharing via TFTP. Connect it up to a **lan** port on the router, set all the correct variables in uboot (usually just //setenv ipaddr// and //setenv serverip//) for retrieving the firmware. Flash with the commands below, they are assuming you are using a trunk or other fully supported firmware version: +Once connected, plug in the router and break uboot by pressing any key immediately at boot. Have a tftp server running on a machine with the //openwrt_image_factory.bin// in the correct directory for sharing via TFTP. Connect it up to a **lan** port on the router, set all the correct variables in uboot (usually just //setenv ipaddr// and //setenv serverip//) for retrieving the firmware. Flash with the commands below, they are assuming you are using fully supported firmware version: 
  
 To flash the 1st boot partition, make sure //boot_part '1'// and //bootcmd 'run nandboot'// is set and use: To flash the 1st boot partition, make sure //boot_part '1'// and //bootcmd 'run nandboot'// is set and use:
Line 1070: Line 1068:
 ===== Tags ===== ===== Tags =====
 [[meta:tags|How to add tags]] [[meta:tags|How to add tags]]
-{{tag>GigabitEthernet FastEthernet 4NIC 2WNIC 5Port USB kirkwood 64RAM 64Flash ARM}}+{{tag>kirkwood 64Flash 64RAM GigabitEthernet FastEthernet 4NIC 2WNIC 5Port USB ARM dual_firmware}}
  • Last modified: 2024/02/12 08:58
  • by 127.0.0.1