Posted: Wed Apr 12, 2017 7:23 Post subject: Also hoping for DD-WRT for this router
I also have the EA9500. Please let me know if I can be of any assistance. I am studying networking and cybersecurity and wish I had bought one capable of SNMP, as I need to learn to use networking monitoring tools.
Decompressing...done
Found a Toshiba NAND flash:
Total size: 128MB
Block size: 128KB
Page Size: 2048B
OOB Size: 64B
Sector size: 512B
Spare size: 16B
ECC level: 8 (8-bit)
Device ID: 0x98 0xf1 0x80 0x15 0xf2 0x16
find_devinfo: devinfo block found at 0x00180000!
Press Ctrl+C to stop in CFE
CFE version 7.14.131.35 (r612453) based on BBP 1.0.37 for BCM947XX (32bit,SP,)
Build Date: Fri Jan 22 18:07:59 CST 2016 (proc@ubuntu12d04LTS), for the EA9500 board
Copyright (C) 2000-2008 Broadcom Corporation.
Copyright (C) 2016 Arcadyan Corporation.
Flashing all LEDs ...
Init Arena
Init Devs.
Boot partition size = 262144(0x40000)
DDR Clock: 800 MHz
Info: DDR frequency set from clkfreq=1400,*800*
Hardware Info:
CPU Broadcom BCM4709C0KFEBG dual-core @ 1.4 GHz
Switch in BCM4709C0KFEBG & BCM53125
RAM 256 MB
Flash 128 MB
2.4 GHz Radio BCM4366 4×4 2.4/5G single chip 802.11ac SoC
Skyworks SE2623L 2.4 GHz power amp (x4)
5 GHz radio BCM4366 4×4 2.4/5G single chip 802.11ac SoC
RFMD RFPA5542 5 GHz PA module (x4)
NOTE: There are two 5 GHz radios.
PCIe PLX Technology PEX8603 3-lane, 3-port PCIe switch
It appears that like Netgear R8000, Linksys EA9500 CPU is connected to CPU port 5. Additionally we have to add VLAN1 changes to accommodate this.
For b53_common.c, at around line 1385 add following:
1386
1387
if (of_machine_is_compatible("linksys,ea9500"))
sw_dev->cpu_port = 5;
Adding changes to Network Config (target/linux/bcm53xx/base_files/02_network):
wan_macaddr="$(nvram get wan_hwaddr)"
case "$board" in
asus,rt-ac87u)
ifname=eth1
etXmacaddr=$(nvram get et1macaddr)
;;
dlink,dir-885l | \
netgear,r7900 | \
netgear,r8000 | \
netgear,r8500 | \
linksys,ea9500) # add ea9500
ifname=eth2
etXmacaddr=$(nvram get et2macaddr)
;;
*)
ifname=eth0
etXmacaddr=$(nvram get et0macaddr)
;;
esac
# If WAN MAC isn't explicitly set, calculate it using base MAC as reference.
[ -z "$wan_macaddr" -a -n "$etXmacaddr" ] && wan_macaddr=$(macaddr_add "$etXmacaddr" 1)
# Workaround for devices using eth2 connected to (CPU) switch port 8
case "$board" in
dlink,dir-885l | \
netgear,r7900 | \
netgear,r8000 | \
netgear,r8500 | \
linksys,ea9500) # add ea9500
ifname=eth0
ucidef_add_switch "switch0" \
"0:lan" "1:lan" "2:lan" "3:lan" "4:wan" "5t@$ifname"
# These devices should use eth2 so their eth0 interface often has no MAC
# assigned. Manually assign eth2's MAC to the LAN.
et2macaddr="$(nvram get et2macaddr)"
[ -n "$et2macaddr" ] && ucidef_set_interface_macaddr "lan" "$et2macaddr"
[ -n "$wan_macaddr" ] && ucidef_set_interface_macaddr "wan" "$wan_macaddr"
Yes Ah-Pin-Kor, I've been working with brainslayer diligently to develop this, it should be coming very very soon
Also shout out to npcomplete for helping us out as well!!!!!
I've been frustrated with he ea9500, which I bought partially to replace my tired old download server... Or at least, offload some tasks to it, and was looking to install LEDE on it, eventually. I would feel much more "safe" installing DD-WRT once it becomes available though So seeing the last couple of posts, @mattlesh1 - Awesome work! If you need an alpha or beta tester who also knows his way around code and electronics, hit me up! Happy to help.
So very unfortunately, there will be no possible way of getting ddwrt on to the Linksys EA9500. Although we have developed dd-wrt for it, it will not be able to work as the firmware for both the models (v1 having a dual core broadcom northstar cpu. And v2 having arm 64 quadcore cpu) are encrypted and signed via pgp. A sad day indeed