Twister fails for STM32H743 when running on pipeline but locally it passes

[harshrmistry-eaton]

Hi, I have a machine where our pipeline tests are setup. When I trigger a twister run on the machine, it fails on the pipeline with Device issue (Flash error?). Locally it passes on my machine without any issues. I am running twister test for Nucleo-H743ZI2 board. Below is the snapshot of the error:

I am using Zephyr 3.6.

Below is the command used in the pipeline:
python scripts/twister --device-testing --device-serial COM3 -p nucleo_h743zi -T <path to the root directory for my examples> -O <path to a directory> -c

[FRASTM]

Hi @harshrmistry-eaton
I would recommend to update the stlink of your nucleo_h743zi board with the cube programmer.
Then you could check if your twister and your west flash are using the same runner.

[FRASTM]

I found this:
with STLinkUpdate you can use the following command line:

• check the current fw version on your board : java -jar STLinkUpgrade.jar -checkVer
• update the fw version of your board (if a more recent one is detected) : java -jar STLinkUpgrade.jar -update

[harshrmistry-eaton]

@FRASTM The issue is quite random. It doesn't happen locally but only on pipeline. But our machines are identical. The only difference is some have Windows 10 and some have Windows 11. The st-link versions were different for the respective boards connected to our machines. The machines don't have STM32CubeProgrammer installed. Only one machine has ST-LINK Utility installed since that's a debug machine.

It would be helpful if someone from ST could help with the minimum st-link firmware version required for twister to run. We are currently on Zephyr 3.6.0. Also, does twister use openocd while flashing? Is it necessary to have STM32CubeProgrammer installed on the machines?

[FRASTM]

If the runner is openocd (that's the case with board.cmake), flashing is done with openocd, no need for stm32CubeProgrammer
However the openocd is detecting the STLink which is present on the target board. For example:

Open On-Chip Debugger 0.11.0+dev-00726-ge2b6f5655 (2023-09-22-14:29)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
init
Info : STLINK V3J13M4 (API v3) VID:PID 0483:374E

[harshrmistry-eaton]

@FRASTM We upgraded all H7 boards to V3J15M6 version. We again started facing this issue.

I have posted in ST forum as well but haven't got any concrete response. Please help regarding this.

[FRASTM]

I guess your twister has openocd as runner, What are the build.log and device.log when failing ?

Can you also try with pyocd as runner for twister scripting