NUCLEO-H743ZI2 firmware upload

[kucza]

Hi. I’m trying to work with NUCLEO-H743ZI2. But there is a problem with uploading/debuging. It has ST-Link v3 onboard and FW is up to date. It looks like theere is a problem with resetting target MCU. When i try Embedded Project and debug using OpenOCD the TEST button gives below output. But if I manualy press/relese reset button on nucleo board then it pass TEST and can connect to MCU.

C:\Users\info\AppData\Local\VisualGDB\EmbeddedDebugPackages\com.sysprogs.arm.openocd\bin\openocd.exe -c "gdb_port 62444" -c "telnet_port 62442" -f interface/stlink.cfg -f target/stm32h7x_dual_bank.cfg -c init -c "reset init" -c "echo VisualGDB_OpenOCD_Ready"
Open On-Chip Debugger 0.11.0 (2021-11-18) [https://github.com/sysprogs/openocd]
Licensed under GNU GPL v2
libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "hla_swd". To override use 'transport select <transport>'.
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
Info : clock speed 1800 kHz
Info : STLINK V3J9M3 (API v3) VID:PID 0483:3754
Info : Target voltage: 3.282704
Error: init mode failed (unable to connect to the target)

I can not check OpenOCD ST fork becouse it gives notification that stm32h7x_single_bank.cfg is missing:

VisualGDB version: 5.6.106.4622
------------------ System.IO.FileNotFoundException ------------------
System.IO.FileNotFoundException: Could not find file 'C:\Users\info\AppData\Local\VisualGDB\EmbeddedDebugPackages\com.sysprogs.arm.openocd.st\share\openocd\scripts\target\stm32h7x_single_bank.cfg'.
File name: 'C:\Users\info\AppData\Local\VisualGDB\EmbeddedDebugPackages\com.sysprogs.arm.openocd.st\share\openocd\scripts\target\stm32h7x_single_bank.cfg'
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.StreamReader..ctor(String path, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize, Boolean checkHost)
at System.IO.StreamReader..ctor(String path, Encoding encoding)
at System.IO.File.InternalReadAllLines(String path, Encoding encoding)
at System.IO.File.ReadAllLines(String path)
at OpenOCDPackage.OpenOCDDebugController.StartGDBStub(IDebugStartService startService, DebugStartContext context)
at VisualGDB.Common_GUI.WPF.DebugMethodSettingsControl.Controller.TestDebugConnection()
at VisualGDB.Common_GUI.WPF.DebugMethodSettingsControl.ConnectionTest_Click(Object sender, RoutedEventArgs e)
trace=[System.IO.__Error.WinIOError:518, System.IO.FileStream.Init:928, System.IO.FileStream..ctor:14, System.IO.StreamReader..ctor:83, System.IO.StreamReader..ctor:0, System.IO.File.InternalReadAllLines:6, System.IO.File.ReadAllLines:14, OpenOCDPackage.OpenOCDDebugController.StartGDBStub:555, VisualGDB.Common_GUI.WPF.DebugMethodSettingsControl+Controller.TestDebugConnection:286, VisualGDB.Common_GUI.WPF.DebugMethodSettingsControl.ConnectionTest_Click:25]

There is definitly something wrong with reset method. Even if I use STM32CubeProgrammer it can only connect with target if Reset mode is set to Hardware reset.

[support]

Hi,

The “could not find file” error happens because the regular OpenOCD and the ST fork use slightly different script names. You can view the available scripts by enabling the raw view in the device selector under VisualGDB Project Properties -> Debug Settings.

If you are able to connect to the device while holding reset, please try checking the “connect under reset” checkbox in the OpenOCD settings. This way it should work similarly to your current STM32CubeProgrammer configuration.

[Author]

Posts