On Saturday 16 January 2010, Freddie Chopin wrote: > with STM32 the first > gdb "load" after power-up of STM32 fails.
Just for reference, the relevant bits of "first.log" seem to be the appended lines. I have an idea, which I'll look at later; it revolves around general weakness in fault handling in all of the ADIv5 code. Oh, and while this is clearly a "bug", from what I've heard it isn't a "regression" from the last release ... "just" a long standing bug. - Dave Debug: 359 4984 cortex_m3.c:396 cortex_m3_debug_entry(): entered debug state in core mode: Thread at PC 0xfffffffe, target->state: halted Debug: 360 4984 target.c:968 target_call_event_callbacks(): target event 2 (gdb-halt) Debug: 361 4984 target.c:968 target_call_event_callbacks(): target event 3 (halted) User : 362 4984 target.c:1234 target_arch_state(): target state: halted User : 363 4984 armv7m.c:489 armv7m_arch_state(): target halted due to debug-request, current mode: Thread xPSR: 0x01000000 pc: 0xfffffffe msp: 0xfffffffc Debug: 364 4984 target.c:968 target_call_event_callbacks(): target event 8 (gdb-end) Debug: 365 4984 command.c:133 script_debug(): command - ocd_command ocd_command type ocd_stm32.cpu curstate Debug: 366 4984 command.c:133 script_debug(): command - ocd_stm32.cpu ocd_stm32.cpu curstate Debug: 367 4984 command.c:133 script_debug(): command - ocd_command ocd_command type ocd_stm32.cpu invoke-event reset-end Debug: 368 4984 command.c:133 script_debug(): command - ocd_stm32.cpu ocd_stm32.cpu invoke-event reset-end Debug: 369 5000 gdb_server.c:2097 gdb_input_inner(): received packet: 'X8000000,0:<binary-data>' Debug: 370 5000 gdb_server.c:2097 gdb_input_inner(): received packet: 'X8000000,3f20:<binary-data>' Debug: 371 5000 gdb_server.c:1371 gdb_write_memory_binary_packet(): addr: 0x08000000, len: 0x00003f20 Debug: 372 5000 target.c:1251 target_write_buffer(): writing buffer of 16160 byte at 0x08000000 Debug: 373 5078 arm_adi_v5.c:325 swjdp_transaction_endcheck(): swjdp: CTRL/STAT error 0xf0000021 Error: 374 5078 arm_adi_v5.c:336 swjdp_transaction_endcheck(): AHBAP Cached values: dp_select 0x0, ap_csw 0xa2000012, ap_tar 0xffffffff Error: 375 5078 arm_adi_v5.c:342 swjdp_transaction_endcheck(): JTAG-DP STICKY ERROR Debug: 376 5078 arm_adi_v5.c:354 swjdp_transaction_endcheck(): swjdp: status 0xf0000001 Error: 377 5078 arm_adi_v5.c:360 swjdp_transaction_endcheck(): Read MEM_AP_CSW 0x23000052, MEM_AP_TAR 0x8000004 Debug: 378 5156 arm_adi_v5.c:325 swjdp_transaction_endcheck(): swjdp: CTRL/STAT error 0xf0000021 Error: 379 5156 arm_adi_v5.c:336 swjdp_transaction_endcheck(): AHBAP Cached values: dp_select 0x0, ap_csw 0xa2000012, ap_tar 0xffffffff Error: 380 5156 arm_adi_v5.c:342 swjdp_transaction_endcheck(): JTAG-DP STICKY ERROR Debug: 381 5156 arm_adi_v5.c:354 swjdp_transaction_endcheck(): swjdp: status 0xf0000001 Error: 382 5156 arm_adi_v5.c:360 swjdp_transaction_endcheck(): Read MEM_AP_CSW 0x23000052, MEM_AP_TAR 0x8000004 Warn : 383 5156 arm_adi_v5.c:599 mem_ap_write_buf_u32(): Block write error address 0x8000000, wcount 0xfc8 Error: 384 5156 gdb_server.c:1197 gdb_error(): unexpected error -107 _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
