On Sat, Aug 12, 2023 at 6:38 AM Tomas Vanek
wrote:
> ...
> The part of openocd.cfg up to here is +- standard.
>
> The following part is a folklore added by zephyr project, which changes
> OpenOCD
> startup behaviour and gdb attach. TBH I see no reason why they need it for.
>
> $_CHIPNAME.cpu0 con
Hi Michael,
the fragment of OpenOCD log shows that CPU0 (M7 core) cannot be halted.
What is programmed in M7 startup?
On 11/08/2023 22:34, Banducci, Michael wrote:
I started based on the example OpenOCD configs for the STM32H745 and
H747 and attempted to build a configuration file (see below)
Have you tried using the ST fork of OpenOCD?
https://github.com/sysprogs/openocd-st/
Is this of any use?
https://visualgdb.com/tutorials/arm/stm32/multicore/startup/
Hi all,
I'm attempting to get Zephyr working on the M4 core of an STM32H755. I'm using
an ST-Link v3set on Windows 11 with OpenOCD v. 0.12.0.
I am able to flash a compiled binary via OpenOCD, but I have so far been unable
to get to a place where I can debug the second core. I started based on t
