I made CFE backup, when uploaded another CFE found on the net, it didn't work so I successfully restored my backuped CFE, everything was alright. But after it I flashed another CFE, it didn't work and now I'm unable to flash back my backuped CFE!
it just freezes:
Just wondering if anyone has had luck de-bricking a WRT160NL (shagged cfe through about .5 seconds of stupidity) with TJTAG?
I connected it up with a dlc5 and TJTAG detects the cpu as an Atheros 531X (cpu is an Atheros 9130 but TJTAG has no support for those), it seems to reset the cpu and enables the mem ok, but wont probe the flash (I assume because it is the wrong cpu and it's not setting up the mem correctly when it says it is). If I force the flash with /fc:22 (flash is an MX25L6405 which is supported) it will continue and write the image successfully, but then hangs on "resuming processor" and powering off and back on still gives me the "flashing light of death". I tried with both /dma and /nodma but the end result is the same.
I obtained the image of the CFE from a working WRT160NL that is running openwrt by doing a "dd if=/dev/mtd0 of=AR-CFE.BIN". I read somewhere that the file endianess needs to be swapped when flashing a file obtained with the dd command and found a utility on here that apparently did this, but still haven't had any luck using the normal version or the byte swapped version.
Has anyone got some suggestions to try or am I wasting my time using 531X configuration with a 9130?
There is currently no support for writing a serial flash chip in AR7xxx/AR9xxx based routers. _________________ Kernel panic: Aiee, killing interrupt handler!
None that I am aware of except for very expensive professional solutions.
There is no useful information in that opinion piece of yours, it is only a personal attack.
You'd better stop if you want to remain a poster on this board. _________________ Kernel panic: Aiee, killing interrupt handler!
I am just telling the truth and if you want this board to be productive, please stop your negative comments. At least show some positive side to the people interested in dd-wrt.
LOM wrote:
lijianch wrote:
I notice most of your replies are negative.
LOM wrote:
None that I am aware of except for very expensive professional solutions.
There is no useful information in that opinion piece of yours, it is only a personal attack.
You'd better stop if you want to remain a poster on this board.
He's just stating a fact you know. Basically, whoever needs jtag for any newer unit is screwed.
Since it looks like Tornado just vanished into thin air, I hardly see what's so positive about that.
He's just stating a fact you know. Basically, whoever needs jtag for any newer unit is screwed.
Yes, but lijianch rather see users wasting a day on coming to that conclusion than I telling them so they can use their time on other things.
BlCa` wrote:
Since it looks like Tornado just vanished into thin air, I hardly see what's so positive about that.
Nah, he hasn't vanished but is very busy with work.
A binary only pre-release of tjtag 3.02 should come any day now.
I will try to write an AR7/AR9 serial flash driver for tjtag in the autumn but it is quite a big job which I need both time and some additional hardware for. _________________ Kernel panic: Aiee, killing interrupt handler!
When I posted the picture of Westell 7501 PCB, you insisted that it was a DSL combo and would never be supported. Later you corrected your negative comments because you were wrong.
Nevertheless, you did continue to deny the Jtag program will work on this unit until Az1234 posted a slightly revised but working Jtag binary and report a success.
I think a better way to "provide advise" is to offer a constructive suggestion or possible ways to put efforts. Your style will simply scare some users away.
LOM wrote:
BlCa` wrote:
He's just stating a fact you know. Basically, whoever needs jtag for any newer unit is screwed.
Yes, but lijianch rather see users wasting a day on coming to that conclusion than I telling them so they can use their time on other things.
BlCa` wrote:
Since it looks like Tornado just vanished into thin air, I hardly see what's so positive about that.
Nah, he hasn't vanished but is very busy with work.
A binary only pre-release of tjtag 3.02 should come any day now.
I will try to write an AR7/AR9 serial flash driver for tjtag in the autumn but it is quite a big job which I need both time and some additional hardware for.
Joined: 26 Jan 2008 Posts: 13049 Location: Behind The Reset Button
Posted: Tue Jun 22, 2010 18:37 Post subject:
BlCa` wrote:
He's just stating a fact you know. Basically, whoever needs jtag for any newer unit is screwed.
Since it looks like Tornado just vanished into thin air, I hardly see what's so positive about that.
I could be incorrect but tmk, I don't think T~ has had one router sent to him excluding a "hand-me-down" or two from Eko once he has finished with it. Dunno for sure.. Grape vine...
I have worked with T~ as have others.. It takes hours & hours, days & days trying to add support by remote control. Meaning he writes the code, and someone does the testing.
If he had the router, he could add support in a weekend if he is so inclined.
Soooo.. Start supporting Tornado with routers that need jtag support or contributions. _________________ [Moderator Deleted]
Nevertheless, you did continue to deny the Jtag program will work on this unit until Az1234 posted a slightly revised but working Jtag binary and report a success.
Boy you are more than dumb, you are dishonest as well.
I did help az1234 with info both in the forum and in a couple of pm's and he patched tjtag so it could do a simple chain read on this particular device only.
I've never denied that it could work, here is what I wrote:
"I can't see Tornado rewriting tjtag for chained devices, it is a too big work especially when not having a router to test on. (see my previous post where I suggested that a router should be donated to Tornado)"
You'd better stop stalking me now or your posting rights in the forum will be removed.
This is your second and last warning. _________________ Kernel panic: Aiee, killing interrupt handler!
Last edited by LOM on Wed Jun 23, 2010 2:24; edited 1 time in total
Thank for showing your rage. Being a forum moderator and blocking poster does not make you wise.
LOM wrote:
lijianch wrote:
Nevertheless, you did continue to deny the Jtag program will work on this unit until Az1234 posted a slightly revised but working Jtag binary and report a success.
Boy you are more than dumb, you are dishonest as well.
I did help az1234 with info both in the forum and in a couple of pm's and he patched tjtag so it could do a simple chain read on this particular device only.
I've never denied that it could work, here is what I wrote:
"I can't see Tornado rewriting tjtag for chained devices, it is a too big work especially when not having a router to test on. (see my previous post where I suggested that a router should be donated to Tornado)"
You'd better stop stalking me now or your posting rights in the forum will be removed.
This is your second and last warning.