Øyvind Harboe wrote:
>> Some developers are working on OpenOCD support for Beagle/OMAP35xx
>> using Flyswatter. As far as I know, the main issue is that OpenOCD
>> doesn't support the "new" JTAG architecture of OMAP35xx at the moment.
>> I.e. you first have to add DAP to the TAP router, via a programming
>> sequence, then ARM core can be accessed.
>>
>
> Can you post some details on this to this mailing list?
>
> The last time this was discussed in openocd development mailing list
> there was various other issues that had to be addressed that got
> in the way... (reset as I recall)... but that should be sorted now.
>
>
Yes, I asked about it a while ago - but - people where busy with a few
other things.
As I recall:
A) There are multiple jtag taps in the OMAP chip.
B) They are *not* chained together in the standard jtag way.
C) Instead, there is a sort of "master jtag tap" - or "tap router" using
TI's name, is part of their "ice-pick"
It basically dynamically adds & removes jtag taps from the chain.
Instead of putting them in "bypass mode"
The beagle wiki page:
http://elinux.org/BeagleBoardJTAG
References this TI Link, which explains *alot* of background about why
it is so weird.
http://focus.ti.com/lit/ml/sprp603/sprp603.pdf
Slides 5/6/7 - seems to be the *main* justification and problem
explanation.
I believe - that is the problem that must be addressed.
This make sense - because the BEAGLE board chip - is actually a multi
die chip (ie: cpu + sdram + nand flash buit in to one package, not to
mention the funny other stuff on the omap cpu)
-Duane.
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
