JTAG - anyone get it to work fully? (technical discussion)

root@ubuntu:/usr/local/share/openocd/scripts# openocd -f interface/parport_dlc5.cfg -f board/azbox.cfg
Open On-Chip Debugger 0.4.0 (2011-03-13-12:05)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
parport port = 0x0
jtag_nsrst_delay: 100
jtag_ntrst_delay: 100
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
Warn : smp8634.cpu: nonstandard IR mask
Warn : use 'smp8634.cpu' as target identifier, not '0'
Info : clock speed 500 kHz
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Command handler execution failed
Warn : jtag initialization failed; try 'jtag init' again.

wath is probem???
please help me!!

Quote:

---

Originally Posted by happyhammer

i have an azbox premium stuck on booting, serial port shows only this:

xosPe0 serial#fb6660ccb1914db3d671f1ff6e 9b0713 subid 0x50
xenv cs2


Now, i finally managed to get the JTAG working on this premium, see attached diagram, i used the second one as this premiun has no resistor packs, seven pullup resistors go to 3.3v one pulldown goes to gnd( shown as a ? in diagram).

After succesfully reflashing which took 28 hours to do, the same bloody thing, stuck on booting with "xenv CS2". I really thought that reflashing would cure this.

Has anyone suggestions how i can proceed? I used the instructions and cfe.bin file from a russian web site. I'm hoping there is maybe another file i can flash to get this box recovered, i read somewhere about getting a YAMON loaded without xenv and reset?


So if anyone knows why the box is not getting past the "xenv cs2" bit, i'd appreciate it.








==============
procedure:

1 -Open a terminal and create a new folder named azbox:
mkdir azbox
cd azbox
sudo apt-get install libftdi-dev libftdi1 libusb-dev
-Download the file ===> http://www.4shared.com/file/a6Wz4Bc5...-azboxtar.html
tar xjvf openocd-0.4.0-azbox.tar.bz2
cd openocd-0.4.0-azbox/
./configure --enable-dummy --enable-parport --enable-parport_ppdev --enable-amtjtagaccel --enable-verbose
make
sudo make install
sudo ln sf /usr/local/bin/openocd /usr/bin/openocd
sudo cp smp8634.cfg /usr/local/share/openocd/scripts/target/smp8634.cfg
sudo cp azbox.cfg /usr/local/share/openocd/scripts/board/azbox.cfg
################################# ##############################
-2 UNPROTECT BIOS BEFORE YOU WRITE WITH tjtag
################################# ##############################
sudo rmmod lp
cd /usr/local/share/openocd/scripts
sudo openocd -f interface/parport_dlc5.cfg -f board/azbox.cfg
Open a new terminal and type:
sudo telnet localhost 4444
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Open On-Chip Debugger
>halt
>reset
>reset init
>flash protect 0 0 last off
>flash protect_check 0
>flash info 0
>shutdown
-3 Flash is ready to use the now unprotected tjtag to flash the bios.
sudo ./tjtag -flash:cfe /fc:104 /bypass

=============

final output lines from flashing log:


.
.
[ 99% Flashed] ac7fffb0: ffffffff ffffffff ffffffff ffffffff
[ 99% Flashed] ac7fffc0: ffffffff ffffffff ffffffff ffffffff
[ 99% Flashed] ac7fffd0: ffffffff ffffffff ffffffff ffffffff
[ 99% Flashed] ac7fffe0: ffffffff ffffffff ffffffff ffffffff
[ 99% Flashed] ac7ffff0: ffffffff ffffffff ffffffff ffffffff
Done (CFE.BIN loaded into Flash Memory OK)

=========================
Flashing Routine Complete
=========================
elapsed time: 103053 seconds


*** REQUESTED OPERATION IS COMPLETE ***

---

please tell me,you are put RP1 and RP2 in azbox??100 ohm???

RP1 and RP2 are resistor packs. I did not have these parts and only an ordinary soldering iron which is very difficult ti use on surface mounted boards. You do this at your own risk as its very easy to damage tracks/pads etc.

all but one of the 100 ohm resisters go between the Jtag pads and the 3.3v, the other goes to GND. Then the connections from the PC parallel port to the Jtag pads. just as in diagram.

The Jtag must also be enabled by jumper.

please put the picture with your jtag please,with specification,becouse i dont understand scheme 2 in diagram!!
thnx in advance!!

i put 2.2k resistors from rp1 and rp2 becouse dont have 103,(10k)im sure this is corect value10k!!!!!,but i try with this...
message from console 1


root@ubuntu:~# cd /usr/local/share/openocd/scripts
root@ubuntu:/usr/local/share/openocd/scripts# sudo openocd -f interface/parport_dlc5.cfg -f board/azbox.cfg
Open On-Chip Debugger 0.4.0 (2011-03-15-11:33)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
parport port = 0x0
jtag_nsrst_delay: 100
jtag_ntrst_delay: 100
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
Warn : smp8634.cpu: nonstandard IR mask
Warn : use 'smp8634.cpu' as target identifier, not '0'
Info : clock speed 500 kHz
Info : JTAG tap: smp8634.cpu tap/device found: 0x08630001 (mfg: 0x000, part: 0x8630, ver: 0x0)
Info : accepting 'telnet' connection from 0
Info : Halt timed out, wake up GDB.
Error: timed out while waiting for target halted
Command handler execution failed
Info : JTAG tap: smp8634.cpu tap/device found: 0x08630001 (mfg: 0x000, part: 0x8630, ver: 0x0)
Info : JTAG tap: smp8634.cpu tap/device found: 0x08630001 (mfg: 0x000, part: 0x8630, ver: 0x0)
Info : Halt timed out, wake up GDB.
Error: timed out while waiting for target halted
TARGET: smp8634.cpu - Not halted
Command handler execution failed
Error: Target not halted
Error: auto_probe failed -304

Error: Target not halted
Error: auto_probe failed -304

flash bank '0' not found
Command handler execution failed
Error: Target not halted
Command handler execution failed


message from console 2!


root@ubuntu:~# cd /usr/local/share/openocd/scripts
root@ubuntu:/usr/local/share/openocd/scripts# sudo telnet localhost 4444Trying ::1...
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Open On-Chip Debugger
> halt
Halt timed out, wake up GDB.
timed out while waiting for target halted
Command handler execution failed
in procedure 'halt' called at file "command.c", line 650
called at file "command.c", line 361
> reset
JTAG tap: smp8634.cpu tap/device found: 0x08630001 (mfg: 0x000, part: 0x8630, ver: 0x0)
> reset init
JTAG tap: smp8634.cpu tap/device found: 0x08630001 (mfg: 0x000, part: 0x8630, ver: 0x0)
Halt timed out, wake up GDB.
timed out while waiting for target halted
TARGET: smp8634.cpu - Not halted
Command handler execution failed
in procedure 'reset' called at file "command.c", line 650
called at file "command.c", line 361
> flash protect 0 0 last off
Target not halted
auto_probe failed -304

> flash protect_check 0
Target not halted
auto_probe failed -304

flash bank '0' not found
flash protect_check bank_id
Command handler execution failed
in procedure 'flash' called at file "command.c", line 650
called at file "command.c", line 361
> flash info 0
Target not halted
Command handler execution failed
in procedure 'flash' called at file "command.c", line 650
called at file "command.c", line 361
>


im sure put the corect resistors RP! & RP2,WORK!!!

Where Can I obtain the JTAG instructions?

I need a copy to try same.

Please Help

Thanks

http://www.pristavka.de/index.php?topic=6061.0

can opensat do jtag if you send them box to be repaired ?

how much do they charge out of warranty ?

sorry for opening an old thread

But has anybody got a wiring / pin diagram for a jtag cable for the cuberevo / ipbox, i have looked everywhere so hopefully someone can help

I've saw, that only happyhammer, on whole internet wide were had same problem with me.
I have my device stuck on booting with message:

Code:

---

xosPe0 serial#a8e6... subid 0x50
xenv cs2 xosPe0 serial#a8e6... subid 0x50
xenv cs2

---

Nither ok nor failed.

I've tried to use jtag. I was able to connect but now I'm stuck with putting processor to halt.

Please, tell me, were you able to resolve this issue, because from forum posts it is not clear.

hi every body, i have azbox elite and it dont want to connect to jtag ,i used the jtag schema from this topic jumper enabled but openocd tell jtag not found . please help..:confused:

Quote:

---

Originally Posted by nano3000

hi every body, i have azbox elite and it dont want to connect to jtag ,i used the jtag schema from this topic jumper enabled but openocd tell jtag not found . please help..:confused:

---

Check your connection (wiring) more precise, and be sure, that you are running openocd with corret params.

hi ,thanks for your response,epp+ecp enabled in the bios but i have this:

root@debian:/usr/local/share/openocd/scripts# openocd -f interface/parport_dlc5.cfg -f board/azbox.cfg
Open On-Chip Debugger 0.4.0 (2013-08-19-06:37)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
Error: The specified JTAG interface was not found (parport)
The following JTAG interfaces are available:
Command handler execution failed

Quote:

---

Originally Posted by nano3000

hi ,thanks for your response,epp+ecp enabled in the bios but i have this:

root@debian:/usr/local/share/openocd/scripts# openocd -f interface/parport_dlc5.cfg -f board/azbox.cfg
Open On-Chip Debugger 0.4.0 (2013-08-19-06:37)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
Error: The specified JTAG interface was not found (parport)
The following JTAG interfaces are available:
Command handler execution failed

---

It looks like, openocd unable to find parport on your unix system.
Try this:
1. rmmod lp
Run openocd again, if it does not help, please, check that you have /dev/parport0, or anything else with ls /dev/parport*

thanks for your response
root@debian:/usr/local/share/openocd# rmmod lp
ERROR: Module lp does not exist in /proc/modules
root@debian:/usr/local/share/openocd# ls /dev/parport*
ls: impossible d'accéder Ã* /dev/parport*: Aucun fichier ou dossier de ce type

please what can i do now?

What linux distro do you have (uname -a), what PC do you have (particulary motherboard).
Now you should google, why parport device did not initialized on your PC

i'm on debian the following command lsmod |grep parport show this:
root@debian:#lsmod |grep parport
parport_pc 15799 0
parport 22554 1 parport_pc

and
root@debian:#ls /proc/sys/dev/parport
default parport0
i think it's a bug of udev !!

Quote:

---

Originally Posted by nano3000

i'm on debian the following command lsmod |grep parport show this:
root@debian:#lsmod |grep parport
parport_pc 15799 0
parport 22554 1 parport_pc

and
root@debian:#ls /proc/sys/dev/parport
default parport0
i think it's a bug of udev !!

---

Maybe, but I think, this is a little bit out of this discussion thread. If you need help with linux I cat try to help you out of there. (knock to my PM, if you won't be able to deal with it yourself)

Quote:

---

Originally Posted by zingfrid

Maybe, but I think, this is a little bit out of this discussion thread. If you need help with linux I cat try to help you out of there. (knock to my PM, if you won't be able to deal with it yourself)

---

if you have an elite model, forget JTAG, unless someone has some new information, it seems that
the JTAG interface has been disabled during manufacture despite a header being available on this model. if you have a premium model, you can use USBJTAG device. i bought one to see if it would work with elite model but it dont work.

Quote:

---

Originally Posted by happyhammer

if you have an elite model, forget JTAG, unless someone has some new information, it seems that
the JTAG interface has been disabled during manufacture despite a header being available on this model. if you have a premium model, you can use USBJTAG device. i bought one to see if it would work with elite model but it dont work.

---

Hello, happyhammer, glad to see you here. Can you please take a look on my message: post