See the updated thread:
http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/298735.aspx
On Tue, Oct 29, 2013 at 7:27 PM, Andreas Fritiofson <
[email protected]> wrote:
>
> On Tue, Oct 29, 2013 at 5:39 PM, Laszlo Papp <[email protected]> wrote:
>
>> On Tue, Oct 29, 2013 at 4:30 PM, Laszlo Papp <[email protected]> wrote:
>>
>>> On Tue, Oct 29, 2013 at 4:24 PM, Spencer Oliver <[email protected]>wrote:
>>>
>>>> On 29 October 2013 15:48, Laszlo Papp <[email protected]> wrote:
>>>> >
>>>> >
>>>> > We use 14-pin XDS100V2 adapters. Our header is also designed for
>>>> 14-pin.
>>>> >
>>>>
>>>> ah ok, thought the xds100v2 had both connectors - 14 and 20 way.
>>>>
>>>> According to the schematic srst comes out of the cpld pin 21 (vis
>>>> R21), can you not connect here?
>>>>
>>>> http://software-dl.ti.com/dsps/dsps_registered_sw/sdo_ccstudio/XDS/XDS100v2Schematic(rev2)-Setup.zip
>>>
>>>
>>> Could I configure openocd to use that pin for the jtag SRST pin?
>>>
>>
>> Also, that would mean to hack every vendor jtag adapter from TI. I am not
>> sure I am fond of that idea. Perhaps, using watchdog or a different
>> mechanism like serial flasher is a more reliable way with this scenario?
>>
>>
> I haven't looked at the schematics (registration needed and I didn't
> bother) but according to the interface configuration file
> (interface/ftdi/xds100v2.cfg) it has a bunch of extra signals, among those
> are SRST and EMU0/1. Are you saying that the SRST isn't routed to the
> connector because it has no position in the 14-pin TI layout? Then which
> pin did you have in mind to use for reset? OpenOCD can control all FTDI
> pins in arbitrary ways[1], so if you can dedicate a pin that really is
> connected all the way from the FTDI chip to the reset logic on your board,
> you can use it as a reset pin in OpenOCD.
>
> /Andreas
>
> [1] The pin needs to be defined with a signal name in a configuration
> file. If the name is set to nSRST (or nTRST), the pin can be controlled by
> the regular reset commands. Otherwise it can be controlled using the
> ftdi_set_signal command.
>
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
