If tjtag had worked in 8-bit mode then you would have used backup:AR-RED where AR-RED is predefined to start at 0xA8000000 and the length is predefined to be 0x30000.
brjtag hasn't got any Atheros support, AR-RED is not defined so you have to do a backup:custom.bin and then supply the startaddress and length, ie /start:A8000000 /length:30000
tjtag has the AR-WHOLEFLASH definition and in brjtag you will again need to do a backup:custom.bin but with the parameters /start:A8000000 /length:100000
The /window switch is only for probing, erasing, and writing flash and is not needed for reading when you override the flash detection with /fc:003.
It is possible that you can read without the /Wx8 switch but you can definitely not successfully probe,erase, or write without it. _________________ Kernel panic: Aiee, killing interrupt handler!
If tjtag doesn´t recognize the cpu, it will be hard to get something. You could try with other softwares or take a look in the livebox dedicated forums to see if they have developed some tool to access it.
Joined: 24 Jan 2009 Posts: 40 Location: Sorocaba, Sao Paulo, Brazil
Posted: Mon Oct 03, 2011 2:24 Post subject:
I'm trying to debrick a Dir-300A1 via JTAG with a cable and TJTAG3 after an unsuccessful attempt to update the Redboot and the firmware (no ethernet, only power led is on) but is returning the following error message:
"Unknown or NO Flash Chip Detected"
The flash chip is a Promos Flash V54C3128164VBI7 (http://www.promos.com.tw/website/html/english/product/V54/V54C3128804VB%28Ind.%29.pdf).
Is there another option that is compatible with this flash chip or something that can be done?
If tjtag doesn´t recognize the cpu, it will be hard to get something. You could try with other softwares or take a look in the livebox dedicated forums to see if they have developed some tool to access it.
Hi, thanks for the reply.
This link is valid to Livebox1 with Broadcom CPU, but Livebox2 have a Ikanos CPU.
With brjtag the output of readings is BAD SET ADDRESS.
On this board TDO is not conected to CPU, I put one 0 ohms resistor to have direct contact with the CPU.
I orderer tornado´s favourite jtag adaptor to test.
I'm trying to debrick a Dir-300A1 via JTAG with a cable and TJTAG3 after an unsuccessful attempt to update the Redboot and the firmware (no ethernet, only power led is on) but is returning the following error message:
"Unknown or NO Flash Chip Detected"
The flash chip is a Promos Flash V54C3128164VBI7 (http://www.promos.com.tw/website/html/english/product/V54/V54C3128804VB%28Ind.%29.pdf).
Is there another option that is compatible with this flash chip or something that can be done?
Thank´s
That is not the flash, that chip is the RAM. The flash is the smaller chip, to the right of the frontal leds.
Do you have a serial console connected to it ? What does it show ?
If tjtag doesn´t recognize the cpu, it will be hard to get something. You could try with other softwares or take a look in the livebox dedicated forums to see if they have developed some tool to access it.
Hi, thanks for the reply.
This link is valid to Livebox1 with Broadcom CPU, but Livebox2 have a Ikanos CPU.
With brjtag the output of readings is BAD SET ADDRESS.
On this board TDO is not conected to CPU, I put one 0 ohms resistor to have direct contact with the CPU.
I orderer tornado´s favourite jtag adaptor to test.
Greetings.
Ok, I did not pay much attention to that link. What I meant was if you had a serial console connected to it, and what was the output in it ?
Joined: 24 Jan 2009 Posts: 40 Location: Sorocaba, Sao Paulo, Brazil
Posted: Tue Oct 04, 2011 1:42 Post subject:
RogFanther wrote:
That is not the flash, that chip is the RAM. The flash is the smaller chip, to the right of the frontal leds.
Do you have a serial console connected to it ? What does it show ?
Oh sorry. Is 25x32VF18.
Serial Console is dead too.
If tjtag doesn´t recognize the cpu, it will be hard to get something. You could try with other softwares or take a look in the livebox dedicated forums to see if they have developed some tool to access it.
Hi, thanks for the reply.
This link is valid to Livebox1 with Broadcom CPU, but Livebox2 have a Ikanos CPU.
With brjtag the output of readings is BAD SET ADDRESS.
On this board TDO is not conected to CPU, I put one 0 ohms resistor to have direct contact with the CPU.
I orderer tornado´s favourite jtag adaptor to test.
Greetings.
Ok, I did not pay much attention to that link. What I meant was if you had a serial console connected to it, and what was the output in it ?
Hi rogFanther.
No response over serial console, Im waiting the tiao bufferef universal jtag.
Do you know if TDO need one 0 ohms resistos or 32 ohms over 2.6 mips specifications?
Don´t know if the resistance needs to be an exact value. In the few cases I had to bridge pads to make jtag work, I used 0 ohm resistores and all was fine.
But I don´t believe your problem to be in the jtag adapter. TJTAG recognizes and works with a defined set of processors. Your appliance seems to use another, unrecognized one, and thus the software will have problem controlling it and the flash.
What are the results if you run tjtag with the /flash_debug option ? ( consult the exact wording in the program help ) . ( also, without the /fc: parameter . We are interested in what tjtag is detecting as flash ) .
In your original post, I believe to see kind of a misunderstanding. When you use the /fc: parameter, the messages say that the user manually selected that flash type, it doesn´t mean that tjtag recognized the chip ( maybe you already know it, but as you wrote
"Now recognize fine the flash.", I found it good to remember ) .
Try to get the results for /flash_debug and post them here.
Don´t know if the resistance needs to be an exact value. In the few cases I had to bridge pads to make jtag work, I used 0 ohm resistores and all was fine.
But I don´t believe your problem to be in the jtag adapter. TJTAG recognizes and works with a defined set of processors. Your appliance seems to use another, unrecognized one, and thus the software will have problem controlling it and the flash.
What are the results if you run tjtag with the /flash_debug option ? ( consult the exact wording in the program help ) . ( also, without the /fc: parameter . We are interested in what tjtag is detecting as flash ) .
In your original post, I believe to see kind of a misunderstanding. When you use the /fc: parameter, the messages say that the user manually selected that flash type, it doesn´t mean that tjtag recognized the chip ( maybe you already know it, but as you wrote
"Now recognize fine the flash.", I found it good to remember ) .
Try to get the results for /flash_debug and post them here.
You are right, this soft not can recognize the flash.
Mensajes: 4034
Ver Perfil Email Mensaje Privado (Conectado)
xxx
« : Ayer a las 08:49:20 » Responder con cita Modificar mensaje Eliminar mensaje Dividir Tema
D:\tjtaglast\Windows32>tjtag3 -probeonly /skipdetect /nocwd /flash_debug
You are right, this soft not can recognize the flash.
Jtag is a cpu interface and all operations on the memory bus(es) is done with help of the cpu.
If your jtag software don't have support for the cpu, then you will never be able to read or write the flash. _________________ Kernel panic: Aiee, killing interrupt handler!
The normal interfaces, discussed here in the forums, that are supported by tjtag, are supported by urjtag. I used the same "arachno-cable" with tjtag in a thomsom router with tjtag, and in a G700AP, with urjtag.
Make a buffered one, to reduce interference/problems.