I'm working on a port of the ADM6996M driver, wish me luckPondera wrote:rbilka wrote: is there any hope, that someone will fix/add the necessary SWITCH driver (or perhaps some work-around which we can do thru telnet/ssh) to the routerTech firmware, for D-Link's modems like 584/G684 and many others D-Link's modems/routers ?Not properly one or two...thechief wrote: Since there are one or two DLink routers that have this switch, and we are unlikely to change the existing switch driver code, perhaps "someone" could write a script for the admtool to set up VLANs? I am sure this would be of immense help to those who have the ADM6996 switch.
DSL-584T/G684T are the Annex B version of DSL-524T/G624T! Also I have a DSL-524T and a DSL-G624T and both they use ADM6996 switch! And these are only the European ADAM2 based models!
The equivalent South American and Asiatic PSPBoot based models are DSL-2540T/2640T and the Australian DSL-504T/G604T Generation II!
DLink DSL-2640t bricked and recovered...
Re: DLink DSL-2640t bricked and recovered...
- thechief
- RouterTech Team
- Posts: 12067
- Joined: Wed Feb 01, 2006 10:22 pm
- Location: England, the Centre of Africa
- Contact:
Re: DLink DSL-2640t bricked and recovered...
I wish you luck!geekgirl wrote:I'm working on a port of the ADM6996M driver, wish me luck
You may also wish to note that the kernel code for the 1350A wireless is different from that of the 1130 wireless/non-wireless (i.e., "standard"). You need to bear this in mind if you're thinking of supporting both 1350A and "standard".
The Chief: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
No support via PM. Ask all questions on the open forum.
Re: DLink DSL-2640t bricked and recovered...
yep... I'm only going to propose patch for the ROHS firmware sources
Re: DLink DSL-2640t bricked and recovered...
I have a Linksys AG241V1 which has a ADM6996L switch (similar to many other Linksys variants), never tried RouterTech firmware on it - would be great if there was a switch driver that would work is the "L" anything like the "M" that is used in 2640T?
Re: DLink DSL-2640t bricked and recovered...
I'm not an expert on the topic, so probably not the best to ask. But will tell you what I know so far from general research I did earlier:mstombs wrote:is the "L" anything like the "M" that is used in 2640T?
http://www.infineon.com/cms/en/corporat ... 32389.htmlThe Samurai product family consists of four six-port controllers: ADM6996LC, ADM6996FC, ADM6996I, ADM6996M and one five-port controller: ADM6995LC.
So the ADM6996* are all six-port controllers.
As to differences, I'm quite clueless. All I can find is from the following pdf:
http://www.infineon.convergy.de/upload/ ... Rev1.4.pdf
There's a few mentions of "ADM6996L/F style storming control" vs. "ADM6996FC/FCX/FHX style storming control" on page 105 (out of 187) of the above-mentioned pdf.3.25 The Hardware Difference between ADM6996FC/FCX and ADM6996F
ADM6996FC/FCX is power-down version to replace ADM6996F and ADM6996M is advanced function version to new application.
N.B.:
In November 6, 2009, Infineon sold its wireline business to Lantiq.. It's really hard to find any worthy info (or datasheets) on Lantiq's site:
http://www.lantiq.com/products/home-net ... i-adm6996/
searching for datasheets:
http://www.alldatasheet.com/view.jsp?Se ... d=ADM6996M
I can only find old datasheets (from 2004) for the L and the F, none specific for the M.
Re: DLink DSL-2640t bricked and recovered...
Hi all.
I see that You all experts here and You really know what you are doing.
I can't understand most of what has been discussed here but I want to share this:
I have a dsl-2640t and I was able to upgrade it to RouterTech firmware, almost everything works fine (wireless, wan pppoe, lan,..). I only have issues with IPQos, rshapre and wget (not working). Maybe I am not using the correct settings.
My router bricked the first time I flashed it with RT firmware (using web interface). But I recovered it using both pctool and RRT (I used pctool to get the ip and then RRT to flash the router with the original firmware). After that I've flashed it with RT several times with no problems.
Device info:
H/W Ver.: B1
F/W Ver.: V3.02B01T01.ME-A
Thanks
I see that You all experts here and You really know what you are doing.
I can't understand most of what has been discussed here but I want to share this:
I have a dsl-2640t and I was able to upgrade it to RouterTech firmware, almost everything works fine (wireless, wan pppoe, lan,..). I only have issues with IPQos, rshapre and wget (not working). Maybe I am not using the correct settings.
My router bricked the first time I flashed it with RT firmware (using web interface). But I recovered it using both pctool and RRT (I used pctool to get the ip and then RRT to flash the router with the original firmware). After that I've flashed it with RT several times with no problems.
Device info:
H/W Ver.: B1
F/W Ver.: V3.02B01T01.ME-A
Thanks
- thechief
- RouterTech Team
- Posts: 12067
- Joined: Wed Feb 01, 2006 10:22 pm
- Location: England, the Centre of Africa
- Contact:
Re: DLink DSL-2640t bricked and recovered...
Well, I can definitely confirm that the admtool is brilliant. I acquired a G624T with fully working wireless, but with all four ethernet ports dead. A bit of experimentation with the admtool restored ports 1, 3 and 4. For the curious, these are the commands I ran
The code 0x8000 means "reset the port (self clear)".
Port 2 is still dead, but that is not an issue - except that all these problems with the adm6996 may point to an inherent flakiness in this switch. I haven't really tried very hard to resuscitate port 2 - but it may well be that it is like the OP's port 4 (and if it comes alive, then all the ports will die).
It seems that this admtool can be used to do virtually anything with the adm6996 switch.
Code: Select all
adm6996-tool 0x1 0x8000 #lan port 4
adm6996-tool 0x3 0x8000 #lan port 3
adm6996-tool 0x5 0x8000 #lan port 2
adm6996-tool 0x7 0x8000 #lan port 1
Port 2 is still dead, but that is not an issue - except that all these problems with the adm6996 may point to an inherent flakiness in this switch. I haven't really tried very hard to resuscitate port 2 - but it may well be that it is like the OP's port 4 (and if it comes alive, then all the ports will die).
It seems that this admtool can be used to do virtually anything with the adm6996 switch.
The Chief: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
No support via PM. Ask all questions on the open forum.
Re: DLink DSL-2640t bricked and recovered...
On several italian forum it's been noticed similar problems with 524T/G624T switch...thechief wrote:I acquired a G624T with fully working wireless, but with all four ethernet ports dead. A bit of experimentation with the admtool restored ports 1, 3 and 4.
[...]
Port 2 is still dead, but that is not an issue - except that all these problems with the adm6996 may point to an inherent flakiness in this switch. I haven't really tried very hard to resuscitate port 2 - but it may well be that it is like the OP's port 4 (and if it comes alive, then all the ports will die).
salted has fixed it changing a couple of 100 uF 25 VL 105°C spent condensers (red arrow) and also a too hot 1000 uF 25 VL 105°C condenser (blue arrow):
salted (HWU forum) wrote: Connessione eThernet solo a 10 Mb
Dopo 2 anni anche il mio DSL G624T ha cominciato a funzionare sulla ethernet solo alla velocità fissata sul PC a 10 Mb e alcune porte non funzionavano più. Era un problema HW legato allo switch interno costituito dall'integrato Infineon ADM6996M. L'ho risolto cambiando due condensatori da 100 uF 25 VL a 105°C e per precauzione anche un condensatore da 1000 uF 25 VL 105°C che scaldava troppo (nella foto indicati con frecce rossa e blu rispettivamente). Ora l'interfaccia ethernet è tornata a funzionare regolarmente... come nuovo!
- thechief
- RouterTech Team
- Posts: 12067
- Joined: Wed Feb 01, 2006 10:22 pm
- Location: England, the Centre of Africa
- Contact:
Re: DLink DSL-2640t bricked and recovered...
Conclusion: dodgy system boards (and poor quality control)
The Chief: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
No support via PM. Ask all questions on the open forum.
- thechief
- RouterTech Team
- Posts: 12067
- Joined: Wed Feb 01, 2006 10:22 pm
- Location: England, the Centre of Africa
- Contact:
Re: DLink DSL-2640t bricked and recovered...
Passing "0x800F" to each port resuscitated all the ports, but had to set the PC's network card manually to 10Mbps for any of it to work.thechief wrote:Port 2 is still dead, but that is not an issue - except that all these problems with the adm6996 may point to an inherent flakiness in this switch. I haven't really tried very hard to resuscitate port 2 - but it may well be that it is like the OP's port 4 (and if it comes alive, then all the ports will die).
If anyone has a fully functional G624T or 2640T, it would be interesting to see the output of "adm6996-tool dumpall".
The Chief: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
No support via PM. Ask all questions on the open forum.
Re: DLink DSL-2640t bricked and recovered...
I have a 2640T with RT firmware working just fine.
If anyone can tell me where to find the tools and what to do, maybe I can help.
If anyone can tell me where to find the tools and what to do, maybe I can help.
RouterTech_3.7.1B_1350A_20100105_2.92 on D-Link DSL-2640T
- thechief
- RouterTech Team
- Posts: 12067
- Joined: Wed Feb 01, 2006 10:22 pm
- Location: England, the Centre of Africa
- Contact:
Re: DLink DSL-2640t bricked and recovered...
The tool is posted earlier in this thread. But I have now obtained the required information from a 524T. Thanks.
The Chief: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
No support via PM. Ask all questions on the open forum.
Re: DLink DSL-2640t bricked and recovered...
geekgirl, any news on adm6996 driver?
as jtag is already soldered to my router, im thinking if i should go and write it.
EDIT1:
Ok, basic driver is ok and working perfectly on my dlink 2640t. Im impressed with the HUGE AND UGLY MESS that is AR7 kernel code.
Later (or tomorrow) i will implement some fancy stuff, vlan, priorities, etc.. For now the driver functionality is very basic, just enough to detect the chip and make the interfaces (on /proc or the web GUI) report proper data.
as jtag is already soldered to my router, im thinking if i should go and write it.
EDIT1:
Ok, basic driver is ok and working perfectly on my dlink 2640t. Im impressed with the HUGE AND UGLY MESS that is AR7 kernel code.
Later (or tomorrow) i will implement some fancy stuff, vlan, priorities, etc.. For now the driver functionality is very basic, just enough to detect the chip and make the interfaces (on /proc or the web GUI) report proper data.
- thechief
- RouterTech Team
- Posts: 12067
- Joined: Wed Feb 01, 2006 10:22 pm
- Location: England, the Centre of Africa
- Contact:
Re: DLink DSL-2640t bricked and recovered...
Well done!drwyrm wrote:Ok, basic driver is ok and working perfectly on my dlink 2640t.
Welcome to our world. If you think that the kernel code is a mess, look at the html code for the web interface - an even greater mess (archetypal spaghetti code).drwyrm wrote:Im impressed with the HUGE AND UGLY MESS that is AR7 kernel code.
The Chief: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
No support via PM. Ask all questions on the open forum.
EEPROM is corrupted!!
Hi,
I have a problem with the EEPROM of my DSL card, Its data is corrupted and I cant connect to the internet via cable anymore (Local only) but my wireless works.
how can I repair EEPROM's data?
tnx
I have a problem with the EEPROM of my DSL card, Its data is corrupted and I cant connect to the internet via cable anymore (Local only) but my wireless works.
how can I repair EEPROM's data?
tnx