Skip to main content
Associate
October 21, 2026
Solved

Can't complete pre-launch phase in CubeIDE

Hello everyone! I am following the tutorial on st wiki on how to work with STM32MP257F-DK board. Everything was going pretty good, until the “Develop on Arm® Cortex®-M33” part. This is a really important part for me, because the main reason I chose this MPU is because of the additional low-power cortex M33 and M0 co-processors. The part where I am stuck is “Modify, rebuild and reload the firmware for A35-TD flavor”. I have successfully built the “*_sign.bin” file and populated the board with it by using the “Run_Configuration” button. However past 78% the process stops and shows an error that states:

“Error in final launch sequence:

Failed pre launch
Failed pre launch
Firmware remoteproc load failed, please:


     1. make sure that /lib/firmware on your target has space
     2. make sure that /lib/firmware has write access

   > you can open a Console View for this..”

In the STM32MP2 system a log of these messages are displayed:

“

[ 2321.306087] remoteproc remoteproc0: powering up m0 
[ 2321.307801] remoteproc remoteproc0: Image is corrupted (bad magic)           
[ 2321.311511] remoteproc remoteproc0: Boot failed: -22

“

I tried re-flashing the sd card with the correct .tsv file “FlashLayout_sdcard_stm32mp257f-dk-ca35tdcid-ostl-m33-examples-optee.tsv”, re-added the CubeIDE project and even re-did the “Run_Configuration”. I also saw that the “*_sign.bin” file is added to the /usr/local/projects/…/lib/firmware directory instead of the /lib/firmware directory, however after adding the “_sing.bin” file in the latter directory myself, nothing changed. I am lost on what to do next, hence why I am asking for help. Any advice is appreciated, thanks!
 

 

John_PexBest answer
Associate
October 22, 2026

Just figured it out, had to change the network configuration in “Window” → “Preferences...” → “Remote Development” → “Remote Connections” to password based authentication (by default leave it empty) and in advanced settings uncheck the “Use login shell” option as it is not needed for SSH connection, because you cannot access the shell if you are not root (check mate).

Hope this helps somebody and you won’t have to go out of your mind for 3 days and try everything humanly possible to make CubeIDE work properly (:

1 reply

John_PexAuthorBest answer
Associate
October 22, 2026

Just figured it out, had to change the network configuration in “Window” → “Preferences...” → “Remote Development” → “Remote Connections” to password based authentication (by default leave it empty) and in advanced settings uncheck the “Use login shell” option as it is not needed for SSH connection, because you cannot access the shell if you are not root (check mate).

Hope this helps somebody and you won’t have to go out of your mind for 3 days and try everything humanly possible to make CubeIDE work properly (: