I have turbo nat enabled, but not sure if it works :/
I honestly don't know what Turbo Nat does. On my router with V1 Hardware and V2 Firmware I am unable to ' enable ' Turbo Nat. It doesn't reboot as the message states but simply reverts back to ' Disabled '.
Asking doesn't bring a port of dd-wrt closer.
There won't be any until Brainslayer has a router on his desk which supposedly never will happen since this thread is only populated by free-riders.
I would be willing to help out jwbaynham with his costs if indeed the router has been sent to DD-WRT for testing.
I just acquired a second ESR-9850 yesterday, opened it up, took pictures, installed a serial cable, loaded DD-WRT for ESR-9752 on it (at some risk) and have posted the results here for anyone to analyze.
Last edited by chateau on Wed Nov 17, 2010 14:24; edited 2 times in total
Well, it looks like I may have done damage to the router. I did a power down at the wrong time during a flash of DD-WRT. (Oh Well)
Edit: I forgot to mention the router still works (with the original firmware flashed) in that DHCP works, I can access the internet and other web pages, just not the one at 192.168.0.1.
The router will still boot and I can use Option 2 or Option 4. The original firmware (uImage_esr9850.bin) will load and I can then install the dlf files from the web interface. Unfortunately after that the web interface for normal operation says it has an error and the page does not load.
If I try to flash DD-WRT using firmware.bin for the ESR-9752 it goes to a point and then loops endlessly displaying memory address 0xBF169202
If I choose Option 4 during uBoot I can erase Linux and erase Bank 1. Both appear to work but to no avail.
Here is how far it gets in the process now when flashing DD-WRT.
Please choose the operation:
1: Load system code to SDRAM via TFTP.
2: System Load Linux Kernel then write to Flash via TFTP.
Warning!! Erase Linux in Flash then burn new one. Are you sure?(Y/N)
Please Input new ones /or Ctrl-C to discard
Input device IP (192.168.99.9) ==:
Input server IP (192.168.99. ==:
Input Linux Kernel filename (uImageESR9850) ==:firmware_esr9752.bin
Using Eth0 device
TFTP from server 192.168.99.8; our IP address is 192.168.99.9
Filename 'firmware_esr9752.bin'.
Loading: checksum bad
checksum bad
checksum bad
checksum bad
checksum bad
ArpTimeoutCheck
Got ARP REPLY, set server/gtwy eth addr
Got it
checksum bad
checksum bad
checksum bad
T #
first block received
################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#
done
Bytes transferred = 3661082 (37dd1a hex)
Erase linux kernel block !!
From 0xBF050000 To 0xBF3CFFFF
Please choose the operation:
1: Load system code to SDRAM via TFTP.
2: System Load Linux Kernel then write to Flash via TFTP.
Warning!! Erase Linux in Flash then burn new one. Are you sure?(Y/N)
Please Input new ones /or Ctrl-C to discard
Input device IP (192.168.99.9) ==:
Input server IP (192.168.99. ==:
Input Linux Kernel filename (uImageESR9850) ==:uImage_esr9850.bin
Using Eth0 device
TFTP from server 192.168.99.8; our IP address is 192.168.99.9
Filename 'uImage_esr9850.bin'.
Loading: checksum bad
checksum bad
checksum bad
checksum bad
checksum bad
ArpTimeoutCheck
Got ARP REPLY, set server/gtwy eth addr
Got it
checksum bad
checksum bad
checksum bad
T #
first block received
################################################################
#################################################################
#################################################################
############
done
Bytes transferred = 1059403 (102a4b hex)
Erase linux kernel block !!
From 0xBF050000 To 0xBF15FFFF
This pretty much confirms that I have killed part of the flash memory. It is from Putty's serial terminal while upgrading the APPS firmware (not from the normal web interface) but via the recovery web interface (Bluebox).
I do want to make it clear that flashing DD-WRT did not brick the router. I had flashed firmware.bin for the ESR-9752 onto the router at least three times and then flashed it back to the original firmware each time with no problems. I was trying to capture the data in Putty's screen to post here and simply pulled the power at the wrong time during a flash.
I do want to make it clear that flashing DD-WRT did not brick the router. I had flashed firmware.bin for the ESR-9752 onto the router at least three times and then flashed it back to the original firmware each time with no problems. I was trying to capture the data in Putty's screen to post here and simply pulled the power at the wrong time during a flash.
Pulling the power plug while flashing should normally not damage the flash, it looks from your logs as if cell bit has got stuck or a flash sector has become write protected.
I suppose that you never got the LAN switch working, ESR-9752 is using the RT3052's internal switch while an ESR-9850 has an external gigabit switch.
Do you have any log from stock firmware showing the mtd partitions, ie their addresses and sizes? _________________ Kernel panic: Aiee, killing interrupt handler!
Pulling the power plug while flashing should normally not damage the flash, it looks from your logs as if cell bit has got stuck or a flash sector has become write protected.
I suppose that you never got the LAN switch working, ESR-9752 is using the RT3052's internal switch while an ESR-9850 has an external gigabit switch.
Do you have any log from stock firmware showing the mtd partitions, ie their addresses and sizes?
Trying to un-protect the flash (Option 4 during uBoot) was how I finally bricked the router. I have been known to do a dumb thing every now and then.
Edit: Yes I knew the ESR-9850 has a separate Gibabit Switch and has little or no chance of the switch working with the ESR-9752 firmware. What I forgot to test was the wireless. It uses the RT3052f to my knowledge. Will try that when I get things going again.
The LAN or WAN switch does not work with ESR-9752 flashed on the router. I did notice that all the LEDs for Power, LAN, WAN did work with DD-WRT, even after a power down. By working I mean they responded to an ethernet cable being plugged in and appeared to blink with traffic.
I did notice that some of the GPIO seemed pretty standard in that GPIO 0 is WPS and GPIO 10 is Reset. I think that in one of my posts using factory firmware they also called GPIO 7 to reboot the router.
Edit: I will be able to get a log of the factory firmware KNL and APPS being loaded via Putty using the Recovery Web Interface (Bluebox). I have posted the same information for ESR-9752 so I know it is available, just did not check for it earlier. Unfortunately when using option 2 from uBoot there is little information to see. There is no access to telnet that I know of. With the factory firmware you end up in the Console mode which does not show much. I may be missing something in Console but have been unable to use it.
I would be glad to test for anything you want on my other ESR-9850 but it will take me a day or so to do that.
Edit: This is where the Kernel is flashed by factory firmware. Not sure if that is of any use.
Joined: 22 Jun 2007 Posts: 277 Location: Physically: Somewhere in time and space / Mentally: As lost as the next person
Posted: Thu Nov 18, 2010 3:19 Post subject:
This router definitely needs some DD-WRT love...the GUi on this bad boy is a beast...it really sucks! I could see that DD-WRT would be the last link to make it a notably great router...up there with the very best!
My main issue currently with it is the dang wireless config...confusing as hell!