Here are my choices from most favorite to least:
[ 1, 6, 4, 7, 8, 9, 3, 2, 5 ]
Ed
___
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel
"De Cesaris, Ivan" wrote:
>
>Hi All,
>jumping on the topic of "the future of OpenOCD", one thing I'd like the core
>group to consider is the license.
>
>Maybe this is not obvious to everyone but the code, being GPL, precludes some
>usages.
>I'm not a lawyer but I can't release internal developed
Michael Schwingen wrote:
>This is with current git master (pulled yesterday).
>
>Any hints where to look? Is FT2232+KTLINK or the LPC812 considered stable?
I don't know if this is related, but I just started attempting to use my new
SWD adapter for the Olimex ARM-USB-TINY-H and an em358 target.
Paul Fertser wrote:
>On Thu, Mar 05, 2015 at 10:32:41AM -0500, Ed Beroset wrote:
>> Andreas Fritiofson wrote:
>> >Have you read the note in target/stellaris.cfg about nSRST not working well
>> >on those chips?
>...
>> I'm trying to get this working for
Andreas Fritiofson wrote:
>On Thu, Mar 5, 2015 at 2:39 PM, Ed Beroset wrote:
>>
>> Specifically, if I use "reset_config none" I get no error, but if I issue
>> "reset_config srst_only" I get the error every time. Here's the
>> openocd.cfg I&
Ed Beroset wrote:
>
>[...]
>>Something has made it unhappy, but I'm not entirely sure what. Any clues to
>>where I can look next? I believe this is the last impediment to my fully
>>using OpenOCD and gdb on this target. Thanks!
>
>I have determined that thin
Ed Beroset wrote:
[...]
>Something has made it unhappy, but I'm not entirely sure what. Any clues to
>where I can look next? I believe this is the last impediment to my fully
>using OpenOCD and gdb on this target. Thanks!
I have determined that things that used to work don&
As I have been trying to find out what's wrong with my particular
board/installation, I tried using the measure_clk command. It works, but
reported that my clock was 0.495 kHz when it was actually set to (and verified
by frequency counter) to be 500 kHz. It turned out to be a simple fix which
I'm currently working with a TI Firestorm part and trying to use OpenOCD for
debugging. I'm currently using the Olimex ARM-USB-TINY-H dongle (but get the
same results with the Luminary ICDI dongle). Here's my openocd.cfg file:
source [find interface/ftdi/olimex-arm-usb-tiny-h.cfg]
adapter_khz
Paul Fertser wrote:
> Hello,
>
> On Thu, Feb 19, 2015 at 06:01:29PM -0500, Ed Beroset wrote:
>> I have a Stellaris part that is locked and wanted to use OpenOCD to
>> unlock it. I see that there is a "stellaris unlock 0" function
>> available but it doesn&#
I have a Stellaris part that is locked and wanted to use OpenOCD to unlock it.
I see that there is a "stellaris unlock 0" function available but it doesn't
work because it only works after the part has been identified. That can't
work, at least with JTAG, because the part is locked. In doing
I followed the steps here:
http://openocd.sourceforge.net/doc/doxygen/html/index.html and successfully
created and submitted a patch. That patch has now been committed to the code,
so what I'd like to do is to bring my local copy up to date with the online
version. I attempted it via this se
12 matches
Mail list logo
