Well I kinda thought that but how are people seemingly messing up their CFE from firmware updates? Also, can you change the way DD-wrt installs to overwrite the CFE?
Joined: 26 Jan 2008 Posts: 13049 Location: Behind The Reset Button
Posted: Thu Oct 20, 2011 18:43 Post subject:
Bird333 wrote:
Well I kinda thought that but how are people seemingly messing up their CFE from firmware updates? Also, can you change the way DD-wrt installs to overwrite the CFE?
installing dd-wrt does not, can not, write the cfe space using normal methods (tftp, gui upgrade, etc). I suppose things can get screwed up if someone "experiments" with firmware in a router that is not supported but even then, writing the cfe space really can't happen.
The only time a cfe needs replacing is when the install procedure manipulates the cfe (vxworks bsp to linux cfe, TM, RG, etc.), and replacing a cfe to change a router (320 to e2000, 610 to e3000) and things go wrong.
What you see is someone that bricked the router and all that needs to be done is to erase nvram and / or kernel but they fire up jtag and erase wholeflash.
you can mess thing up with mtd commands. _________________ [Moderator Deleted]
Well I kinda thought that but how are people seemingly messing up their CFE from firmware updates? Also, can you change the way DD-wrt installs to overwrite the CFE?
installing dd-wrt does not, can not, write the cfe space using normal methods (tftp, gui upgrade, etc). I suppose things can get screwed up if someone "experiments" with firmware in a router that is not supported but even then, writing the cfe space really can't happen.
The only time a cfe needs replacing is when the install procedure manipulates the cfe (vxworks bsp to linux cfe, TM, RG, etc.), and replacing a cfe to change a router (320 to e2000, 610 to e3000) and things go wrong.
What you see is someone that bricked the router and all that needs to be done is to erase nvram and / or kernel but they fire up jtag and erase wholeflash.
you can mess thing up with mtd commands.
This was what I thought but sometime ago Eko created some test firmware for me for a WRTSL54GS and he needed to modify the CFE. It has been quite awhile ago but I don't ever remember replacing the CFE with the 'mtd' commands.
Joined: 26 Jan 2008 Posts: 13049 Location: Behind The Reset Button
Posted: Thu Oct 20, 2011 19:18 Post subject:
Bird333 wrote:
barryware wrote:
Bird333 wrote:
Well I kinda thought that but how are people seemingly messing up their CFE from firmware updates? Also, can you change the way DD-wrt installs to overwrite the CFE?
installing dd-wrt does not, can not, write the cfe space using normal methods (tftp, gui upgrade, etc). I suppose things can get screwed up if someone "experiments" with firmware in a router that is not supported but even then, writing the cfe space really can't happen.
The only time a cfe needs replacing is when the install procedure manipulates the cfe (vxworks bsp to linux cfe, TM, RG, etc.), and replacing a cfe to change a router (320 to e2000, 610 to e3000) and things go wrong.
What you see is someone that bricked the router and all that needs to be done is to erase nvram and / or kernel but they fire up jtag and erase wholeflash.
you can mess thing up with mtd commands.
This was what I thought but sometime ago Eko created some test firmware for me for a WRTSL54GS and he needed to modify the CFE. It has been quite awhile ago but I don't ever remember replacing the CFE with the 'mtd' commands.
All the prep's, killers, cfe updaters do write to the cfe space but were designed to do so.
The thread start out: "Does the CFE get flashed during a normal firmware upgrade?"
Keyword here is normal _________________ [Moderator Deleted]
