wl520gu-hax wrote:Even if adding more memory is possible, you see, there is still the problem of working with a configuration that doesn't know it, and the problem of telling it how to go about using all the fancy new stuff you just added. it's a bit of a catch 22.
The way I imagine it working is: you compile an openwrt kernel that's using most of brainslayer's .config so it's really quite braindead at first.
That should be the first step to get around this 2MB limitation.
My RAM arrived today, so tomorrow I plan to bump up to 64 MB (will test the 256 MB later since I am still not certain A12 would be connected, and I don't feel like x-raying the guy to find out). I have installed dd-wrt micro on this guy, so I think I can test out the increased RAM through that, once that is verified, then I plan to try and flash OpenWrt onto it with 2 MB of flash since the .bin file is 1.8 MB. Am I missing something there?
After OpenWrt is up and running, then it will be time for the mmc hack to increase the flash space, I have a 32 MB SD card waiting with a floppy cable salvaged from the scrap heap in the garage. I love doing hardware on a budget, I have quite the reputation as a dumpster diver around the office 
I'll keep you posted on my adventures, given the cheap v8s found on ebay, I may try and pick one up to test with since I ordered extra RAM.
Update: Well, all is not happy in Muddville. Adding the RAM chip is easy when you have proper tools (hot air station, fine tip iron), but you are dead nuts on, the config is not going well. I have installed dd-wrt micro so I have a telnet to change nvram parameters, but that doesn't seem too kosher to the v5 for some reason. I did have to tie A12 on the RAM to ground (it is NOT connected on the board...geez guys thanks for bothering to take a trace away you had on previous revs!), but it happily boots with the new chip as an 8 MB chip (it is a 256 Mbit chip, so 64 MB onboard). Trying to turn on the "extra" memory leads to wonderful bricklike behavior. Thankfully, a simple erase of the NVRAM and it returns to operation (make a jtag cable before changing any chips...odds are you will need it!). I am going to keep monkeying with the nvram settings and see if I can get it to open up, but I am starting to wonder if the guys at Linksys have actually gone to the trouble to screw us over on the BCM5352.
OK, some success. I don't understand why it took so long to work, but this morning I did the following from the telnet prompt:
nvram set sdram_init=0x0A
nvram set sdram_ncdl=0x0000
nvram commit
I then exited the telnet session and instead of power cycling, used the dd-wrt webpage to reboot, and presto, 16 MB now available on my v5 router. I swear I tried the nvram settings above first shot with a brick following a power cycle, but maybe I screwed something up. Sadly, the chip I put in only has 9-bit column addressing, so I can't get at the rest of the memory (it is a 256 Mbit chip), but if things go well from here on out, I will probably get a better chip to put on now that I have a better understanding of what is happening. I will keep you posted with further progresses as it occurs (just tested a power cycle, all is well, still have my 16 MB). Joy returns to Muddville!
(Last edited by Milkman on 9 Apr 2008, 13:41)