I just did a OOCDLink-H cable work with CrossWorks for ARM, Release 2.0.8, using the "Generic FTD2232" target interface. The configurations used was:
OutputPins = "0x0f1b"
Output Value = "0x0c08"
The XML exported by CrossWorks for this target is:
I know that this post is old, but there isn't much information about how to
configure a oocdlink-h with crossworks on the net, so I am posting here in case
someone else needs it.
--- In l..., "M.G." wrote:
> I'm still trying to use OOCDLink JTAG under CrossStudio but without efects.
> I get "Cannot identify target" message. This JTAG works fine with OpenOCD.
> This is OOCDLink JTAG project:
> Schematic: http://tinyurl.com/68qkag
> Channel A
> ADBUS0 -> TCK;
> ADBUS1 -> TDI;
> ADBUS2 -> TDO;
> ADBUS3 -> TMS;
> ADBUS4 ->
> ADBUS5 ->
> ADBUS6 -> 1 if target present
> ADBUS7 -> SRST in;
> ACBUS0 -> TRST buffer enable;
> ACBUS1 -> TRST;
> ACBUS2 -> SRST buffer enable;
> ACBUS3 -> SRST;
> Channel B
> BCBUS2 -> LED
> BCBUS3 -> LED
> In CrossStudio in "Generic FT2232 Device" I have:
> Output Pins 0x0F0F = ADBUS0 - ADBUS3 & ACBUS0 - ACBUS3 ?
> Output Value 0x0000
> nSRST Mask 0x0800 = ACBUS1 ?
> nTRST Mask 0x0200 = ACBUS3 ?
> PID: 0xBAF8
> VID: 0x15BA
> All other are set to 0x0000.
> What about this "ADBUS7 -> SRST in" input pin ?
> JTAG Clock Divider is set to 25, Fast Memory Accesses=No.
> What are the correct settings for this JTAG ?
> How to set mask for led pins on channel B ?