OpenOCD supports STM32F103ZC debugging?

Development Boards MicroMod
1

Hello,

I have STM32F103ZC based system, and i have OpenOCD-SVN:717.

It is programming the STM32F103ZC…

Open On-Chip Debugger (2008-06-19 19:00) svn: 717

URL: http://svn.berlios.de/svnroot/repos/openocd/trunk

Info: options.c:50 configuration_output_handler(): Open On-Chip Debugger (2008-06-19 19:00) svn: 717

Info: options.c:50 configuration_output_handler(): jtag_speed: 10, 10

Info: jtag.c:1389 jtag_examine_chain(): JTAG device found: 0x3ba00477 (Manufacturer: 0x23b, Part: 0xba00, Version: 0x3)

Info: jtag.c:1389 jtag_examine_chain(): JTAG device found: 0x06414041 (Manufacturer: 0x020, Part: 0x6414, Version: 0x0)

Info: jtag.c:1389 jtag_examine_chain(): JTAG device found: 0x3ba00477 (Manufacturer: 0x23b, Part: 0xba00, Version: 0x3)

Info: jtag.c:1389 jtag_examine_chain(): JTAG device found: 0x06414041 (Manufacturer: 0x020, Part: 0x6414, Version: 0x0)

Info: target.c:237 target_init_handler(): executing reset script ‘program.script’

Info: stm32x.c:631 stm32x_probe(): device id = 0x10016414

Info: stm32x.c:670 stm32x_probe(): flash size = 256kbytes

Info: options.c:50 configuration_output_handler(): stm32x mass erase complete

Info: options.c:50 configuration_output_handler(): wrote 8492 byte from file ./main.bin in 0.953125s (8.700820 kb/s)

Info: jtag.c:1389 jtag_examine_chain(): JTAG device found: 0x3ba00477 (Manufacturer: 0x23b, Part: 0xba00, Version: 0x3)

Info: jtag.c:1389 jtag_examine_chain(): JTAG device found: 0x06414041 (Manufacturer: 0x020, Part: 0x6414, Version: 0x0)

But when i tried to debug the program, in the "RUN" menu, the single stepping functions are inactive (Gray).

And it displayed the following…

Open On-Chip Debugger (2008-06-19 19:00) svn: 717

URL: http://svn.berlios.de/svnroot/repos/openocd/trunk

Info: options.c:50 configuration_output_handler(): Open On-Chip Debugger (2008-06-19 19:00) svn: 717

Info: options.c:50 configuration_output_handler(): jtag_speed: 10, 10

Info: jtag.c:1389 jtag_examine_chain(): JTAG device found: 0x3ba00477 (Manufacturer: 0x23b, Part: 0xba00, Version: 0x3)

Info: jtag.c:1389 jtag_examine_chain(): JTAG device found: 0x06414041 (Manufacturer: 0x020, Part: 0x6414, Version: 0x0)

Info: jtag.c:1389 jtag_examine_chain(): JTAG device found: 0x3ba00477 (Manufacturer: 0x23b, Part: 0xba00, Version: 0x3)

Info: jtag.c:1389 jtag_examine_chain(): JTAG device found: 0x06414041 (Manufacturer: 0x020, Part: 0x6414, Version: 0x0)

User: target.c:436 target_process_reset(): Timed out waiting for halt after reset

Info: server.c:78 add_connection(): accepting ‘gdb’ connection from 0

Warning: gdb_server.c:416 gdb_get_packet_inner(): acknowledgment received, but no packet pending

Error: flash.c:219 get_flash_bank_by_num(): auto_probe failed -304

User: target.c:1838 handle_soft_reset_halt_command(): requesting target halt and executing a soft reset

OPenOCD-svn:717 does not have debug support for STM32F103ZC ??????

or

What is incorrect with the settings in Eclipse?

Can someone provide win32 binaries of latest OpenPCD release svn:1xxx ???

2

I’ve successfully debugged blinking led project in RAM with openocd-1362 and wiggler on stm3210e board under eclipse. Toolchain 2008q3-66 from CodeSourcery.

My GDB Initialize command set

target remote localhost:2001
set remote memory-write-packet-size 1024
set remote memory-write-packet-size fixed
set remote memory-read-packet-size 1024
set remote memory-read-packet-size fixed
load
tbreak main

I can send You openocd binary (native) by e-mail.

3

Hello,

Thank you for helping again.

It may sound stupid, but i do not know where to put the “GDB Initialization command set”, (i 've just started using these tools) .

(Further, the blinky example also has been supplied with "GDB Initialization commands " in the form of file. Again, how to use?)

1.0 Please let me know how to use these “GDB Initialization commands”.

2.0 Can’t we debug from FLASH, rather than RAM?

3.0 Can you provide win32 binaries of latest OpenPCD release svn:1xxx ???

4

Hello,

I’ve tested debugging in flash, it’s ok with following commands

target remote localhost:2001 
set remote memory-write-packet-size 1024 
set remote memory-write-packet-size fixed 
set remote memory-read-packet-size 1024 
set remote memory-read-packet-size fixed 
monitor halt
load 
thbreak main
monitor reset

It work for me with one issue, if I unplug wiggler and reset device (with reset button), program doesn’t start, even if both reset pins (nSRST and nTRST) are connected together. But if I turn device’s power off and then on - program starts. Such behaviour doesn’t trouble me very much, but it’d be nice te get some response from developers.