On Jan 6, 2009, at 10:59 PM, Peter LaDow wrote:
1. How does one determine the proper CPUTAPID value for the
"-expected_id"? Is this a trial and error thing?
Basically. The data sheet for the part _might_ say in the section on
debugging. In general, we just get the value reported by an a
Committed.
Thanks!
--
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 XScale Cortex
JTAG debugger and flash programmer
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/ope
Ok, I think perhaps it is working. I'll have to do some further
testing to determine if this is indeed the case, but I did figure out
some things, I think.
On Tue, Jan 6, 2009 at 8:35 AM, Rick Altherr wrote:
> It may not make a difference, but r717 is fairly old and many changes and
> fixes have
Peter LaDow a écrit :
> This may not directly be an OpenOCD issue, but I am trying to debug my
> design. Since this list is well populated with ARM users, perhaps
> somebody has some insight.
>
> I've received the parts and assembled my first LPC2148 based design.
> I've also purchased the Olimex
This is the addition of the Python based SVF to XSVF converter and the
XSVF file dumper.
The xsvf.c rewrite is nearing completion and that patch should also be
forthcoming soon.
Dick
Index: tools/xsvf_tools/xsvfdump.py
===
--- t
RLink support is new and I believe untested on Windows. Adding the
original contributors to CC.
Rick
On Jan 6, 2009, at 12:10 PM, Freddie Chopin wrote:
First post here, so ... hi there!
Yesterday I managed to succesfully compile the latest OpenOCD
release I
took from SVN (revision 1302
First post here, so ... hi there!
Yesterday I managed to succesfully compile the latest OpenOCD release I
took from SVN (revision 1302). I'm using Windows 2003 Server, and
compiled that using MinGW/MSYS with hundreds of additional modules (;
I compiled the code just for the RLINK that sits on t
It may not make a difference, but r717 is fairly old and many changes
and fixes have been made in the meantime. Please try with the current
SVN trunk as it includes more debugging information when run with
'debug_level 3'. Also, 'debug_level 3' should be the first line in
your first confi
Hello Peter and list,
I might be looking into completely wrong direction in this case, but it is
worth noting
that when I was experimenting with LPC2148 with OpenOCD,
If found out, that LPC needs reset pulled while RTCK is low.
At least from what I've seen, it seemed to me that power-on
reset is
On Tue, Jan 6, 2009 at 12:16 AM, Rick Altherr wrote:
> It doesn't appear that you've specified any JTAG taps. That _should_ be a
> hard error when init is run. It appears that OpenOCD is trying to validate
> the chain anyway.
>
> You'll need to add some lines to your config to describe the taps
are you running from RAM or FLASH?
On Mon, Dec 29, 2008 at 3:05 PM, Michel Catudal wrote:
> I have a few issues with debugging a STM32-SK board (using eclipse with
> the latest Zylin plugin)
>
> I have modified the IAR application so it would work with my arm-elf-gcc
> compiler. I use the latest
On Dec 29, 2008, at 6:46 AM, trollepi jj wrote:
Hi,
I use the latest version of openocd (rev. 1293) and I try to use it
with the at91sam9261-ek and a jlink (v 7.0) in Fedora 8.
I try to debug on SDRAM and it works but very slow (jtag_khz 30).
I replace jtag_khz by jtag_rclk. Again, nothing
It doesn't appear that you've specified any JTAG taps. That _should_
be a hard error when init is run. It appears that OpenOCD is trying
to validate the chain anyway.
You'll need to add some lines to your config to describe the taps on
the JTAG chain. Look at the target scripts included
This may not directly be an OpenOCD issue, but I am trying to debug my
design. Since this list is well populated with ARM users, perhaps
somebody has some insight.
I've received the parts and assembled my first LPC2148 based design.
I've also purchased the Olimex ARM-USB-TINY module to use for
pr
14 matches
Mail list logo
