What OS, host architecture, and JTAG interface are you using? The GDB
keep alive packet messages tend to show up when using GPIO-based JTAG
interfaces that have delays after a write to deal with synchronization
issues between host and target. Do your JTAG interface and target
support RTCK
Hi Rick
I'm sorry to have disappeared, I had a bunch of lessons and exams to give so
i didn't have time to work on this.
good news and bad news: the complete program crash has stopped with the
latest svn, however the gdb keep alive packet errors are still there. so in
the meantime:
I'm actually g
I don't see any obvious reason for this. destroy_reg_param() frees
exactly one item in the passed structure. From working through the
code, the pointer being freed shouldn't be changed. Sadly, that means
this is likely to be much more difficult to track. Is it easily
reproducible? If s
Hi guys,
Rick, here's the gdb output:
Error: Unable to write block write code to target
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f7e0f8626e0 (LWP 16245)]
0x7f7e0ef4fbcb in free () from /lib/libc.so.6
(gdb) bt
#0 0x7f7e0ef4fbcb in free () from /lib/lib
Run openocd under gdb and when you get a segmentation fault, type "bt"
at the gdb command prompt. Paste the results here. The output from
openocd from before the segfault would be useful as well.
Rick
On Nov 6, 2008, at 6:59 AM, Federico Spadini wrote:
Hi Oyvind,
I agree wholeheartedly.
Hi Oyvind,
I agree wholeheartedly. I'm looking into it... I'm going to probably
have to take blame for configuration file differences... I realized
that in my systematic testing at version 826 I started having to futz
with my configurations a bit to get things running (hmmh, so not
really so system
On Thu, Nov 6, 2008 at 2:17 PM, Federico Spadini <[EMAIL PROTECTED]> wrote:
> Hey Guys,
> So to respond, r826 is the first point of failure I found (825 works
> and flashes) 826 fails and does not flash.
It is inconceivable (ref. The Princess Bride) that the problem was introduced
with 826.
If yo
Hey Guys,
So to respond, r826 is the first point of failure I found (825 works
and flashes) 826 fails and does not flash.
Current SVN Head gives warning message and does not flash.
Currently rolling through 826-svn head and double checking.
version 1014 gives a different error message:
---
Does the failure actually begin happening when you use r826 or is that
when you start getting the warning about the GDB alive packet? The
warning message is actually fairly benign. If the failure starts with
that revision, it helps narrow down the problem. That said, the
various patches
hey guys,
looks like the point of failure is svn revision 826 where the gdb keep
alive messages are added to avoid "cryptic error messages" (from the
change log).
This is the error from 826
826 failure on load:
Open On-Chip Debugger 1.0 (2008-11-04-18:19) svn:826
$URL: http://svn.berlios.de/svnr
On Fri, Oct 31, 2008 at 1:06 PM, Federico Spadini <[EMAIL PROTECTED]> wrote:
> Hi Guys,
>
>
>
> I've recently built OpenOCD SVN version 1112 under Ubuntu Linux 8.04
> on AMD64 with the proper FTDI libraries. The target board is an iMote2
I'd like the imote2.cfg added to the target library. How is
11 matches
Mail list logo
