This method of flashing the CFE is not recommended for 'everyone' until further testing. The instructions are good as-is. If anything we want to discourage those who are not qualified to follow them to try, but some do fall through the gaps. _________________ EA6200: r28598 as EA6350 on CFE 6.37.14.86 (r456083)
E4200: r28598
Need edit CFE because EA6350 wifi modules is switched wl0, wl1
Thank you for answer, but please give more information:
1. Need edit CFE of new build for firmware upgrade EA6200?
2. If yes, it was required on previous builds or it's new update?
3. If I already have flashed EA6200 with dd-wrt, do I need edit CFE of new builds ?
It just means that it will show up as EA6200, but underneath it detects as EA6350 anyways...
Not going to bother to update my CFE parameters to reflect this change.
You still need to flash to CFE with NVRAM bug fix if you want to use DDWRT without issues, the startup script isn't guaranteed to be enough to prevent the NVRAM bug. _________________ EA6200: r28598 as EA6350 on CFE 6.37.14.86 (r456083)
E4200: r28598
Another Question, How Can I improve USB transfer speeds?
I'm getting 13mb/s (Wired Conecction) UP/Down, with the original stock firmware I was getting 20mb/s up and 32mb/s down.
Posted: Tue May 03, 2016 18:57 Post subject: EA6200 xvortex CFE derived from LOM's EA6350 version.
With xvortex-cfe-ea6200-as-ea6350-with-ea6200-devinfo.bin, almost all the builds from 2016 were showing a kernel-space memory leak such that the ea6200 could not be used for more than a day.
I'm now on ddwrt-r29519, and the ea6200 is stable, with no memory increase. I'm uploading LOM's-xvortex-CFE-for-ea6350-modified-for-ea6200 for others to try out (usual disclaimer applies).
This binary is the same as LOM's xvortex CFE for the ea6350, but with the following differences:
Code:
devpath0=pci/2/1 (was pci/1/1 for EA6350)
devpath1=pci/1/1 (was pci/2/1 for EA6350)
boardnum=20130125 (was 20140309 for EA6350)
boardrev=0x1100 (was 0x1200 for EA6350)
modelNumber=EA6200 (was EA6350 for EA6350)
0:macaddr=hw_mac_addr+3 (was hw_mac_addr+2 for EA6350)
1:macaddr=hw_mac_addr+2 (was hw_mac_addr+3 for EA6350)
You will have to change the following according to your EA6200 router, using CFEEdit.exe (included):
Consider me a total noob in this space. I installed many DD WRT before and im looking for a router that supports openvpn. There is a used EA6200 router for sale, idk if it's v1 or v2.. and it seems that only the v1 is supported?
After reading this thread I'm a little afraid to flash this router.. I don't really want to fiddle with CFE or whatever as I also have a mac and not windows.
So.. should I avoid this router? Any other considerations to take into account because in the DB it doesn't mention any issue with the build and only in a search this post came out.
I'm still on the CFE from the Chinese forum, just wanted to chip in that I have successfully updated to Kong's Firmware: DD-WRT v3.0-r29620M kongac (05/10/16)
If I run into any issues I might try the modded EA6350 CFE, but other than the swapped radios everything has been stable. I seem to be getting good WiFi speeds on it so no reason for me to change anything. _________________ EA6200: r28598 as EA6350 on CFE 6.37.14.86 (r456083)
E4200: r28598
Posted: Wed May 25, 2016 13:43 Post subject: Running stable on ddwrt-r28598.
Good Morning All,
Just wanted to say that my ea6200 is finally running stable on ddwrt-r28598 with the above CFE. Note that my usage is routing-only, and so I am not using the radios. However, I have another one planned which will likely have the 5GHz radio (only) enabled. We'll see.
BTW, I also tried inserting the "default CFE params" found in xvortex-cfe-lom-ea6350-for-ea6200.bin into Linksys' default CFE and flashed that onto the ea6200. The good news is that that made it brick-proof, i.e. if you had accidentally erased the nvram/devinfo partitions via manual, or 30-30-30 or web GUI, the router did not turn into a brick. HOWEVER, it did not bring in all the "0:" and "1:" parameters after such an event, and so no WiFi (with default Linksys firmware). That CFE really is the pits. Bad Linksys.
Also BTW, openwrt-20160520's openwrt-bcm53xx-linksys-ea6300-v1-squashfs.trx works on the ea6200 with the above CFE. The first boot had a lot ubi warnings, but it's up and running with 122M rootfs! Now have to find out what's usable ...
did the CFE edit and flash successfully I'm pretty sure.. trying a coule different firmware versions I'm now stuck at a boot looping CFE miniWeb Server page _________________ DD-WRT w/ Superchannel, Ubiquiti RS Pro @800Mhz, Ubiquiti SR71-A a/n,g/n
ok, so I found that in order to make it not loop and get a full firmware uploaded it is necessary to start the router with the reset pushed for a few seconds and then it will not automatically reboot until a successful firmware upload. I'm running the latest R6350 now. I know this is a dd-wrt forum but has anyone tried alternate firmwares with the new CFE? _________________ DD-WRT w/ Superchannel, Ubiquiti RS Pro @800Mhz, Ubiquiti SR71-A a/n,g/n
lowlymortal, even with your CFE my router eventually crashed from the memory leak with 6/6/16 and your r29529. So far so good on r28397 12/1/15. Holding at 68% free _________________ DD-WRT w/ Superchannel, Ubiquiti RS Pro @800Mhz, Ubiquiti SR71-A a/n,g/n