I'd like to reproduce recent OpenOCD status with Beagleboard (and then
maybe help/test?):
I use OpenOCD svn version 1245 from yesterday with openocd.cfg and
beagleboard.cfg in attachment (mainly from [1]). I use libFTDI and
Flyswatter with TinCanTools Beagleboard adapter kit. BeagleBoard runs
at U-Boot prompt (serial console via Flyswatter), then I do
-- cut --
> openocd -s lib/openocd/
Open On-Chip Debugger 1.0 (2008-12-16-07:54) svn:1245
BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS
$URL: svn://svn.berlios.de/openocd/trunk/src/openocd.c $
jtag_speed: 1
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...
Warning:no gdb ports allocated as no target has been specified
Warning:no tcl port specified, using default port 6666
-- cut --
At TinCanTools's JTAG adapter which is connected to the JTAG connector
of BeagleBoard, jumper EMU0 and EMU1 are at 2-3 location, JP3 is open.
Is this what you get, too?
Best regards
Dirk
[1]
https://lists.berlios.de/pipermail/openocd-development/2008-December/003838.html
#
# Beagle Board is an ultra-low cost, high performance,
# low power OMAP3 based platform designed by BeagleBoard.org
# community members and sold by Digi-Key.
#
# The OpenOCD BeagleBoard support in under development and not functional
# yet
#By default the BeagleBoard name as used in the rest of the configuration
#if BeagleBoard unless specified otherwise
if { [info exists CHIPNAME] } {
set _CHIPNAME $CHIPNAME
} else {
set _CHIPNAME beagleboard
}
#BeagleBoard scan chain.
#
# JRC or JTAG Router Controler is the piece hardware that can dynamically
# add or remove Test access points to a JTAG scan chain.
#
# Texas Instruments calls this feature ICEPick. ICEPick can be seen as
# Controller with can not only enable and disable parts of the scan chain
# but apparently also other things (like reading the emu status bits?).
#
# JTAG
#
# TDO | | TDI
# | |
# -----|------------|---------------
# | | | |
# | | (Bypass)-IcePickTAP |
# | | | |
# | (Bypass)-----(Bypass) |
# ----------------------------------
# | |
# | |
# CoreSight DSP
#
#The first item is the IcePick TAP itself is has a known tap id.
#The IcePick can control up to 16 TAPs.
#The Second item in the scan chain on the beagleboard the dap providing direct
#access to memory, the cortex8, the etm and the etb. This item is not enabled
#By default and is attached to the third TAP on the IcePick. This is not visible
#here but needs to be known in order to send the right enable/disable command
#to the IcePick controller
jtag newtap $_CHIPNAME jrc -irlen 6 -ircapture 0x1 -irmask 0x0 -expected-id
0x0b7ae02f
jtag newtap $_CHIPNAME dap -irlen 4 -ircapture 0x1 -irmask 0x0
#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]
#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
