On Tue, Dec 2, 2008 at 1:33 AM, Duane Ellis <[EMAIL PROTECTED]> wrote:
> Kees Jongenburger wrote:
>>
>> This patch provides an initial beaglebloard.cfg file up for
>> inclusion/review.
>>
>
> 1) Please review the new documentation.
>
> http://openocd.berlios.de/doc/Config-File-Guidelines.html
Hi I added some comments here:
http://box.mmapps.net/sb/Config_File_Guidelines_-_Open_On-Chip_Debugger_(OpenOCD)-1/index.html
Overall I find the syntax a little challenging. it looks like tcl is
not making everything as easy
as hoped.
> 2) In the "beagleboard.cfg"
>
> These should read:
>
> jtag newtap $_CHIPNAME jrc -irlen 6 -ircapture 0x01 -irmask 0x0
> jtag newtap $_CHIPNAME dap -irlen 4 -ircapture 0x01 -irmask 0x0
Updated see new patch.
that I use with this configuration
#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
#this code needs to more somewhere else
jtag tapdisable beagleboard.dap
#also needs moving to the board?
reset_config trst_and_srst
>
> So where is the CPU?
> Where is the ETB tap?
> Where is the DSP tap?
> Are there not more taps?
There will be the DSP but I don't think the CPU and ETB will be separate TAPs
but that is the next step :p
Index: src/target/board/beagleboard.cfg
===================================================================
--- src/target/board/beagleboard.cfg (revision 0)
+++ src/target/board/beagleboard.cfg (revision 0)
@@ -0,0 +1,49 @@
+#
+# 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
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
