will tincan "flyswatter" JTAG be upward compatible to A8?

i can read here:

http://elinux.org/BeagleBoardOpenOCD

that, at the moment, openocd has only "basic" support for OMAP3 but
not yet Cortex A8. i'm assuming this is true but can i assume that,
if i buy the flyswatter and beagleboard adapter kit from here:

http://tincantools.com/product.php?productid=16134&cat=0&page=1

that HW will still apply when A8 support is added to openocd? thanks.

rday

Robert,

Robert P. J. Day wrote:

  i can read here:

BeagleBoardOpenOCD - eLinux.org

that, at the moment, openocd has only "basic" support for OMAP3 but
not yet Cortex A8. i'm assuming this is true

Yes, it is :wink:

There's actually some discussion how to add Cortex A8 support to OpenOCD

but unfortunately not a lot progress (?).

but can i assume that,
if i buy the flyswatter and beagleboard adapter kit from here:

http://tincantools.com/product.php?productid=16134&cat=0&page=1

that HW will still apply when A8 support is added to openocd? thanks.

I'm not sure I got your question right. You want to know if Flyswatter will still work with OpenOCD & Beagle when OpenOCD supports Cortex A8?

Note that Flyswatter is HW only, while OpenOCD is SW (and Cortex A8 support is SW, too). Having Cortex A8 support (i.e. OpenOCD knows how to deal with Cortex A8 JTAG/debug registers etc.) in OpenOCD is the *requirement* for (GDB) debugging via Flyswatter.

That is, Cortex A8 support in OpenOCD is *necessary* to use Flyswatter (for GDB debugging). Thus, the answer to your question (if I got it right) is: Yes.

Dirk

Btw.: If somebody likes/is able to help with adding Cortex A8 support to OpenOCD, this would be greatly appreciated!

i realized the difference between the SW and HW aspects of the
above, i just wanted to verify that adding the (eventual?) openocd SW
support for cortex A8 wouldn't require some sort of HW mod.

rday

Btw.: If somebody likes/is able to help with adding Cortex A8 support
to OpenOCD, this would be greatly appreciated!

Hi Dirk,

I might have a little time and find this topic very interesting. I would
therefore like to hear a little about what it takes to help OpenOCD forward.
I have basic knowledge of JTAG and the OMAP-emulation-system in general.
Furthermore I have access to a working CCS JTAG setup, which might show
useful as well :slight_smile:

I however have absolutely no knowledge about OpenOCD and very little about
GDB...

In case you can match this with what you need to get going in anyway, please
let me know, and let's see if we can find a way forward...

Best regards
  Søren

Søren,

Søren Steen Christensen wrote:

Btw.: If somebody likes/is able to help with adding Cortex A8 support
to OpenOCD, this would be greatly appreciated!

Hi Dirk,

I might have a little time and find this topic very interesting. I would
therefore like to hear a little about what it takes to help OpenOCD forward.
I have basic knowledge of JTAG and the OMAP-emulation-system in general.
Furthermore I have access to a working CCS JTAG setup, which might show
useful as well :slight_smile:

I however have absolutely no knowledge about OpenOCD and very little about
GDB...

Same here :wink:

General good starting point could be

http://elinux.org/BeagleBoardOpenOCD

As mentioned there, we already can access "ARM JTAG device" and now have to 'teach' OpenOCD how to deal with Cortex A8 JTAG (registers?).

OpenOCD already supports Cortex M3. It's my understanding that we need now something similar for Cortex A8 like

http://svn.berlios.de/svnroot/repos/openocd/trunk/src/target/cortex_m3.c

Next step would be to have look to

and try to understand it :wink:

In case you can match this with what you need to get going in anyway, please
let me know, and let's see if we can find a way forward...

Have a look to above and see if you can get an idea what's needed.

Many thanks!

Dirk

Dirk Behme wrote:

Søren,

Søren Steen Christensen wrote:

Btw.: If somebody likes/is able to help with adding Cortex A8 support
to OpenOCD, this would be greatly appreciated!

Hi Dirk,

I might have a little time and find this topic very interesting. I would
therefore like to hear a little about what it takes to help OpenOCD forward.
I have basic knowledge of JTAG and the OMAP-emulation-system in general.
Furthermore I have access to a working CCS JTAG setup, which might show
useful as well :slight_smile:

I however have absolutely no knowledge about OpenOCD and very little about
GDB...

Same here :wink:

General good starting point could be

BeagleBoardOpenOCD - eLinux.org

As mentioned there, we already can access "ARM JTAG device" and now have to 'teach' OpenOCD how to deal with Cortex A8 JTAG (registers?).

OpenOCD already supports Cortex M3. It's my understanding that we need now something similar for Cortex A8 like

http://svn.berlios.de/svnroot/repos/openocd/trunk/src/target/cortex_m3.c

Next step would be to have look to

https://lists.berlios.de/pipermail/openocd-development/2009-March/005097.html OpenOCD - Open On-Chip Debugger - berlios.de OpenOCD - Open On-Chip Debugger - berlios.de

and try to understand it :wink:

In case you can match this with what you need to get going in anyway, please
let me know, and let's see if we can find a way forward...

Have a look to above and see if you can get an idea what's needed.

Just fyi: At OpenOCD mailing list Rick Altherr wrote a nice intro how to help with Cortex A8 support for OpenOCD. I tried to summarize it in

http://elinux.org/BeagleBoardOpenOCD#Cortex_A8_support

Best regards

Dirk

FWIW, the documents that require you to be a "registered ARM customer" just mean you need to create an account usually. I don't believe you need to work for any specific company or have any real agreement with ARM.