openocd-devel

[OpenOCD-devel] Flyswatter Rev-B interface issue

[Laszlo P. <lp...@kd...>]

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, it is based on schematics and
code
in ft2232.c. Please report your experience with this file to openocd-devel
mailing list, so it could be marked as working or fixed.
Info : only one transport option; autoselect 'jtag'
RCLK - adaptive
fast memory access is enabled
dcc downloads are enabled
force hard breakpoints
use of EmbeddedICE dbgrq instead of breakpoint for target halt enabled
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
connect_deassert_srst
Info : RCLK (adaptive clock speed) not supported - fallback to 1500 kHz
Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: omapl138.jrc: IR capture error; saw 0x3f not 0x01
Warn : Bypassing JTAG setup events due to errors
Error: Target not examined yet
...
<<<<

Here you can find the schematic for details:
https://www.tincantools.com/assets/FLYSWATTER_REV-B.pdf

Many thanks,
Laszlo

Re: [OpenOCD-devel] Flyswatter Rev-B interface issue

[Peter S. <pe...@st...>]

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 could be marked as working or fixed.

So if it isn't working then please submit a fix. See the file HACKING
for instructions.


Thanks

//Peter

Re: [OpenOCD-devel] Flyswatter Rev-B interface issue

[Andreas F. <and...@gm...>]

On Fri, Jul 5, 2013 at 8:07 PM, Laszlo Papp <lp...@kd...> 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 GPL v2
> For bug reports, read
>         http://openocd.sourceforge.net/doc/doxygen/bugs.html
> 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 could be marked as working or fixed.
> Info : only one transport option; autoselect 'jtag'
> RCLK - adaptive
> fast memory access is enabled
> dcc downloads are enabled
> force hard breakpoints
> use of EmbeddedICE dbgrq instead of breakpoint for target halt enabled
> trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
> connect_deassert_srst
> Info : RCLK (adaptive clock speed) not supported - fallback to 1500 kHz
>

Does your target handle 1500 kHz?

Error: JTAG scan chain interrogation failed: all ones
> Error: Check JTAG interface, timings, target power, etc.
> Error: Trying to use configured scan chain anyway...
> Error: omapl138.jrc: IR capture error; saw 0x3f not 0x01
> Warn : Bypassing JTAG setup events due to errors
> Error: Target not examined yet
> ...
> <<<<
>
> Here you can find the schematic for details:
> https://www.tincantools.com/assets/FLYSWATTER_REV-B.pdf
>
>
The config file matches the schematic, as far as I can tell.

Have you double-checked connections, tried another target, etc?

/Andreas

Re: [OpenOCD-devel] Flyswatter Rev-B interface issue

[Laszlo P. <lp...@kd...>]

> 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] -> I also tried [find
interface/flyswatter.cfg]

The board config is something like this:

proc programFoo ()
{
    global foo
    global foo_addr
    global foo_size
    halt
    wait_halt
    arm7_9 dcc_downloads enable
    sleep 15
    poll
    mww a b
    sleep 15
    flash erase_address $foo_addr $foo_size
    flash write_image  $foo $foo_addr
    sleep 15
    reset run
    sleep 15
    shutdown
}


> The config file matches the schematic, as far as I can tell.

As for me, it seems there is a mismatch actually: 0xcdb instead of
0xcfb as it should be input to be high, or I am getting something
wrong?

At any rate, I am getting the same issue with ftdi/flyswatter as well
as flyswatter.

> Have you double-checked connections, tried another target, etc?

I have no EVM if that is what you mean, or even a spare board. Not
really sure what connections you mean, but I just use the usb for
supplying the power and the 14-pin for flashing on the target board.

Any more ideas?

Many thanks,

Laszlo



On Fri, Jul 5, 2013 at 8:56 PM, Andreas Fritiofson <
and...@gm...> wrote:

