Cody Schafer

For others running into this: turns out the magical flag for objcopy is contents, without which it zeros the section's content.

Ah, found out why xPSR.T was 0: My fw.elf file's first section (address 0x08000000 length 0x000020c4) is a bootloader, which is generated/included via (approximately) the following steps: $CC -o boot.elf $BOOT_OBJ $OBJCOPY -O binary boot.elf boot.bin $LD -r -b binary boot.bin -o boot.o $OBJCOPY --rename-section .data=.bootldr,alloc,load,readonly,rom,data boot.o boot-ldr.o boot-ldr.o is then linked into the image with the following linker script snippet: SECTIONS { .bootldr ORIGIN(FLASH) : { KEEP(*(.bootldr))...

I've submitted a variation of this for inclusion. http://openocd.zylin.com/#/c/4658/

I tried the reset_config srst_only srst_nogate connect_assert_srst with fw.elf. No change in behavior (still fails every other time) was noted (test script attached). I also modified fw.elf to start with an infinite loop. No change in behavior was noted (still fails to flash via algorithm every-other time)

I tried the reset_config srst_only srst_nogate connect_assert_srst with fw.elf. No change in behavior (still fails every other time) was noted (test script attached). I also modified fw.elf to start with an infinite loop. No change in behavior was noted (still fails to flash via algorithm every-other time)

A few more details (using stlink_usb_v2_read_debug() to get values) In success case, while running the flash algorithm: stlink_usb_run(), xPSR.T==1 prior to clearing C_HALT and xPSR.T==0 after clearing C_HALT. In the failing case, xPSR.T==0 also prior to clearing C_HALT (theory: it immediately faults in this case). Multiple algorithm executions in a single flash write_image erase fw.elf work. Even though xPSR.T==0 on read back in stlink_usb_run(), on second algorithm execution xPSR.T==1 is seen prior...

A few more details (using stlink_usb_v2_read_debug() to get values) In all cases, while running the flash algorithm: stlink_usb_run(), xPSR.T==1 prior to clearing C_HALT and xPSR.T==0 after clearing C_HALT. In the failing case, xPSR.T==0 also prior to clearing C_HALT (theory: it immediately faults in this case). Multiple algorithm executions in a single flash write_image erase fw.elf work. Even though xPSR.T==0 on read back in stlink_usb_run(), on second algorithm execution xPSR.T==1 is seen prior...

A few more details (using stlink_usb_v2_read_debug() to get values) In all cases, while running the flash algorithm: stlink_usb_run(), xPSR.T==1 prior to clearing C_HALT and xPSR.T==0 after clearing C_HALT. In the failing case, xPSR.T==0 also prior to clearing C_HALT (theory: it immediately faults in this case). Multiple algorithm executions in a single flash write_image erase fw.elf work. Even though xPSR.T==0 on read back in stlink_usb_run(), on second algorithm execution xPSR.T==1 is seen prior...