You should try Amontec JTAGkey serie.
The JTAGkey is one of the only JTAG dongle providing all states for TRST
SRST (low high tristate) and providing JTAG IO auto-sense from 1.4V to 6.5V.
If your target provide RTCK you should use JTAGkey-2.
If you want to supply your target board, you may use
Laszlo Papp wrote:
> > So can we remove the notice from flyswatter.cfg now? Have you verified
> > that both SRST and TRST are working?
>
> Unfortunately no because I am unable to use flyswatter for my board.
> I need to use a TI compatible jtag
Why? Please do not leave out the details, because th
On Mon, Jul 8, 2013 at 6:42 PM, Andreas Fritiofson <
[email protected]> wrote:
>
> On Mon, Jul 8, 2013 at 6:56 PM, Laszlo Papp wrote:
>
>> Alright, the issue seems to be silly. The root cause is the mismatch
>> between the TI and ARM jtag pinouts.
>>
>
> I was just going to reply with
On Mon, Jul 8, 2013 at 6:56 PM, Laszlo Papp wrote:
> Alright, the issue seems to be silly. The root cause is the mismatch
> between the TI and ARM jtag pinouts.
>
I was just going to reply with what I meant with double-checking
connections, but I think it's obvious now... :)
So can we remove th
Alright, the issue seems to be silly. The root cause is the mismatch
between the TI and ARM jtag pinouts.
Thank you for anyone who tried to help with this in here!
On Mon, Jul 8, 2013 at 3:29 PM, Laszlo Papp wrote:
> On Mon, Jul 8, 2013 at 3:18 PM, Laszlo Papp wrote:
>
>> > What other config
On Mon, Jul 8, 2013 at 3:18 PM, Laszlo Papp wrote:
> > What other config files do you use? (i.e show the complete command line)
>
> Well, the interface is simply this: source [find
> interface/ftdi/flyswatter.cfg] -> I also tried [find
> interface/flyswatter.cfg]
>
> The board config is something
> So if it isn't working then please submit a fix. See the file HACKING for
instructions.
Fix for what exactly? I have really no clue. ;-)
> What other config files do you use? (i.e show the complete command line)
Well, the interface is simply this: source [find
interface/ftdi/flyswatter.cfg] ->
On Fri, Jul 5, 2013 at 8:07 PM, Laszlo Papp wrote:
> Hi,
>
> I am facing the issue below when using the ftdi/flyswatter.cfg file
> interface:
>
What other config files do you use? (i.e show the complete command line)
>
> Open On-Chip Debugger 0.7.0 (2013-05-05-22:01)
> Licensed under GNU
Laszlo Papp wrote:
> I am facing the issue below when using the ftdi/flyswatter.cfg file
> interface:
> WARNING!
> This file was not tested with real interface, it is based on schematics and
> code
> in ft2232.c. Please report your experience with this file to openocd-devel
> mailing list, so it c
Hi,
I am facing the issue below when using the ftdi/flyswatter.cfg file
interface:
Open On-Chip Debugger 0.7.0 (2013-05-05-22:01)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.sourceforge.net/doc/doxygen/bugs.html
WARNING!
This file was not tested with real interface
10 matches
Mail list logo
