> On 17 Apr 2023, at 14:47, Kristof Mulier > <kristofmul...@users.sourceforge.net> wrote: > > We have prepared two projects for this demonstration: > > • f303-working: This project works with all the OpenOCD versions - up > to and including OpenOCD 0.12.0 > • f303-failing: This project works with OpenOCD 0.10.0, but not with > OpenOCD 0.11.0 and 0.12.0.
This approach is a bit unusual; since you have a binary that can be flashed with all versions and one that fails with the latest two versions, assuming that all other things are the same, the natural question that comes to my mind is what differs between the two binaries? Did you inspect the size and layout of the sections in the elf files and check if they are valid for your device? readelf or objdump may provide some help. Another thing to try would be to flash the failing binary with the STM tools, and watch for errors/warnings messages, perhaps you can get some hints on what might be wrong. The fact that your binary was fine with 0.10 and fails with the newer releases does not automatically imply a regression, it can also be explained by a problem with your binary and an extra validation test that was added in recent OpenOCDs, not accompanied by a helpful error message. Only if you have the confirmation that the binaries are valid and can be flashed with a professional tool, (either provided by the silicon vendor or by some acknowledged third party like SEGGER), you can expect someone to consider a bug in OpenOCD. Liviu
