FAQs
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

STM32_Programmer_CLI "Error: Failed to Power ON the board !" with STM32N6

cgnd_chris
Associate II

‎2025-12-10 9:43 PM

When I attempt to power cycle a STM32N6570-DK or NUCLEO-N657X0-Q board via the STM32_Programmer_CLI, I get the following error message:

Error: Failed to Power ON the board ! 

Here is the full log:

❯ STM32_Programmer_CLI --power off index=0 --power on index=0
-------------------------------------------------------------------
STM32CubeProgrammer v2.21.0 
-------------------------------------------------------------------

Power OFF...
Drives the target power pin out of the (onboard) ST-Link.
Info: Power ON/OFF maybe not available on your Board [also not available on standalone probes]
Power OFF the board finished with success !

Power ON...
Drives the target power pin out of the (onboard) ST-Link.
Info: Power ON/OFF maybe not available on your Board [also not available on standalone probes]
Error: Failed to Power ON the board ! 

 

However, when I attempt the same command on other Nucleo boards, I don't get this error. Here's the same command run on the NUCLEO-H533RE:

❯ STM32_Programmer_CLI --power off index=0 --power on index=0
-------------------------------------------------------------------
STM32CubeProgrammer v2.21.0 
-------------------------------------------------------------------

Power OFF...
Drives the target power pin out of the (onboard) ST-Link.
Info: Power ON/OFF maybe not available on your Board [also not available on standalone probes]
Power OFF the board finished with success !

Power ON...
Drives the target power pin out of the (onboard) ST-Link.
Info: Power ON/OFF maybe not available on your Board [also not available on standalone probes]
Power ON the board finished with success !
0 Kudos
3 REPLIES 3
cgnd_chris
Associate II

‎2025-12-10 9:45 PM

FYI, ST-LINK FW is V3J16M8 for all boards.

0 Kudos
cgnd_chris
Associate II

‎2025-12-10 10:57 PM

The original post above is what I was seeing on macOS.

When I switch to Windows, I get a different set of errors...

I get the following on the STM32N6570-DK or NUCLEO-N657X0-Q boards:

❯ STM32_Programmer_CLI.exe --power off index=0 --power on index=0
-------------------------------------------------------------------
STM32CubeProgrammer v2.21.0
-------------------------------------------------------------------

Power OFF...
Drives the target power pin out of the (onboard) ST-Link.
Info: Power ON/OFF maybe not available on your Board [also not available on standalone probes]
Error: Failed to Power OFF the board. Cannot getting device information !
Power ON...
Drives the target power pin out of the (onboard) ST-Link.
Info: Power ON/OFF maybe not available on your Board [also not available on standalone probes]
Error: Failed to Power ON the board !

 

On Windows with the NUCLEO-H533RE board:

❯ STM32_Programmer_CLI.exe --power off index=0 --power on index=0
-------------------------------------------------------------------
STM32CubeProgrammer v2.21.0
-------------------------------------------------------------------

Power OFF...
Drives the target power pin out of the (onboard) ST-Link.
Info: Power ON/OFF maybe not available on your Board [also not available on standalone probes]
Error: Failed to Power OFF the board. Cannot getting device information !
Power ON...
Drives the target power pin out of the (onboard) ST-Link.
Info: Power ON/OFF maybe not available on your Board [also not available on standalone probes]
Power ON the board finished with success !

 

0 Kudos
Kouthair
ST Employee

‎2025-12-24 6:24 AM

Hello there Cgnd_Chris,

Thank you for reporting this issue.
We have reproduced this error and we'll report this to the dedicated team (internal ticket number: 224339).
PS: Ticket number: 224339 is an internal tracking number and is not accessible or usable by customers.

Kouthair

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
Top