Re: [OpenOCD-user] problem with openocd 0.12.0

[Paul F. <fer...@gm...>]

Hey Tommy,

Your guess was spot-on, thank you!

On Wed, Mar 20, 2024 at 04:49:22PM +0000, Tommy Murphy wrote:
> I really meant the OpenOCD logs from running it standalone from the command
> line. Not the VSCode (?) log that seems to have other stuff interspersed. My
> hypothesis is that maybe whatever string/pattern that the VSCode debug
> configuration uses to detect that OpenOCD has started successfully is detected
> for 0.10.0 but not for 0.12.0 due to changes in between these two releases? 

>From v0.11.0-412-gba1061fe1 commit message:

Giving the example of STM32WL55x the examine log is the following:

Info : stm32wlx.cpu0: hardware has 6 breakpoints, 4 watchpoints
Info : stm32wlx.cpu1: hardware has 4 breakpoints, 2 watchpoints

After this change the examine log becomes:

Info : stm32wlx.cpu0: Cortex-M4 r0p1 processor detected
Info : stm32wlx.cpu0: target has 6 breakpoints, 4 watchpoints
Info : stm32wlx.cpu1: Cortex-M0+ r0p1 processor detected
Info : stm32wlx.cpu1: target has 4 breakpoints, 2 watchpoints


Found this by doing
$ git log -S ": hardware"

--
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fer...@gm...