> 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 <
[email protected]> wrote:
> On Fri, Jul 5, 2013 at 8:07 PM, Laszlo Papp <[email protected]> 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
>
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