> On Fri, Jul 5, 2013 at 8:07 PM, Laszlo Papp <lp...@kd...> 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 GPL v2
>> For bug reports, read
>>         http://openocd.sourceforge.net/doc/doxygen/bugs.html
>> 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 could be marked as working or fixed.
>> Info : only one transport option; autoselect 'jtag'
>> RCLK - adaptive
>> fast memory access is enabled
>> dcc downloads are enabled
>> force hard breakpoints
>> use of EmbeddedICE dbgrq instead of breakpoint for target halt enabled
>> trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
>> connect_deassert_srst
>> Info : RCLK (adaptive clock speed) not supported - fallback to 1500 kHz
>>
>
> Does your target handle 1500 kHz?
>
> Error: JTAG scan chain interrogation failed: all ones
>> Error: Check JTAG interface, timings, target power, etc.
>> Error: Trying to use configured scan chain anyway...
>> Error: omapl138.jrc: IR capture error; saw 0x3f not 0x01
>> Warn : Bypassing JTAG setup events due to errors
>> Error: Target not examined yet
>> ...
>> <<<<
>>
>> Here you can find the schematic for details:
>> https://www.tincantools.com/assets/FLYSWATTER_REV-B.pdf
>>
>>
> The config file matches the schematic, as far as I can tell.
>
> Have you double-checked connections, tried another target, etc?
>
> /Andreas
>
>

Re: [OpenOCD-devel] Flyswatter Rev-B interface issue

[Laszlo P. <lp...@kd...>]

On Mon, Jul 8, 2013 at 3:18 PM, Laszlo Papp <lp...@kd...> 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 like this:
>
> proc programFoo ()
> {
>     global foo
>     global foo_addr
>     global foo_size
>     halt
>     wait_halt
>     arm7_9 dcc_downloads enable
>     sleep 15
>     poll
>     mww a b
>     sleep 15
>     flash erase_address $foo_addr $foo_size
>     flash write_image  $foo $foo_addr
>     sleep 15
>     reset run
>     sleep 15
>     shutdown
> }
>
> To be completely precise just in case: openocd -f flyswatter.cfg  -c
my_board.cfg "init" -c "reset_init" -c "programFoo ()"

Cheers,
Laszlo

Re: [OpenOCD-devel] Flyswatter Rev-B interface issue

[Laszlo P. <lp...@kd...>]

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 <lp...@kd...> wrote:

> On Mon, Jul 8, 2013 at 3:18 PM, Laszlo Papp <lp...@kd...> 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 like this:
>>
>> proc programFoo ()
>> {
>>     global foo
>>     global foo_addr
>>     global foo_size
>>     halt
>>     wait_halt
>>     arm7_9 dcc_downloads enable
>>     sleep 15
>>     poll
>>     mww a b
>>     sleep 15
>>     flash erase_address $foo_addr $foo_size
>>     flash write_image  $foo $foo_addr
>>     sleep 15
>>     reset run
>>     sleep 15
>>     shutdown
>> }
>>
>> To be completely precise just in case: openocd -f flyswatter.cfg  -c
> my_board.cfg "init" -c "reset_init" -c "programFoo ()"
>
> Cheers,
> Laszlo
>

Re: [OpenOCD-devel] Flyswatter Rev-B interface issue

[Andreas F. <and...@gm...>]

On Mon, Jul 8, 2013 at 6:56 PM, Laszlo Papp <lp...@kd...> 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 the notice from flyswatter.cfg now? Have you verified that
both SRST and TRST are working?

Regarding 0xcdb vs 0xcfb it's OK as it is. A_nSRST as output, driven high
to pull the reset line low, driven low to release it.

/Andreas

Re: [OpenOCD-devel] Flyswatter Rev-B interface issue

[Laszlo P. <lp...@kd...>]

On Mon, Jul 8, 2013 at 6:42 PM, Andreas Fritiofson <
and...@gm...> wrote:

>
> On Mon, Jul 8, 2013 at 6:56 PM, Laszlo Papp <lp...@kd...> 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 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, and this one is not like that.

Off-topic: I opened a new thread about an issue with the same scenario, but
a different interface jtag. Your help would be appreciated if you have
anything to comment on. :)

Regarding 0xcdb vs 0xcfb it's OK as it is. A_nSRST as output, driven high
> to pull the reset line low, driven low to release it.
>

OK, fair enough.

Many thanks,
Laszlo

Re: [OpenOCD-devel] Flyswatter Rev-B interface issue

[Peter S. <pe...@st...>]

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 they are what
actually matters.


//Peter

Re: [OpenOCD-devel] Flyswatter Rev-B interface issue

[Laurent G. <lau...@am...>]

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 JTAGkey-2P.

Best regards,
Laurent
  http://www.amontec.com

Le 08.07.2013 22:06, Peter Stuge a écrit :
> 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 they are what
> actually matters.
>
>
> //Peter
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> OpenOCD-devel mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openocd-devel