The firmware cannot be upgraded from FW_EA8500_1.1.3.166845_prod.img to FW_EA8500_1.1.9.x_prod.img, after updating it, it will failover to default version over and over again.
Means if I want to be upgraded to ddwrt, I have to use USB serial? I previously planned to upgrade using the E8500WW firmware.
Just guessing .... the EA8500 router you have is a made for North America (US) EA8500
That means you cannot go from a firmware that old to directly Linksys latest.
Look at 'For US' in this link ---> https://www.linksys.com/us/support-article?articleNum=156300 AND this is no place to ask about upgrading Linksys firware to another Linksys firmware.
You should call them or ask at https://www.linksys.com/us/support/
If you're looking to switch to DD-WRT, don't install the latest Linksys firmware. The last Linksys firware that will allow you to run dd-wrt without having to use a serial to USB "hack" is 1.1.4.169978.
Otherwise, MRJCD is right on...not a place to ask about linksys firmware...
You should run Kong's firmware if you're going to run DD-WRT on the EA8500.
The test folder has the latest builds made by Kong, but beware they are running on the newer Linux K4.19 kernel which slows down the router on ISP connections over 75mbps.
If your connection is faster. stick to the build in the non test folder.
Can someone tell me why the newer Linux K4.19 test build has a major impact on routers with ISP connections over 75 mbps speeds? Just curious if there is a ticket open that I can look at exactly. Thanks.
Doesn't impact me much though since my ISP speed is 70 mbps haha.
After getting tired of wifi dropouts on the latest EA8500 Linksys firmware I thought I'd give dd-wrt a shot. Opened up the case to find no pins which was a bummer but was able to attach pins for the TTL leads. Then I followed the @mrjcd guide to the letter and everything seemed to be going well, got serial communication, uploaded the kong image to both partitions, reset and then...
Code:
Loading from nand0, offset 0x3780000
Image Name: Linux-3.18
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2097023 Bytes = 2 MiB
Load Address: 42208000
Entry Point: 42208000
Automatic boot of image at addr 0x44000000 ...
Image Name: Linux-3.18
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2097023 Bytes = 2 MiB
Load Address: 42208000
Entry Point: 42208000
Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!
And then it just sits at the IPQ prompt. I've tried re-downloading the file and flashing again but to no avail. Tried flashing the latest kong factory file, but all the did was replace image name on boot from Linux-3.18 to DD-WRT V3.0 but still bad CRC check. Even tried old linksys firmware images but same issue. Tried the whole process over again on another computer but not difference.
I am really at a loss. Could serial pins not be attached right or damaged something when I put on the leads? Would really like to get this functioning again.
I attached the session log if that proves helpful.
balar55,
aside from you have uboot version 1.0.12 and mine are version 1.0.9
I'm not sure what you've gotton into.
What Linksys FW were you having trouble with? You say the latest...
... which their current latest is Ver. 1.1.9.192968 (03/20/2019)
I find it hard to believe it caused wifi dropouts under any type normal/decent conditions.
DID YOU RESET IT BEFORE TRYING TO GO TO DD-WRT ???
What other firmware have you tried to install?
How long have you had this router?
Where did you get it from?
sompin just don't really looky right...but who knows what's what and/or who may have done whatever
smem ram ptable found: ver: 0 len: 5
DRAM: 491 MiB
NAND: SF: Unsupported manufacturer 00
ipq_spi: SPI Flash not found (bus/cs/speed/mode) = (0/0/48000000/0)
128 MiB
MMC:
PCI0 Link Intialized
PCI1 Link Intialized
In: serial
Out: serial
Err: serial
cdp: get part failed for 0:HLOS
Net: MAC1 addr:0:3:7f:ba:db:1
athrs17_reg_init: complete
athrs17_vlan_config ...done
S17c init done
MAC2 addr:0:3:7f:ba:db:2
eth0
Warning: eth0 MAC addresses don't match:
Address in SROM is 00:03:7f:ba:db:01
Address in environment is 00:06:3b:01:41:00
, eth1
Updating boot_count ... done
Saving Environment to NAND...
Erasing Nand...
Erasing at 0xec0000 -- 100% complete.
Writing to Nand... done
Hit any key to stop autoboot: 0
MMC Device 0 not found
MMC Device 0 not found
Loading from nand0, offset 0x3780000
Image Name: Linux-3.18
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2097023 Bytes = 2 MiB
Load Address: 42208000
Entry Point: 42208000
Automatic boot of image at addr 0x44000000 ...
Image Name: Linux-3.18
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2097023 Bytes = 2 MiB
Load Address: 42208000
Entry Point: 42208000
Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!
smem ram ptable found: ver: 0 len: 5
DRAM: 491 MiB
NAND: SF: Unsupported manufacturer 00
ipq_spi: SPI Flash not found (bus/cs/speed/mode) = (0/0/48000000/0)
128 MiB
MMC:
PCI0 Link Intialized
PCI1 Link Intialized
In: serial
Out: serial
Err: serial
cdp: get part failed for 0:HLOS
Net: MAC1 addr:0:3:7f:ba:db:1
athrs17_reg_init: complete
athrs17_vlan_config ...done
S17c init done
MAC2 addr:0:3:7f:ba:db:2
eth0
Warning: eth0 MAC addresses don't match:
Address in SROM is 00:03:7f:ba:db:01
Address in environment is 00:06:3b:01:41:00
, eth1
Updating boot_count ... done
Hit any key to stop autoboot: 0
MMC Device 0 not found
MMC Device 0 not found
Loading from nand0, offset 0x3780000
Image Name: Linux-3.18
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2097023 Bytes = 2 MiB
Load Address: 42208000
Entry Point: 42208000
Automatic boot of image at addr 0x44000000 ...
Image Name: Linux-3.18
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2097023 Bytes = 2 MiB
Load Address: 42208000
Entry Point: 42208000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
###
EDIT:
I dunno.... your log shows it was all transferred correct byte for byte but then he seems to erase from an ungodly address. I think something is screwed. If you try again just try to flash one time only and if completes and get you get (IPQ) # I would then type 'reset' which will reboot it...maybe it can find correct image ...I just dunno
Thank you for looking into this.
Wifi dropout might have been an incorrect phrase, devices would disconnect/reconnect in a loop until a restart. Have had the router for about three or four years new. Started with linksys 1.1.9.192968 firmware from a reset state.
First I used the factory image from the PuTTy-TFTP folder. Then I tried the EA8500-factory-to-ddwrt.img from http://desipro.de/ddwrt/K3-AC-IPQ806X/
At that point I was curious so I tried linksys firmware 1.1.4.168206 and 1.1.4.169978.
Each time it acted like it was taking the firmware just fine as on restart the loading image name would change but then checksum fail. I still have serial access and can send commands. Looking around a bit it might be related to memory adresses/sizing issues. It's really weird...
smem ram ptable found: ver: 0 len: 5
DRAM: 491 MiB
NAND: SF: Unsupported manufacturer 00
ipq_spi: SPI Flash not found (bus/cs/speed/mode) = (0/0/48000000/0)
1
eth0
Warning: eth0 MAC addresses don't match:
Address in SROM is 00:03:7f:ba:db:01
Address in environment is 00:06:3b:01:41:00 <<----need change to mac of SROM
, eth1
Updating boot_count ... done
Hit any key to stop autoboot: 0
MMC Device 0 not found
MMC Device 0 not found
Loading from nand0, offset 0x3780000<<<------need flash same fw to both partitions
Automatic boot of image at addr 0x44000000 ...
Image Name: Linux-3.18
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2097023 Bytes = 2 MiB
Load Address: 42208000
Entry Point: 42208000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK[/code]
###
EDIT:
stop at ipq# by any key...
help
printenv
setenv eth0 00037fbadb01
saveenv