Øyvind Harboe wrote:
> type "help reset"
>
Yes but that doesn't say what the parameters do.
> openocd.texi under subversion control. It is in sync w/source of course :-)
>
> to build a PDF file:
>
> make pdf
>
accessing the installed openocd.info is fine for me. (Although I got the
impres
Øyvind Harboe wrote:
>> target state: halted
>> target halted in ARM state due to debug-request, current mode: Supervisor
>> cpsr: 0x00d3 pc: 0x
>>
>>> flash protect 0 0 2 off
>>>
>> memory read caused data abort (address: 0x0001, size: 0x1, count: 0x1)
>> memory read ca
PS. here's my openocd.cfg, just to make sure we know what we're talking
about:
telnet_port 5
gdb_port 50001
interface ft2232
ft2232_device_desc "Olimex OpenOCD JTAG TINY"
ft2232_layout olimex-jtag
ft2232_vid_pid 0x15ba 0x0004
source /home/chrisarm/src/openocd-svngit--trunk/src/target/target/s
Christian Jaeger wrote:
Øyvind Harboe wrote:
Try the attached patch.
It should cause an error rather than running into an infinite loop.
Hm, somehow today I'm only getting the "target not halted" and
subsequent "Target not examined yet" error when issuing &quo
Øyvind Harboe wrote:
> Committed.
>
Did you see my patch of your patch?
SVN version 970 is giving:
/home/chrisarm/src/openocd-svngit--trunk/src/flash/str9x.c: In function
‘str9x_write’:
/home/chrisarm/src/openocd-svngit--trunk/src/flash/str9x.c:630: error:
redeclaration of ‘i’ with no linka
Øyvind Harboe wrote:
Try the attached patch.
It should cause an error rather than running into an infinite loop.
Hm, somehow today I'm only getting the "target not halted" and
subsequent "Target not examined yet" error when issuing "halt", even
with yesterday's code. I'd think the order i
Thanks for your reply, I've only now gotten back to this topic.
Øyvind Harboe wrote:
Please include a debug_level 3 log. This will tell me the origin of the error.
At first, I've run openocd -d3 and attached gdb and ran "load" of the
same old .elf file from there. Somehow this time it seem
Hello
I'm connecting an Olimex arm-usb-tiny to a STEVAL IFD001V1 with
STR912FAW44 cpu. I run openocd (SVN revision 895 and/or 902) and then
connect with gdb someimage.elf, then run:
(gdb) load
Error erasing flash with vFlashErase packet
Error: error erasing flash bank, status: 0xa2
Error: fai
Duane Ellis wrote:
> duane> I believe this would be a better solution.
>
> [snip]
>
> dominic>We would end up with quite a few config files.
>
> Ugh - that would be nasty.
>
> Then why not change openocd - w/ an #if WINDOWS - try the given DESC ,
> if that fails, quietly append " A" and try again.
It seems that ft2232_vid_pid is absolutely required and
ft2232_device_desc has to match as well at the same time.
---
src/target/interface/olimex-jtag-tiny.cfg |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/src/target/interface/olimex-jtag-tiny.cfg
b/src/target/interfa
---
...olimex-jtag-tiny-a.cfg => olimex-jtag-tiny.cfg} |0
1 files changed, 0 insertions(+), 0 deletions(-)
rename src/target/interface/{olimex-jtag-tiny-a.cfg => olimex-jtag-tiny.cfg}
(100%)
diff --git a/src/target/interface/olimex-jtag-tiny-a.cfg
b/src/target/interface/olimex-jtag-tiny.
Hello,
I've spent quite a bit of time trying to get access to an ARM-USB-TINY
interface while only getting the not so helpful answer
Error: unable to open ftdi device: device not found
Runtime error, file "?", line 1:
unable to open ftdi device: device not found
I had been using (amongst
12 matches
Mail list logo
