Linksys ea8500 port is ready

Post new topic   This topic is locked: you cannot edit posts or make replies.    DD-WRT Forum Index -> Atheros WiSOC based Hardware
Goto page Previous  1, 2, 3 ... 115, 116, 117 ... 123, 124, 125  Next
Author Message
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 6268
Location: Texas

PostPosted: Fri Apr 12, 2019 17:38    Post subject: Reply with quote
pakesusu wrote:
Upgrading the firmware using US firmware to any version above, does not help, still failover-ing into version 1.0.1.188217.

I DO NOT know WTH you have but it just don't look right.
AFAIK there was NEVER a FW version that you have ---

Linksys EA8500 Firmware Release Notes wrote:
---------------------------------------------------------------------------
Firmware version: 1.1.3.166556
Release date: Apr 7, 2015

- Initial release

---------------------------------------------------------------------------

You can try serial to see whats what but I would be more inclined to send it back to wherever you got it Rolling Eyes
Sponsor
Rocketboy235
DD-WRT User


Joined: 14 Oct 2016
Posts: 109
Location: United States

PostPosted: Sun Apr 14, 2019 3:14    Post subject: Reply with quote
msoengineer wrote:
mrjcd wrote:
pakesusu wrote:
Hi,

I bought E8500 on SG, with the following firmware version:

https://imgur.com/a/6B1xXZr (1.0.1.188217).

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.

To go from linksys to DD-WRT use this firmware first:
http://www.desipro.de/ddwrt/K3-AC-IPQ806X/EA8500-factory-to-ddwrt.img

Then you can use BIN files for DD-WRT to DD-WRT updates:
http://www.desipro.de/ddwrt/K3-AC-IPQ806X/

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.
Per Yngve Berg
DD-WRT Guru


Joined: 13 Aug 2013
Posts: 6856
Location: Romerike, Norway

PostPosted: Sun Apr 14, 2019 8:30    Post subject: Reply with quote
The issue is with QOS. See the tickets in tatsuya46's signature.

The latest Kong build 39345M work OK on 100 Mbit/s
Per Yngve Berg
DD-WRT Guru


Joined: 13 Aug 2013
Posts: 6856
Location: Romerike, Norway

PostPosted: Sun Apr 14, 2019 8:39    Post subject: Reply with quote
tatsuya46 wrote:
Status: many times better than bs builds at least..
Reset: no
Errors: see tickets below

https://svn.dd-wrt.com/ticket/5225 *
https://svn.dd-wrt.com/ticket/5603 *
https://svn.dd-wrt.com/ticket/5699
https://svn.dd-wrt.com/ticket/5845
https://svn.dd-wrt.com/ticket/5848
https://svn.dd-wrt.com/ticket/5933
https://svn.dd-wrt.com/ticket/5938
https://svn.dd-wrt.com/ticket/6059
https://svn.dd-wrt.com/ticket/6286
https://svn.dd-wrt.com/ticket/6466
https://svn.dd-wrt.com/ticket/6481 *
https://svn.dd-wrt.com/ticket/6495
https://svn.dd-wrt.com/ticket/6511
https://svn.dd-wrt.com/ticket/6516

included tickets are only those affecting r7800 and kong build only.

wifi latency under wan load is finally a bit better, not "normal" but better..
Rocketboy235
DD-WRT User


Joined: 14 Oct 2016
Posts: 109
Location: United States

PostPosted: Mon Apr 15, 2019 13:19    Post subject: Reply with quote
Per Yngve Berg wrote:
The issue is with QOS. See the tickets in tatsuya46's signature.

The latest Kong build 39345M work OK on 100 Mbit/s


Thank you!!
balar55
DD-WRT Novice


Joined: 02 May 2019
Posts: 2

PostPosted: Thu May 02, 2019 22:33    Post subject: Reply with quote
So I need some assistance.

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.
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 6268
Location: Texas

PostPosted: Fri May 03, 2019 0:18    Post subject: Reply with quote
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

yours -- flashimg --
Bytes transferred = 24393983 (17438ff hex)

NAND erase: device 0 offset 0xf80000, size 0x2800000
Erasing at 0x3760000 -- 100% complete.
OK
###
mine -- flashimg --
Bytes transferred = 24393983 (17438ff hex)

