Update: I receive many emails from people who are trying to update their DSL-2640T with Routertech firmware after looking at this thread or this post. I must update here that the Routertech team has declared this router as “incompatible” with their wireless PSP firmware. If you’re still going to update to this firmware, either know what you’re doing and ask reasonable questions, or you’re on your own.
WARNING: Always check the firmware you need to download using RUC first (linked below).
Before you start, I must say that updating a router’s firmware is not for the faint hearted and I take no responsibility if anything goes wrong with your router. This is pretty much a n00b friendly tutorial, so you should be okay, if you follow everything as written in the RouterTech’s help docs and in this tutorial. Now over to the tutorial:
Please download the following tools and confirm the settings following afterward.
1- Download RUC (Router Update Checker, available here
2- Download WEB (Wireless Environment Builder, available here).
3- Download your router’s latest official firmware (you should have a copy, in case this goes kaput).
Now whatever you do, don’t blame me. Next open up RUC and enter your router login info, defaults are:
ip: 192.168.1.1web user: adminweb pass: admintelenet user: roottelnet pass: adminno of ethernet ports: 4router description: dlink g624T
check all boxes at the bottom (they are there for a reason).
* You can edit the routers.txt and make an entry for DSL-2640T as follows too:
Once RUC gives you a report, it should be similar to the following:
Router Upgrade Check 1.2.9 19/09/2008 09:49:15Router IP: 192.168.1.1CLI is neededDescription: Dlink G624TBoard type: AR7VWProduct ID: AR7WRDBootloader: psblRAM 16.0 MBFlash (ROM) 4.0 MBADAM2: NoNo default env: NoLinux version: 2.4.17_mvl21-malta-mips_fp_leFirmware build:Firmware version: V3.02B01T01.ME-A.20080125Firmware stamp: 20080125143616CPU: MIPS 4KEc V4.8DSP: 6.00.04.00Annex: A/proc/wlan: Yes/usr/sbin/wlan: YesTIAP: YesTNETW: YesWireless: YesWIFI chip: TNETW1350AWIFI chip conf: YesPorts: 4Marvell (or Marvell like): NoNSP: V3.02B01T01.ME-A.20080125Manufacturers: D-link CorporationRNDIS: Telogy Networks Inc
Now, the things to make sure in the above log are:
Product ID or Board type: AR7WRDBootloader: psblRAM 16.0 MBFlash (ROM) 4.0 MBWIFI chip: TNETW1350AMarvell (or Marvell like): No
The above settings will qualify you for a RouterTech firmware upgrade. The reason to run RUC was to backup all your settings and configurations at one place. If you have not backed-up your settings, do it now. No one will be responsible, if you do this carelessly and brick your router.
Download RouterTech firmware from http://routertech.org/forum.php. You must register on the forum to download the firmware. For DSL2640T, you’ll need the RoHS 4-port PSP firmware. It should be named something as follows:
extract it to some directory and open up the upgrade.html file and DO WHAT IT SAYS.
1- back-up all your settings
d- config.bin (using your router’s “save config to hard disk” option in the web panel)
2- reset your router to factory default settings. reboot.
3- once the router comes back online, save all settings and reboot again.
4- open up the update firmware panel in the router’s web panel; Tools->Firmware and browse to where you extracted the above zip file and select:
Now click on Apply and pray to God that all goes well. Leave the router alone for about
After ten minutes, telnet into your router again and see if it lets you log in using:
Log in using user:Admin and pass:Admin
If the router let you log in, go to your Router’s web panel and into the System panel. Click on Restore Factory Settings and Reboot. Once the router comes online. Telnet back into your router:
and take a look at the variables and back them up.
Next perform the following steps:
setenv led_conf led.2640t && /sbin/reboot
once again, when the router comes back online. Telnet again into the router and type:
setenv vlynq_polarity low
Reboot the router once again and you should have a working DSL-2640T running with everything on a custom routertech firmware. You can issue all the commands above in a single go but I say, do not mess with your router, unless you are confident of your actions.
For the people, who do not have their WLAN working, after the upgrade or even so before the upgrade, please follow the steps below:
A common issue for many people on a router exists, where the AP stays off and only comes online by using
"echo NVS_TFTP_LOAD 0 > /proc/ticfg/env"
However, this can create issues on the environment side and the solution itself is temporary too. The actual issue is a corrupted WLAN EEPROM, which needs to be fixed:
– Extract WEB (Wireless Environment Builder) somewhere in a directory and open it up.
– Fill up the information it asks for.
– If you do not have a TWNET ID, go to your router’s system logs. They can be found in Status->SystemLog. Browse them and find the line where it says:
"Failed to get DIE ID from wlan driver. Cannot validate EEPROM Image"........"Setting bootloader env NVS_TFTP_LOAD to 1"
– Look for a string similar to this:
"Retrieving EEPROM image file nvs_5e015cf4a901151d.bin from TFTP Server""ERROR: TFTP of file : nvs_5e015cf4a901151d.bin failed"
– there, the string next to “nvs_” is your TWNETID i.e.5e015cf4a901151d. It should be different for you.
– copy it in WEB and click on “get router details” or “build environment”. It should work and after a while, it will ask you that it can send the script directly to the router. Do so, and let the router reboot after that. You’re done, once the Router comes back online, go check your environment now and you’re good to go.
I hope this will help many people. You might wanna head over to RouterTech for more help and if you run into any issues. Those guys are a great help and they have some fantastic stuff there.
- LinkDotNet – PTCL – ADSL Hell
This entry was posted on Friday, February 20th, 2009 at 11:53 am
You can follow any responses to this entry through the RSS 2.0 feed.