On Wed, Jun 15, 2011 at 11:06 PM, Rodrigo Rosa <rodrigorosa...@gmail.com> wrote:
> i'm not sure i'm getting this right, i think i know very little about
> how this stuff works...
>
> i had modified ft2232.c
> in ft2232_execute_queue, instead of doing layout->blink was using some
> mpsse commands to set/clear read/write gpio pins available on the
> ft2232, which are not used by jtag.

SWD and other transports will use bitbang() and transfer() new
interface methods to work on the bus. queue_flush() / execute_queue()
is jtag only function and should not be used for transports other than
jtag, as it is too jtag-only as it works on commands queued on
CMD_CTX, but these are jtag only.

the idea is to become transport independent, so the context and queue
will be now part of given transport. libswd for instance has swd_ctx
holding all settings and queue, each libswd function works on this
context, so there may be many different contexts in use with no
collisions. this swd_ctx will be hold by void pointer in transport
structure (void so any other context can be used as well).

> i need is some way to type "my_function_in_ft2232.c some_arg" in the
> telnet interface so that the function my_function in ft2232.c gets
> called...
> i managed to make the chip do what i needed without using swd.
> maybe i can get around with some patch on ft2232.c and jtag interface...
>
> how are you testing stuff without the "jtag" command in the cfg files?

target operations are not yet ready. jtag functions are jtag only.
agree there is a mess because i am using some functions or structures
having "jtag" in their name only because some time ago noone
considered other transports than jtag, so instead oocd_interface there
is jtag_interface etc. this must be fixed after transport is
functional, i wanted to rename this stuff before but it took too much
time, so i decided to first make transport working and later
reorganize openocd interals as time is limited...

Best regards! :-)
Tomek

btw. maybe automatically executing autoreconf for libswd submodule
will fix the problem you mentioned.. i have created configure script
to avoid this, but there seems to be someissues with that.. will have
to take closer look :-)

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to