Hello,
when a STM32L4 is in a tight look, like "while(1){};", at least the STLink
adapter is not able to read STM provided memory, like the flash size
register. Arm provided memory like the ID register is readable. Before
#3115, the STM32L4 driver asserted in that situation. Now with (changed)
#3115 the user is warned, a possible solution is proposed and openocd exits
normal with error. Other STM32 drivers use similar coding, and I guess other
drivers do similar.
Getting control to the CPU is not possible with gdb only.
(gdb) tar ext :3333
Remote debugging using :3333
Remote connection closed
and openocd output:
Error: auto_probe failed
Error: Connect failed. Consider setting up a gdb-attach event for the \
target to prepare target for GDB connect, or use \
'gdb_memory_map disable'.
Error: attempted 'gdb' connection rejected
Is it possible to delay "auto-probe" after attaching to the target and
gaining access with e.g. "mon reset_config none; mon reset halt"?
Thanks
--
Uwe Bonnes [email protected]
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 1623569 ------- Fax. 06151 1623305 ---------
------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
