Unfortunately I can't change the PC:
(gdb) set $pc=0xd850
Value being assigned to is no longer active.
Fixed in head of GDB?
http://www.nabble.com/Patch-for-the-gdb-problem-%C2%ABValue-being-assigned--to-is-no-longer-active%C2%BB-td23615004.html
Is there any other way to setup the PC
1614 introduces *lots* of changes. It could have been broken into half
a dozen commits. :-)
One thing to try:
tms_sequence long
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
___
Openocd-development
Gary Carlson wrote:
1) One of the features that the software currently allows is configuration
setting inheritance from board to target to CPU. While I generally am a big
advocate of extensibility in most software projects, I have been very leery
of doing this for hardware-specific
2) One possible process improvement that I believe makes sense is to start
enforcing a rule that authors of new configuration files must include a
minimal comment header at the top of the file that specifies the exact
hardware/debugger combination used. The SAM-ICE (J-link) debugger I am
3) One feature that I think may make sense to add at some point in the
future to the main software is support for label/value associations that
allow hexadecimal register values to be associated with more legible and
understandable names. Looking at mww 0x3ec2 0x2 in a configuration
Some quick comments...
Why are you using reset halt and not reset init?
last qestion:
if i try the command line
openocd -f jtagkey.cfg -f sam7x512.cfg -c script flash.script
I have an error:
Unknown command: reset halt
You need to set up OpenOCD after configuring it by running
the init
I can now see that I left off a critical detail! :)
Yes, you most certainly can use a TCL set command to accomplish this. The
only issue is you have to spend an inordinate amount of time entering the
values by hand. That in itself is another source for errors -- especially
on processors with
On 9/1/09 12:04 AM, Øyvind Harboe oyvind.har...@zylin.com wrote:
2) One possible process improvement that I believe makes sense is to start
enforcing a rule that authors of new configuration files must include a
minimal comment header at the top of the file that specifies the exact
Crazy idea:
- write a small C app for the target that goes along with board config file
- this .elf file is loaded by OpenOCD
- use built-in ARM simulator to execute fn's in that .elf file
?
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
Øyvind Harboe wrote:
Crazy idea:
- write a small C app for the target that goes along with board config file
- this .elf file is loaded by OpenOCD
- use built-in ARM simulator to execute fn's in that .elf file
What advantage does that provide?
You need a disassembler to view the effective
Hi Magnus,
On Mon, Aug 31, 2009 at 05:36:11PM +0200, Magnus Lundin wrote:
dap_ap_select(swjdp, 1);
before the two lines
dap_ap_read_reg_u32(swjdp, 0xFC, idreg);
dap_ap_read_reg_u32(swjdp, 0xF8, romaddr);
in ahbap_debugport_init()
What happens when you do dap info
On Tue, Sep 1, 2009 at 10:24 AM, Michael
Schwingenrincew...@discworld.dascon.de wrote:
Øyvind Harboe wrote:
Crazy idea:
- write a small C app for the target that goes along with board config file
- this .elf file is loaded by OpenOCD
- use built-in ARM simulator to execute fn's in that .elf
Harald Welte wrote:
Hi Magnus,
On Mon, Aug 31, 2009 at 05:36:11PM +0200, Magnus Lundin wrote:
dap_ap_select(swjdp, 1);
before the two lines
dap_ap_read_reg_u32(swjdp, 0xFC, idreg);
dap_ap_read_reg_u32(swjdp, 0xF8, romaddr);
in ahbap_debugport_init()
Øyvind Harboe wrote:
What advantage does that provide?
You need a disassembler to view the effective board-init sequence, you
need a cross-toolchain to modify the code, in comparison to just
changing a script file.
You can use the header files for the target file without having to
Hm - yes, that might be useful. I have used objdump to extract the
initialization tables from my board-init code to create BDI2000/OpenOCD
init scripts.
Now, if we could do that in some *nice* way it would be quite
a powerful method. Most every PCB out there has some working
sample code
On Tue, Sep 1, 2009 at 11:54 AM, Peter Zuidemapzuid...@octrium.com wrote:
The AT91SAM7X(C)512 contains 2 flash banks, each 256KB.
Yes, I know
You have to change the sam7x512.cfg and add a flash-bank definition.
Are you sure?
The doc/openocd.pdf has some information in chapter 13 Flash
Hi Oyvind,
On 9/1/09, Øyvind Harboe oyvind.har...@zylin.com wrote:
Fixed in head of GDB?
http://www.nabble.com/Patch-for-the-gdb-problem-%C2%ABValue-being-assigned--to-is-no-longer-active%C2%BB-td23615004.html
Thank you very much!
Is there any other way to setup the PC to right position?
michal smulski wrote:
When I run this code:
set CONFIG_SYS_HZ_CLOCK16500
global CONFIG_SYS_HZ_CLOCK
proc showAmbaPLL {} {
global CONFIG_SYS_HZ_CLOCK
puts [format CONFIG_SYS_HZ_CLOCK %d $CONFIG_SYS_HZ_CLOCK]
}
I get this message:
Runtime error, file t.tcl,
The svn 2600 cannot finalize MAKE under windows cygwin.
Note: openocd.exe is compiled and is working for both Amontec JTAGkey
and Amontec JTAGkey-2
Here the result of the last line of make :
make[2]: Leaving directory
`/cygdrive/c/amontec/openocd_builder/svn/trunk/src'
Making all in doc
19 matches
Mail list logo
