On Oct 31, 2008, at 2:35 AM, Øyvind Harboe wrote:
The attached patch will address *some* of the problems you have found. If you can help with testing and get this committed, perhaps we can see more clearly what's going on once the first couple of bugs are fixed. The attached patch improves error handling. Testing is needed for each point below: 1. if writing memory arguments fails, run_algorithm will now fail early. An error should be reported and displayed properly.2. if running the algorithm failed, e.g. w/unexpected exit point, then thereshouldn't be a dangling breakpoint anymore. An error should be reported and displayed properly. 3. Do you have a case where running the algorithm *does* work that you can run as a regression test? Thanks! -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 XScale Cortex JTAG debugger and flash programmer <cortexfixrunalgorithm.txt>
I'll play with this tonight. I seem to be able to get the flash writes to work most of the time if I use 'reset halt' or 'reset init; halt' so I should be able to try some regression testing. I'm still concerned that removing the dangling breakpoint would produce a error message and even more concerned that the error message would change if I set a breakpoint on the original error message under gdb.
-- Rick Altherr [EMAIL PROTECTED]"He said he hadn't had a byte in three days. I had a short, so I split it with him."
-- Slashdot signature
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
