Re: [Openocd-development] WORKS!!!! Was: OMAP3 JTAG

[Rick Altherr]

Excellent news! Now someone needs to work on adding support for Cortex-A8. A lot of the base work for dealing with ADIv5 is already done for the Cortex-M3 support. I looked at this in the past and it appeared to be pretty straightforward, but it will still take some time to implement it.

Rick


On Mar 9, 2009, at 1:26 PM, Kees Jongenburger wrote:

Hi Duane and others,

I finally managed to get this thing working (using Duane's patch
therefore ...thanks). The last piece I was missing was something Arnim
Läuger (urjtag) already told
us that the DAP apparently is added before the jcr. I am attaching an
initial working config but it needs more work and needs Duane's patch,
I updated the git and will continue working from there
until we have something decent. Many thanks to many people! specially
Dirk, Duane and Arnim!

you can git clone git://github.com/keesj/openocd-keesj.git


ke...@ijssijs:~$ openocd_client
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Open On-Chip Debugger

jtag tapenable omap3530.cpu

Enabling Cortex-A8 @ OMAP3
Enabling Cortex-A8 @ OMAP3
Cortex-A8 @ OMAP3 enabled
1

irscan omap3530.cpu 0xE

drscan omap3530.cpu 32 0x0

0B6D602F

This is is the idcode of the DAP.

Greetings.
<omap3530.cfg><openocd.cfg>

--
Rick Altherr
kc8...@kc8apf.net


 -- Unsigned

"He said he hadn't had a byte in three days. I had a short, so I split it with him."

smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development