[Openocd-development] [PATCH] CMake Support

2009-04-13 Thread Dick Hollenbeck
See Dick make CMake files. Can you CMake any sense of this? http://www.vtk.org/Wiki/CMake_FAQ I find it easier to get work done in CMake than in any other build system that I have used. I am not a CMake expert, but this is a decent first draft. I believe it will be possible to get t

Re: [Openocd-development] Segfault when using breakpoints

2009-04-13 Thread Ken Smith
Fantastic! Your patch allows me to single step. You have fixed my one and only problem with OpenOCD. Keep up the great work. Sincere thanks, Ken On Mon, Apr 13, 2009 at 5:31 PM, Zach Welch wrote: > Given your information and the code, the attached patch should work > around the problem,

Re: [Openocd-development] Segfault when using breakpoints

2009-04-13 Thread Zach Welch
Given your information and the code, the attached patch should work around the problem, unless there are instructions not handled by the following block of logic. I added output to see if that is the case. Cheers, Zach On Tue, 2009-04-14 at 00:50 +0200, Magnus Lundin wrote: > Hi, > > Is it pos

Re: [Openocd-development] Segfault when using breakpoints

2009-04-13 Thread Magnus Lundin
Hi, Is it possible to find out the exact assembly code that kills OpenOCD ? Let me guess that I could be an immediate shift or MOVS in thumb mode . I am not an expert on the single step PC prediction code in arm_simulate_step(target_t *target, u32 *dry_run_pc) but there are some tumb instructio

Re: [Openocd-development] Segfault when using breakpoints

2009-04-13 Thread Ken Smith
On Mon, Apr 13, 2009 at 2:23 PM, Hermann Kraus wrote: > On Mon, 13 Apr 2009 23:11:29 +0200, Ken Smith wrote: >> >> This crash kills openocd every time.  Any ideas? > > I have the same problem and one more person on this list also reported it. > It crashes at exactly the same location. I hope some

Re: [Openocd-development] Segfault when using breakpoints

2009-04-13 Thread Hermann Kraus
On Mon, 13 Apr 2009 23:11:29 +0200, Ken Smith wrote: > This crash kills openocd every time. Any ideas? I have the same problem and one more person on this list also reported it. It crashes at exactly the same location. I hope someone fixes this soon, as I currently don't have the time to deb

[Openocd-development] Segfault when using breakpoints

2009-04-13 Thread Ken Smith
I tried to post this to the forum at sparkfun but was denied with: Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Your administrator may not have enabled CGI access for this directory. Thinking about it more, perhaps

Re: [Openocd-development] STM32: How to debug in RAM with GDB? STICKY ERROR

2009-04-13 Thread Magnus Lundin
Hi, The STICKY ERROR messages comes when the debugger asks OpenOCD to read a 32 bit word from address 0xfffe. This is not a valid STM32 memory address so an AHB bus error is generated and shows up at the debug interface as a sticky error. I would say that OpenOCD does exactly what it is su

Re: [Openocd-development] AU1100 (MIPS) problems Fixed!

2009-04-13 Thread John McCarthy
Hi Nico, On Fri, 2009-04-10 at 11:46 +0200, Nico Coesel wrote: > Another update on the AU1100 troubles. Adding 5 clocks after clearing > the Pracc bit solved the problem. The patch is attached to this e-mail. I like this much better. Only question is does this slow down targets that don't need i

Re: [Openocd-development] Converge towards 0.2?

2009-04-13 Thread Dominic
The original idea behind the 7-clocks table and the stable states for which it was defined was that it shouldn't matter how the state machine moves from one stable state to another, as long as some constraints are met like not passing through Test-Logic-Reset or Run-Test/Idle unless ordered to.