It is pretty simple, setup a tftp server e.g. on 192.168.1.2, in the root dir of the tftp goes the firmware, run flashimg flashes to first part run flashimg2 to second part. Attach serial at boot just hit a key, then it jumps to uboot prompt where you set it up.
Hi @tatsuya46,
I tried flashing different builds to a brand new EA8500 I just purchased. Nothing was working as the stock firmware it came with is 1.1.4.173728.
So I started on this path to use tftp, pryed a brand new EA8500 open, but the JM1 pins are not there. I assume I need to solder to the board?
See picture here https://www.jruehlig.com/owncloud/s/tFbXOUpNOm5W44B
####
Or will that not help because the bootloaded is somehow locked?
Thanks
I didn't see your pic and your link aint working for me ---
Does yours not look like this US version 'EA8500 back tag' and the 'EA8500 board'
Thanks for the help and the excellent write-up.
I was able to get a serial connection, the ground trace had no solder in it so I soldererd to a screw mounting. serial connection is working and I'm doing the tftp right now.
is it normal for it take a while? I see see the following...
Load address:0x42000000
Loading:## Watning: gatewayip needed but not set
T T T T T T T ... (these seem to keep generating)
I'm wondering if I my tftp server isn't working properly.
is it normal for it take a while? I see see the following...
Load address:0x42000000
Loading:## Watning: gatewayip needed but not set
T T T T T T T ... (these seem to keep generating)
I'm wondering if I my tftp server isn't working properly.
Setup properly it takes about 10 seconds to write the firmware.
Go back and read every word I wrote and do exactly... don't add anything and don't skip anything.
The pics I added to that page to show exactly what you should be seeing. If not then you are not setup right.
There is also a serial log at bottom of page --
is it normal for it take a while? I see see the following...
Load address:0x42000000
Loading:## Watning: gatewayip needed but not set
T T T T T T T ... (these seem to keep generating)
I'm wondering if I my tftp server isn't working properly.
Setup properly it takes about 10 seconds to write the firmware.
Go back and read every word I wrote and do exactly... don't add anything and don't skip anything.
The pics I added to that page to show exactly what you should be seeing. If not then you are not setup right.
There is also a serial log at bottom of page --
Awesome! I think I added some extra lines in there.
redid it and it worked perfectly, now running with ddwrt!
is it normal for it take a while? I see see the following...
Load address:0x42000000
Loading:## Watning: gatewayip needed but not set
T T T T T T T ... (these seem to keep generating)
I'm wondering if I my tftp server isn't working properly.
Setup properly it takes about 10 seconds to write the firmware.
Go back and read every word I wrote and do exactly... don't add anything and don't skip anything.
The pics I added to that page to show exactly what you should be seeing. If not then you are not setup right.
There is also a serial log at bottom of page --
Awesome! I think I added some extra lines in there.
redid it and it worked perfectly, now running with ddwrt!
Good job ....you really should download Kong latest and flash it using dd-wrt GUI
is it normal for it take a while? I see see the following...
Load address:0x42000000
Loading:## Watning: gatewayip needed but not set
T T T T T T T ... (these seem to keep generating)
I'm wondering if I my tftp server isn't working properly.
Setup properly it takes about 10 seconds to write the firmware.
Go back and read every word I wrote and do exactly... don't add anything and don't skip anything.
The pics I added to that page to show exactly what you should be seeing. If not then you are not setup right.
There is also a serial log at bottom of page --
Awesome! I think I added some extra lines in there.
redid it and it worked perfectly, now running with ddwrt!
Good job ....you really should download Kong latest and flash it using dd-wrt GUI
I installed the latest from the dd-wrt ftp. Any difference with Kong's builds?
Had a reboot in middle of day 5 on r30880M kongat... Not sure why but observed no serious problems and never gave
it a chance to run over few days after that without me messing with something.
Gonna try leave this as is and see how it does -
DD-WRT v3.0-r30910M kongat (12/02/16)
Linux 3.18.45 #249 SMP PREEMPT Fri Dec 2 20:40:15 CET 2016 armv7l
Thought we might be on K4.x by now...??
oh well this is looking great so far.
Not doing anything really special but what I'm doing is all good
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Sun Dec 04, 2016 4:48 Post subject:
mrjcd wrote:
Had a reboot in middle of day 5 on r30880M kongat... Not sure why but observed no serious problems and never gave
it a chance to run over few days after that without me messing with something.
Gonna try leave this as is and see how it does -
DD-WRT v3.0-r30910M kongat (12/02/16)
Linux 3.18.45 #249 SMP PREEMPT Fri Dec 2 20:40:15 CET 2016 armv7l
Thought we might be on K4.x by now...??
oh well this is looking great so far.
Not doing anything really special but what I'm doing is all good
when i asked, kong said he had issues moving ipq806x to k4.4, apparently brainslayer might have some other ipq based units & thats where the issues came from..so he left it alone. idk when we will get k4.x, im guessing whenever brainslayer decides to.. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Switched back over to the partition that had 30840 on it. The latest was giving me issues.
No errors that I could see or loss of speed when running tests but just over all slower lading of web pages, posts taking a long time to lad on Facebook, Instagram etc.
I tried the latest build twice. Even did an erase nvram the second time.
Build 30840 just seems to work better for me. _________________ I am far from a guru, I'm barely a novice.
Last edited by Malachi on Sun Dec 04, 2016 23:40; edited 1 time in total
DD-WRT v3.0-r30910M kongat (12/02/16)
Linux 3.18.45 #249 SMP PREEMPT Fri Dec 2 20:40:15 CET 2016 armv7
root@---:~# dmesg | tail
[ 24.897656] br0: port 2(ath0) entered forwarding state
[ 24.897735] br0: port 2(ath0) entered forwarding state
[ 26.482558] device ath1 entered promiscuous mode
[ 26.898923] br0: port 2(ath0) entered forwarding state
[ 28.341729] br0: port 3(ath1) entered forwarding state
[ 28.341830] br0: port 3(ath1) entered forwarding state
[ 28.791981] device vlan2 entered promiscuous mode
[ 29.737785] device vlan2 left promiscuous mode
[ 30.342941] br0: port 3(ath1) entered forwarding state
[ 331.273016] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
root@---:~# uptime
18:11:35 up 5 days, 34 min, load average: 0.02, 0.05, 0.00
30910M has worked very well for me
------
Install over 30910M -
DD-WRT v3.0-r30925M kongat (12/07/16)
Linux 3.18.45 #256 SMP PREEMPT Wed Dec 7 23:47:56 CET 2016 armv7l
All was working fine but did a reboot after looking at log..... unbound looked a bit out of sorts.
Probably nothing but he was confused during the firmware write.
You can see from log after WANup that unbound numbers didn't make sense to me.
He was working ok but I never seen that before on previous installs.
Install 30925M over 30910M --
Jan 1 00:00:27 --- user.info : wland : WLAN daemon successfully started
Jan 1 00:00:27 --- user.info : WAN is up. IP: 96.46.xxx.xxx
Dec 31 18:00:27 --- daemon.info dnsmasq-dhcp[1248]: DHCPDISCOVER(ath0.1) xx:xx:xx:xx:54:83
Dec 31 18:00:27 --- daemon.info dnsmasq-dhcp[1248]: DHCPOFFER(ath0.1) 10.15.26.25 xx:xx:xx:xx:54:83
Dec 31 18:00:27 --- daemon.info dnsmasq-dhcp[1248]: DHCPDISCOVER(br0) xx:xx:xx:xx:1a:ec
Dec 31 18:00:27 --- daemon.info dnsmasq-dhcp[1248]: DHCPOFFER(br0) 10.72.29.46 xx:xx:xx:xx:1a:ec
Dec 31 18:00:27 --- daemon.info dnsmasq-dhcp[1248]: DHCPDISCOVER(br0) xx:xx:xx:xx:77:8c
Dec 31 18:00:27 --- daemon.info dnsmasq-dhcp[1248]: DHCPOFFER(br0) 10.72.29.7 xx:xx:xx:xx:77:8c
Dec 31 18:00:27 --- daemon.info dnsmasq-dhcp[1248]: DHCPREQUEST(ath0.1) 10.15.26.25 xx:xx:xx:xx:54:83
Dec 31 18:00:27 --- daemon.info dnsmasq-dhcp[1248]: DHCPACK(ath0.1) 10.15.26.25 xx:xx:xx:xx:54:83 tp-resources
Dec 31 18:00:27 --- daemon.info dnsmasq-dhcp[1248]: DHCPREQUEST(br0) 10.72.29.46 xx:xx:xx:xx:1a:ec
Dec 31 18:00:27 --- daemon.info dnsmasq-dhcp[1248]: DHCPACK(br0) 10.72.29.46 xx:xx:xx:xx:1a:ec mrjcd-Chromecast
Jan 1 00:00:27 --- daemon.info hostapd: ath0.1: STA xx:xx:xx:xx:8d:04 IEEE 802.11: authenticated
Jan 1 00:00:27 --- daemon.info hostapd: ath0.1: STA xx:xx:xx:xx:8d:04 IEEE 802.11: associated (aid 2)
Jan 1 00:00:27 --- daemon.info hostapd: ath0.1: STA xx:xx:xx:xx:8d:04 RADIUS: starting accounting session 00000011-00000001
Jan 1 00:00:27 --- daemon.info hostapd: ath0.1: STA xx:xx:xx:xx:8d:04 WPA: pairwise key handshake completed (RSN)
Dec 31 18:00:28 --- daemon.info dnsmasq-dhcp[1248]: DHCPREQUEST(ath0.1) 10.15.26.3 xx:xx:xx:xx:8d:04
Dec 31 18:00:28 --- daemon.info dnsmasq-dhcp[1248]: DHCPACK(ath0.1) 10.15.26.3 xx:xx:xx:xx:8d:04 oShay-gst
Dec 31 18:00:28 --- daemon.info dnsmasq-dhcp[1248]: DHCPREQUEST(br0) 10.72.29.7 xx:xx:xx:xx:77:8c
Dec 31 18:00:28 --- daemon.info dnsmasq-dhcp[1248]: DHCPACK(br0) 10.72.29.7 xx:xx:xx:xx:77:8c da-Box
Dec 8 00:14:45 --- user.info : cron : cron daemon successfully stopped
Dec 8 00:14:45 --- daemon.info hostapd: ath0.1: STA xx:xx:xx:xx:8d:04 WPA: group key handshake completed (RSN)
Dec 8 00:14:45 --- daemon.info hostapd: ath0.1: STA xx:xx:xx:xx:54:83 WPA: group key handshake completed (RSN)
Dec 8 00:14:45 --- daemon.info hostapd: ath0: STA xx:xx:xx:xx:1a:ec WPA: group key handshake completed (RSN)
Dec 8 00:14:45 --- daemon.info hostapd: ath1: STA xx:xx:xx:xx:61:0b WPA: group key handshake completed (RSN)
Dec 8 00:14:46 --- daemon.debug process_monitor[2330]: Restarting cron (time sync change)
Dec 8 00:14:46 --- user.info : unbound : unbound daemon successfully stopped
Dec 8 00:14:46 --- daemon.info unbound: [1993:0] info: service stopped (unbound 1.5.10).
Dec 8 00:14:46 --- daemon.info unbound: [1993:0] info: server stats for thread 0: 70 queries, 61 answers from cache, 9 recursions, 0 prefetch
Dec 8 00:14:46 --- daemon.info unbound: [1993:0] info: server stats for thread 0: requestlist max 19 avg 5.33333 exceeded 0 jostled 0
Dec 8 00:14:46 --- daemon.info unbound: [1993:0] info: average recursion processing time 329145790.526905 sec
Dec 8 00:14:46 --- daemon.info unbound: [1993:0] info: histogram of recursion processing times
Dec 8 00:14:46 --- daemon.info unbound: [1993:0] info: [25%]=0.0709973 median[50%]=0.120149 [75%]=0.458752
Dec 8 00:14:46 --- daemon.info unbound: [1993:0] info: lower(secs) upper(secs) recursions
Dec 8 00:14:46 --- daemon.info unbound: [1993:0] info: 0.032768 0.065536 2
Dec 8 00:14:46 --- daemon.info unbound: [1993:0] info: 0.065536 0.131072 3
Dec 8 00:14:46 --- daemon.info unbound: [1993:0] info: 0.131072 0.262144 1
Dec 8 00:14:46 --- daemon.info unbound: [1993:0] info: 0.262144 0.524288 1
Dec 8 00:14:46 --- daemon.info unbound: [1993:0] info: 262144.000000 524288.000000 2
Dec 8 00:14:46 --- user.info : cron : cron daemon successfully started
Dec 8 00:14:46 --- cron.info cron[3366]: (CRON) STARTUP (fork ok)
Dec 8 00:14:47 --- daemon.debug process_monitor[2330]: Restarting unbound daemon (time sync change)
Dec 8 00:14:47 --- daemon.debug process_monitor[2330]: We need to re-update after 3600 seconds
Dec 8 00:14:47 --- daemon.info process_monitor[2330]: set timer: 3600 seconds, callback: ntp_main()
Dec 8 00:14:47 --- user.info : unbound : recursive dns resolver daemon successfully started
Dec 8 00:14:47 --- daemon.notice unbound: [3375:0] notice: init module 0: validator
Dec 8 00:14:47 --- daemon.notice unbound: [3375:0] notice: init module 1: iterator
Dec 8 00:14:47 --- daemon.info unbound: [3375:0] info: start of service (unbound 1.5.10).
Did reboot --
Jan 1 00:00:27 --- user.info : wland : WLAN daemon successfully started
Jan 1 00:00:27 --- user.info : WAN is up. IP: 96.46.xxx.xxx
Dec 8 00:34:22 --- user.info : cron : cron daemon successfully stopped
Dec 8 00:34:22 --- daemon.info hostapd: ath1: STA xx:xx:xx:xx:61:0b WPA: group key handshake completed (RSN)
Dec 8 00:34:22 --- daemon.info hostapd: ath0.1: STA xx:xx:xx:xx:54:83 WPA: group key handshake completed (RSN)
Dec 8 00:34:22 --- daemon.info hostapd: ath0: STA xx:xx:xx:xx:1a:ec IEEE 802.11: authenticated
Dec 8 00:34:22 --- daemon.info hostapd: ath0: STA xx:xx:xx:xx:1a:ec IEEE 802.11: associated (aid 1)
Dec 8 00:34:23 --- daemon.info hostapd: ath0: STA xx:xx:xx:xx:1a:ec RADIUS: starting accounting session 0000000F-00000000
Dec 8 00:34:23 --- daemon.info hostapd: ath0: STA xx:xx:xx:xx:1a:ec WPA: pairwise key handshake completed (RSN)
Dec 7 18:34:23 --- daemon.info dnsmasq-dhcp[1248]: DHCPREQUEST(br0) 10.72.29.46 xx:xx:xx:xx:1a:ec
Dec 7 18:34:23 --- daemon.info dnsmasq-dhcp[1248]: DHCPACK(br0) 10.72.29.46 xx:xx:xx:xx:1a:ec mrjcd-Chromecast
Dec 8 00:34:23 --- daemon.debug process_monitor[2261]: Restarting cron (time sync change)
Dec 8 00:34:23 --- user.info : unbound : unbound daemon successfully stopped
Dec 8 00:34:23 --- daemon.info unbound: [1922:0] info: service stopped (unbound 1.5.10).
Dec 8 00:34:23 --- daemon.info unbound: [1922:0] info: server stats for thread 0: 25 queries, 19 answers from cache, 6 recursions, 0 prefetch
Dec 8 00:34:23 --- daemon.info unbound: [1922:0] info: server stats for thread 0: requestlist max 2 avg 0.833333 exceeded 0 jostled 0
Dec 8 00:34:23 --- daemon.info unbound: [1922:0] info: average recursion processing time 0.184623 sec
Dec 8 00:34:23 --- daemon.info unbound: [1922:0] info: histogram of recursion processing times
Dec 8 00:34:23 --- daemon.info unbound: [1922:0] info: [25%]=0.147456 median[50%]=0.196608 [75%]=0.24576
Dec 8 00:34:23 --- daemon.info unbound: [1922:0] info: lower(secs) upper(secs) recursions
Dec 8 00:34:23 --- daemon.info unbound: [1922:0] info: 0.065536 0.131072 1
Dec 8 00:34:23 --- daemon.info unbound: [1922:0] info: 0.131072 0.262144 4
Dec 8 00:34:23 --- daemon.info unbound: [1922:0] info: 0.262144 0.524288 1
Dec 8 00:34:23 --- user.info : cron : cron daemon successfully started
Dec 8 00:34:23 --- cron.info cron[3283]: (CRON) STARTUP (fork ok)
Dec 8 00:34:24 --- daemon.debug process_monitor[2261]: Restarting unbound daemon (time sync change)
Dec 8 00:34:24 --- daemon.debug process_monitor[2261]: We need to re-update after 3600 seconds
Dec 8 00:34:24 --- daemon.info process_monitor[2261]: set timer: 3600 seconds, callback: ntp_main()
Dec 8 00:34:25 --- user.info : unbound : recursive dns resolver daemon successfully started
Dec 8 00:34:25 --- daemon.notice unbound: [3292:0] notice: init module 0: validator
Dec 8 00:34:25 --- daemon.notice unbound: [3292:0] notice: init module 1: iterator
Dec 8 00:34:25 --- daemon.info unbound: [3292:0] info: start of service (unbound 1.5.10).
Dec 8 00:34:29 --- user.debug : ttraff: data collection started
