same here, wnr3500l V2, it doesn't accept any non netgear firmware
can anyone help me ,, i have a netgear 3500L v2,,
I have searched the site and cannot find any information as regard putting tomato firmware on it ,,???
i know on the 3500L you have to put a chk file on then ddwrt firm then tomato ,, i can find them files but there is no mention of files for the 3500LV2,,
has anyone who has the 3500LV2 got tomato on there router,, and what files did you use,,
any help appreciated
It is listed in the DD-WRT database. You might want to try the one it shows.
they only have the v1 and not the v2
cutebuny said: they only have the v1 and not the v2
It looks like they do to me.
thats the 3500, but netgear released the WNR 3500L v2
Thanks, Now I gotcha on the L and v2. I am not sure what the difference is. If it doesn't take the L V1 firmware then a look at what chipset and the other hardware would be in order.
Have you looked into what they are using hardware wise on it?
nope not yet, my friend I don't have it with me right now as I finally ordered one today.
my friend ordered one from amazon and got a V2 so I am sure that I will be getting a V2 also
digging up more info
Hopefully netgear didn't pull a linksys and cut the flash and RAM in half
(took a lot of bing searching and second life camping to rackup the amazon.com gift cards)
The Broadcom BCM47186 may be different than the BCM4718 that the V1 uses.
You can see the switch is the same here.
I have no idea right now on the rest. Can you turn on SSH or telnet and go to a shell prompt (telnet or ssh) and type the following
That should give you more info.
the linksys e3200 uses the same CPU
does this help:
oops. false alarm. i think i have v1 :/
BusyBox v1.7.2 (2011-07-22 15:11:05 SGT) built-in shell (ash)
Enter 'help' for a list of built-in commands.
# cat /proc/cpuinfo
system type : Broadcom BCM5357 chip rev 1
processor : 0
cpu model : MIPS 74K V4.9
BogoMIPS : 239.20
wait instruction : no
microsecond timers : yes
tlb_entries : 64
extra interrupt vector : no
hardware watchpoint : yes
ASEs implemented : mips16 dsp
VCED exceptions : not available
VCEI exceptions : not available
unaligned_instructions : 34
dcache hits : 2147483648
dcache misses : 4244618014
icache hits : 2147483648
icache misses : 1940545341
instructions : 2147483648
# nvram get clkfreq
One major difference between WNR3500L and WNR3500Lv2 is WNR3500L uses serial flash whereas WNR3500Lv2 uses NAND flash. So I assume some amount of modification need to be done in Tomato/DD-WRT/OpenWRT firmware to support this flash.
Tathagata Das said: One major difference between WNR3500L and WNR3500Lv2 is WNR3500L uses serial flash whereas WNR3500Lv2 uses NAND flash.
Can you explain the difference between serial flash and NAND flash? This might help in figuring things out.
Brandon C said:Tathagata Das said: One major difference between WNR3500L and WNR3500Lv2 is WNR3500L uses serial flash whereas WNR3500Lv2 uses NAND flash.Can you explain the difference between serial flash and NAND flash? This might help in figuring things out.
I didn't look into that in details.
I noticed in the source code that WNR3500Lv2 uses serial flash as well as nand flash. Also based on this nand flash selection flash layout and flash accessing codes are modified.
The BCM47186 is a dual radio solution, same as Linksys E3200.
The reason why you cannot flash an existing chk file for the wnr3500l is, because the chk does not contain the correct header ( see ambitCfg in netgears src package) for the wnr3500lv2.
#define AMBIT_HARDWARE_VERSION "U12H12700"
#define AMBIT_HARDWARE_VERSION "U12H17200"
I can create a compatible chk file, that the netgear update interface will accept. I don't think the nand flash should be a problem, rather the partition/flash layout. I guess this unit also has 60K or 64K of nvram space.
@cutebunny, if you run:
what size does it report at the last line?
@Kong, are you able to boot WNR3500Lv2 with your firmware ? There are some NAND flash specific changes which I guess necessary for that board.
the current drivers included by dd-wrt do not contain a nflash.c as in the netgear package, the netgear shipped wl_ap.0 says it's of version Broadcom BCM%04x 802.11 Wireless Controller 5.60.136. So the drivers are brandnew and I also doubt the unit will work without updateing the drivers.
So we will have to wait for BS to update the driver, after that eko usually adds patterns mtd layouts etc.
On the last line it shows
size: 21592 bytes (11176 left)
Puuuh, this doesn't look any good. Basically that is not enough to enjoy all features which are currently in my wnr3500lv1 build, which shows: size: 27272 bytes
This is great — releasing a router specifically marked as an open-source router, whereas not only is it not supported by OSS (due to lack of specifications and datasheets on the hardware), but noone in the open-source community is even notified regarding the hardware changes nor of the fact that the new and incompatible hardware is already shipping. With none of the 3rd party firmwares working out of the box for weeks after the ship date!
Brilliant, NETGEAR! Thanks for your clearly false advertising and lack of appropriate hardware and revision specifications!
Want some advise? Before you ship the new hardware to Amazon like this, at least have the courtesy to notify OSS involved and make both the datasheets and the hardware readily available to OSS first.
is there a way to increase the nvram storage, or use any additional flash memory storage left over as additional nvram?
It would require to hack or compile (if we had the sources for it, but this is a broadcom problem) a new cfe.
But installing a new cfe isn't as easy as flashing the firmware.
So again this really sucks and if you look at the latest linksys models which have either 60k or 64k this is really sad.
I think it may be listing both sizes separately
I did a full hard reset
size: 21420 bytes (11348 left) The total nvram may be 32768
with a router with what I am assuming to be 8MB flash storage, if the firmware is around 6-7MB, why cant they just spare a few more KB and reserve like 128K or so.
Is there any benefit to making it small?
The only benefit of "keeping" it small is that you don't have to modify your kernel source code scripts etc.
So basically there was a time when 20k was okay, but since the feature set increased you need more, that howver requires a few changes in your code.
This is why you have different builds now, e.g. my E3000 build is not the same as my wnr3500lv1 build although they have the same hardware, the E3000 has 60K nvram and I compile them once with 60k defined and without.
Therefore the only reason is can think of is that netgear sticks with such low nvram is because it is less work for them. The more models out there the more differences the more work has to be done.
Thus dd-wrt is currently the only router firmware that has a single codebase which can be used to create builds for any router platform and it is pretty easy to integrate a new model. Tomato is limited to a few platforms, openwrt does not support all platforms.