On 17/12/2010 07:54, Mathias K. wrote:
Hello,
the command soft_reset_halt of the current git version of openocd segfault:
(gdb) bt full
#0 cortex_m3_assert_reset (target=0x818dba0) at cortex_m3.c:942
cortex_m3 = 0x818f118
swjdp = 0x818f1d0
reset_config =error
Hello,
sorry, the reset call doesnt work.
I can try it from my upload script (included in the cfg file) or from telnet.
Openocd crash on both.
I have also append the console output without the debug option.
Regards,
Mathias
--- console output ---
Open On-Chip Debugger
On 17/12/2010 10:38, Mathias K. wrote:
Hello,
sorry, the reset call doesnt work.
I can try it from my upload script (included in the cfg file) or from telnet.
Openocd crash on both.
I have also append the console output without the debug option.
You really should be using the included
On 17/12/2010 10:38, Mathias K. wrote:
Hello,
sorry, the reset call doesnt work.
I can try it from my upload script (included in the cfg file) or from telnet.
Openocd crash on both.
I have also append the console output without the debug option.
Just tried to reproduce this with your
There are a lot of areas where the Tcl API could be improved in
openocd config files.
Your load_target is just another example of this.
I don't want to go rushing in here. We need to define a convention
that we're going to stick with.
For sure it should be *much* less verbose.
--
Øyvind
Hello,
okay i switched over to the scripts shipped with openocd and i got the crash
again. I cleand up the
source tree with depclean, compiled again and it is okay now.
My mistake, sorry.
Thanks,
Mathias
Am 17.12.2010 12:07, schrieb Spencer Oliver:
On 17/12/2010 10:38, Mathias K.
Hey guys,
I still have a very similar crash on Mac OS X when compiling openocd using
64bit. The problem disappears when using -m32 flag to the gcc and forcing 32bit
compilation.
The thread about that can be found here:
Hi all,
Here my first patches to be able to use the CFI driver on cortex M3 with the
helper code on target. This is probably not the better way of doing it, but
at least it's work. This have been tested on real hardware. The default cfg
that enable the fsmc can be used. Right now only the 16 bit
?yvind Harboe wrote:
Which is better? (whatever better is)
This:
if {[info exists CHIPNAME]} {
set _CHIPNAME $CHIPNAME
} else {
set _CHIPNAME at91r40008
}
or this:
set _CHIPNAME [defaultval $CHIPNAME at91r40008]
As someone who USES OpenOCD but doesn't live and breathe it,
On Fri, Dec 17, 2010 at 5:03 PM, John Hartman (NoICE)
j...@noicedebugger.com wrote:
?yvind Harboe wrote:
Which is better? (whatever better is)
This:
if {[info exists CHIPNAME]} {
set _CHIPNAME $CHIPNAME
} else {
set _CHIPNAME at91r40008
}
or this:
set _CHIPNAME [defaultval
Øyvind Harboe wrote:
In my opinion the if/then version makes it easier for new users
to customize cfg files. And since most users will need to
customize at least one cfg file, I think simplicity trumps short
files.
I think you raise important enough points that unless they are
On Fri, Dec 17, 2010 at 5:33 PM, Peter Stuge pe...@stuge.se wrote:
Øyvind Harboe wrote:
In my opinion the if/then version makes it easier for new users
to customize cfg files. And since most users will need to
customize at least one cfg file, I think simplicity trumps short
files.
I
Hi,
i start working with the SAM3S4C, but having trouble with openOCD. When I start
debugging, the very first instructions are working fine, but after the 3rd
instruction, its jumping acrross the code.
This is my main.cpp
int main(void) {
int a, i = 0;
a = 5;
for(i = 0; i 10;
Hi,
I did some work on the IXP42x config files, adding more known TAP IDs plus
some helper functions and constants to make board config files simpler and
easier to read.
I have seen 3 of the 6 listed TAP IDs on real hardware, and the others are
inferred from the documentation. There might be
On 18/12/2010, at 6:30 AM, Michael Schwingen wrote:
Hi,
I did some work on the IXP42x config files, adding more known TAP IDs plus
some helper functions and constants to make board config files simpler and
easier to read.
I have seen 3 of the 6 listed TAP IDs on real hardware, and the
Hi, I have an IAR (Olimex OEM) STM32-SK board which has an RST to TRST jumper,
soldered together from the factory, like is also commented here:
http://www.micromouseonline.com/blog/2008/08/05/stm32-and-the-seggeriar-j-link/
To use it with openocd via the IAR (Segger OEM) j-link I have to run
Tormod Volden writes:
Section 9.2 under Signals shorted says to use the
reset_config combination options, however it is not clearly listed which of
the options are of combination type. Naively I tried combined but that
does
not work, it needs separate. Is trst_and_srst a combination?
I have
17 matches
Mail list logo
