Re: Preparing for OpenOCD v1.0.0-rc1

2025-05-23 Thread Brandon Martin
On 5/23/25 06:16, Antonio Borneo wrote: Said that, I invite you all to report any feature still pending in Gerrit that you absolutely want to have in v1.0.0. It would be nice if the flexspi support I've had pending could get merged. I did recently submit a revised patch addressing all outsta

Target scriptable events for non-gdb flash start/end

2025-05-23 Thread Brandon Martin
It would be handy for the FLEXSPI if there were target events for non-GDB initiated flash erase start/end and write start/end since it would allow deferring disabling of watchdogs, which are chip-specific, to the relevant TCL scripts. Is that something that folks would be amenable to me adding

RC1 and open changes/pull request

2025-05-23 Thread Liam.Fletcher
Hello, we see that an RC1 is coming soon. We have some pull requests open for drivers that will probably not make it in on time, however the configuration files for the target is ready and can be used with already upstreamed drivers such as Olimex, etc for software debug. What we would like to

RC1 and open changes/pull request

2025-05-23 Thread Liam.Fletcher
Hello, we see that an RC1 is coming soon. We have some pull requests open for drivers that will probably not make it in on time, however the configuration files for the target is ready and can be used with already upstreamed drivers such as Olimex, etc for software debug. What we would like to

Re: Preparing for OpenOCD v1.0.0-rc1

2025-05-23 Thread Liviu Ionescu
> On 23 May 2025, at 13:16, Antonio Borneo wrote: > > Hello, > > we are going to tag OpenOCD v1.0.0-rc1 in around one month. f I remember right, the Raspberry Pico project also had an openocd fork. It would be great to also upstream the changes in that fork, since the pico is a very popula

Preparing for OpenOCD v1.0.0-rc1

2025-05-23 Thread Antonio Borneo
Hello, we are going to tag OpenOCD v1.0.0-rc1 in around one month. It will follow a period of code freeze, during which only patches for bug fixes will be merged. The release v1.0.0 is expected before the end of the year. Why v1.0.0 ? Because OpenOCD is 20 years old, and at such an age it's matur