Hi, The STICKY ERROR messages comes when the debugger asks OpenOCD to read a 32 bit word from address 0xfffffffe. 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 supposed to do, but the error reporting is not easy to understand.
I think the main problem is that Insight has problems interpreting the processor state before running the low level setup code. Regards, Magnus Michael Fischer skrev: > Hello, > > I want to debug a STM32 example in RAM with Insight, OpenOCD r1454 is used. > Btw, OpenOCD under windows, and with a JTAGkey. > > The problem is, that the debugger set the wrong SP and PC at start, > therefore > we must help GDB and set the SP and PC before. > > Remember, I want to debug in RAM, therefore the vector table is located at > 0x20000000. > > In the GDB script I use the following commands: > > # Set SP and PC > set $sp = *(int*)0x20000000 > set $pc = *(int*)0x20000004 > > With this commands the SP and PC is set, but I get the following errors in > the OpenOCD window: > > Error: address+size wrapped(0xfffffffe, 0x00000004) > Error: AHBAP: dp_select 0x0, ap_csw 0xa2000010, ap_tar 0xffffffff > Error: SWJ-DP STICKY ERROR > Error: dcb_dhcsr 0x30003, nvic_shcsr 0x20000, nvic_cfsr 0x0, nvic_bfar > 0xe000edf8 > Error: AHBAP: dp_select 0x0, ap_csw 0xa2000010, ap_tar 0xffffffff > Error: SWJ-DP STICKY ERROR > Error: dcb_dhcsr 0x30003, nvic_shcsr 0x20000, nvic_cfsr 0x0, nvic_bfar > 0xe000edf8 > > The other point is, that if I start Insight the first time, it will not > work. > After this is must start Insight again, and now it works. Buit still with > the > STICKY ERROR. Now I can every time close start Insight without any problems. > > But if I RESET the CPU, or close and start OpenOCD again, the first time I > want > to use Insight, it is not working. After this all other times it is working > again. > > Attached is the example, which is based on an anglia example. > > Best regards, > > Michael > > ------------------------------------------------------------------------ > > _______________________________________________ > Openocd-development mailing list > Openocd-development@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/openocd-development > _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
