Hi! On Mon, Apr 17, 2023 at 02:00:03PM +0200, kristof.mul...@telenet.be wrote: > > The release pages mention the commit id used, you can try to take > > a look at the changes in the given period, perhaps you can > > identify something related to your problem. > > I'm afraid that's beyond my capabilities. I don't have any knowledge > of the OpenOCD source code. I'd simply get lost.
git bisect start; git bisect bad v0.11.0; git bisect good v0.10.0 https://www.git-tower.com/learn/git/faq/git-bisect/ and you can pin-point the offending commit pretty fast since you have an easy way to reproduce it, without any knowledge of the code base at all. I do not have Nucleo F3 board with me :( -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com