NAND erase: device 0 offset 0xf80000, size 0x17438ff
Erasing at 0x26c0000 -- 100% complete.
OK
################
yours -- flashimg2 --
Bytes transferred = 24393983 (17438ff hex)

NAND erase: device 0 offset 0x3780000, size 0x2800000
Erasing at 0x5f60000 -- 100% complete.
OK
###
mine -- flashing img2 --
Bytes transferred = 24393983 (17438ff hex)

NAND erase: device 0 offset 0x3780000, size 0x17438ff
Erasing at 0x4ec0000 -- 100% complete.
OK

####
I don't really know WTH it's doing and why it's saving to nand and then erasing nand

yours --
Code:

(IPQ) # reset
resetting ...

Resetting with watch dog!


U-Boot 2012.07 [Standard IPQ806X.LN,r40331] (Oct 12 2015 - 17:00:55)

CBT U-Boot ver: 1.0.12

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!

mine --
Code:

(IPQ) # reset
resetting ...

Resetting with watch dog!


U-Boot 2012.07 [Standard IPQ806X.LN,r40331] (Mar 16 2015 - 16:29:21)

CBT U-Boot ver: 1.0.9

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
balar55
DD-WRT Novice


Joined: 02 May 2019
Posts: 2

PostPosted: Fri May 03, 2019 1:53    Post subject: Reply with quote
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...
user78906
DD-WRT Novice


Joined: 06 Jun 2019
Posts: 1

PostPosted: Thu Jun 06, 2019 4:00    Post subject: Reply with quote
Any luck getting it to boot? I have exactly the same problem:

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!


Same U-Boot ver: 1.0.12

if any one has a suggestion i'm willing to try anything at this point.

Thanks
Mrmoves
DD-WRT Novice


Joined: 13 Aug 2017
Posts: 2

PostPosted: Sun Jul 14, 2019 10:13    Post subject: Kong_40270M-071119/ Reply with quote
Hi,

Anyone tried Kong_40270M-071119 yet?
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 6268
Location: Texas

PostPosted: Sun Jul 14, 2019 11:02    Post subject: Re: Kong_40270M-071119/ Reply with quote
Mrmoves wrote:
Hi,

Anyone tried Kong_40270M-071119 yet?

https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=320457
deslatha
DD-WRT User


Joined: 12 Jul 2016
Posts: 187

PostPosted: Tue Jul 23, 2019 0:08    Post subject: Re: Kong_40270M-071119/ Reply with quote
[quote="mrjcd"]
Mrmoves wrote:
Hi,

Anyone tried Kong_40270M-071119 yet?

I did so far so good.


Last edited by deslatha on Tue Jul 23, 2019 0:34; edited 1 time in total
deslatha
DD-WRT User


Joined: 12 Jul 2016
Posts: 187

PostPosted: Tue Jul 23, 2019 0:18    Post subject: Reply with quote
mrjcd wrote:
balar55,

CBT U-Boot ver: 1.0.9 <<------old bootload

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
deslatha
DD-WRT User


Joined: 12 Jul 2016
Posts: 187

PostPosted: Tue Jul 23, 2019 0:22    Post subject: Reply with quote
user78906 wrote:
Any luck getting it to boot? I have exactly the same problem:

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!


Same U-Boot ver: 1.0.12

if any one has a suggestion i'm willing to try anything at this point.

Thanks


bad flash. must stop at ipq# promt by anykey (in 2 seconds).

help
printenv
setenv autostart no
saveenv

then reflash both fw=wraith.bin (rename and edit).
deslatha
DD-WRT User


Joined: 12 Jul 2016
Posts: 187

PostPosted: Tue Jul 23, 2019 0:30    Post subject: U-Boot 2012.07 IPQ806X Reply with quote
Any one can help me post u boot 1.0.12 please.
SBl1, SBL2,SBL3.
Goto page Previous  1, 2, 3 ... 115, 116, 117 ... 123, 124, 125  Next Display posts from previous:    Page 116 of 125
Post new topic   This topic is locked: you cannot edit posts or make replies.    DD-WRT Forum Index -> Atheros WiSOC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum