Rick Altherr wrote:
On Dec 19, 2008, at 4:25 AM, Dirk Behme wrote:
Rick Altherr wrote:
On Dec 18, 2008, at 11:55 PM, Dirk Behme wrote:
ke...@ijssijs:~/projects/beagle/openocd$ make
sudo openocd
Open On-Chip Debugger 1.0 (2008-07-04-09:01) svn:738M
$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/
openocd.c $
Info: options.c:50 configuration_output_handler():
jtag_speed: 1, 1
Info: jtag.c:1389 jtag_examine_chain(): JTAG device found:
0x0b7ae02f (Manufacturer: 0x017, Part: 0xb7ae, Version: 0x0)
I can get this far too, but it doesn't make me very excited.
Rick: How do you get this? Do you like to share the details with
people being a little more excited about this? I.e. me ;)
Use the attached .cfg.
Thanks!
Unfortunately, I still get
Error: JTAG communication failure, check connection, JTAG interface,
target power etc.
Error: trying to validate configured JTAG chain anyway...
Error: Error validating JTAG scan chain, IR mismatch, scan returned
0xff
Error: Could not validate JTAG chain, continuing anyway...
See log in attachment.
Maybe there is really an issue with Flyswatter, or I'm doing anything
else totally wrong :(
Best regards
Dirk
Hit the reset button on the BeagleBoard and then start openocd. As my
other experiments show, you only get one shot at getting the ID code.
You also get some odd results for the first scan regardless of type. I
_really_ doubt this has anything to do with the Flyswatter as the code
for the ft2232 interface has not changed in any meaningful way since at
least r1080 or so. As I said, I will validate the Flyswatter against a
LM3S6965 to rule out that possibility. I'm wondering if we are a)
hitting a JTAG clock speed issue, b) not quite following the JRC's
necessary procedure, or c) hitting some odd case in our JTAG state
machine.
Some updates:
* Thanks to Dave, Rick and I got the "TI doc" now.
* I now get
-- cut --
> openocd -s lib/openocd/
Open On-Chip Debugger 1.0 (2008-12-19-17:38) svn:1261
BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS
$URL: svn://svn.berlios.de/openocd/trunk/src/openocd.c $
jtag_speed: 1
Info: JTAG tap: omap3530.jrc tap/device found: 0x0b7ae02f
(Manufacturer: 0x017, Part: 0xb7ae, Version: 0x0)
Info: JTAG Tap/device matched
Warning:no gdb ports allocated as no target has been specified
Warning:no tcl port specified, using default port 6666
-- cut --
This is with Flyswatter, TinCanTools' adapter and BeagleBoard. I think
this shows that recent svn works with Flyswatter :)
For reference, I attach the config files, just in case somebody is
interested. They are identical to what Kees and Rick sent earlier.
* The problem I had was an user error. Plugging Flyswatter, adapter
and Beagle in the wrong way. If you have this configuration, make sure
you use setup as in
http://www.tincantools.com/images/D/Fly%2BBeagle-800x391.JPG?1229714946602
Thanks to Dave for this, too!
* In contrast to picture above, where EMU0/1 jumpers are in 0-1
position, I switched them to 1-2 position. What I understand from
TinCanTools' JTAG adapter schematic 1-2 position (touching J2) is
EMU0/1 high. This is the recommended configuration from TI's document,
too (?)
Ready for next steps, now :)
Best regards
Dirk
#TI OMAP3530 processor - http://www.ti.com
if { [info exists CHIPNAME] } {
set _CHIPNAME $CHIPNAME
} else {
set _CHIPNAME omap3530
}
if { [info exists ENDIAN] } {
set _ENDIAN $ENDIAN
} else {
# this defaults to a little endianness
set _ENDIAN little
}
if { [info exists CPUTAPID ] } {
set _CPUTAPID $CPUTAPID
} else {
# force an error till we get a good number
set _CPUTAPID 0xffffffff
}
#jtag scan chain
jtag newtap $_CHIPNAME jrc -irlen 6 -ircapture 0x1 -irmask 0xf -expected-id
0x0b7ae02f
jtag newtap $_CHIPNAME cpu -irlen 4 -ircapture 0x1 -irmask 0x0 -expected-id
$_CPUTAPID -disable
jtag configure $_CHIPNAME.cpu -event tap-enable {
puts "Enabling CPU"
irscan omap3530.jrc 7
drscan omap3530.jrc 8 0x89
irscan omap3530.jrc 2
drscan omap3530.jrc 32 0x81000080
drscan omap3530.jrc 32 0xa3002048
drscan omap3530.jrc 32 0x81002148
drscan omap3530.jrc 32 0xa3002148
runtest 10
puts "Enabled CPU"
}
#Basic configuration
telnet_port 4444
gdb_port 3333
#Interface
source [find interface/flyswatter.cfg]
#jtag scan chain
#set CHIPNAME beagleboard
#source [find board/beagleboard.cfg]
source [find target/omap3530.cfg]
#disable the dap before we enable it
#jtag tapdisable beagleboard.dap
#proc enable_dap { } {
# puts "Enabling DAP"
# irscan 0 7
# drscan 0 8 0X89
# #irscan 0 2
# #fails..
# #drscan 0 32 0x81000080
# #drscan 0 32 0xa3002048
# #drscan 0 32 0x81002148
# #drscan 0 32 0xa3002148
# #sleep 10
# #jtag tapenable beagleboard.dap
# puts "Enabled DAP"
#}
#reset_config trst_and_srst
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
