On Nov 29, 2010, at 12:39 PM, Øyvind Harboe wrote: > Better. > > Could you try HEAD w/master branch? > >> #0 0x0000000100073314 in mem_ap_read_atomic_u32 (dap=0x10032f540, >> address=1, value=0x10032e800) at arm_adi_v5.c:214 > > => this doesn't point to anything sensible, it's the tailend of the fn. > > Also try w/-O0 > > CFLAGS="-O0 -g" configure ... > make clean > make
I did that but it does not change anything. It is still failing at the same line. For more context maybe this helps. This is the signal I get: Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: 13 at address: 0x0000000000000000 0x000000010007325c in mem_ap_read_atomic_u32 (dap=0x10032f540, address=1, value=0x10032e800) at arm_adi_v5.c:214 Also I stepped through the code and this is what is happening: jim_target_reset (interp=0x100308c90, argc=3, argv=0x7fff5fbfc9d8) at target.c:4321 cortex_m3_assert_reset (target=0x10032e950) at cortex_m3.c:921 mem_ap_read_atomic_u32 (dap=0x10032f7b0, address=3758157296, value=0x10032f6b0) at arm_adi_v5.c:209 dap_run (dap=0x10032f7b0) at arm_adi_v5.h:337 jtag_dp_run (dap=0x10032f7b0) at adi_v5_jtag.c:435 jtagdp_transaction_endcheck (dap=0x10032f7b0) at adi_v5_jtag.c:222 jtag_dp_run (dap=0x10032f7b0) at adi_v5_jtag.c:436 dap_run (dap=0x10032f7b0) at arm_adi_v5.h:339 mem_ap_read_atomic_u32 (dap=0x10032f7b0, address=3758157296, value=0x10032f6b0) at arm_adi_v5.c:214 these calls work correctly in that order each calling the next. As soon as dap_run returns the mem_ap_read_atomic_u32 function wants to return the dap_run value but failes with the memory access error quoted before. I have never seen such wired behavior before. Cheers Esden -- Blog: http://www.esden.net Projects: http://open-bldc.org http://paparazziuav.org http://github.org/esden/floss-jtag http://github.org/esden/summon-arm-toolchain
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
