Failed pre launch debugging with STM32CubeIDE

[rdmikkelsen]

I am trying to debug a basic project on a STM32MP257F-DK board, and am running into an issue. This is the text of the error I get every time I debug: 

'Launching <project>_CM33 Debug' has encountered a problem.
Error in final launch sequence:
Failed pre launch

========================

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..

Building results in no errors. I have verified that there is space and write access for the location it mentions, and I can see that the .elf file for the project gets written there. I have also gone through all the steps here without an issue: https://wiki.st.com/stm32mpu/wiki/STM32MP25_Discovery_kits_-_Starter_Package. I can also ssh into it without a problem. I have tried it on both Windows 11 and Ubuntu 24.04. 

A couple other people have brought up similar issues, but their solutions did not let me get past this error. I had tried the solutions here and here, but there was no difference (changing the remote connections settings no difference, and there is only one qualifier I can choose). 

Is there anything else I can try to get past this error message?

[Erwan SZYMANSKI]

Hello @rdmikkelsen ,
Did you try to follow this wiki page ? 
https://wiki.st.com/stm32mpu/wiki/Getting_started/STM32MP2_boards/STM32MP257x-DK/Develop_on_Arm_Cortex-M33/Modify,_rebuild_and_reload_the_firmware

Make sure to pay attention to all the details in the IDE configuration steps for build, debug session and so on. For example, the firmware needs to be signed.

Kind regards,
Erwan.

[rdmikkelsen]

Thank you for the response. I went through the steps on that page again, and saw that my issue was that another device other than /dev/ttyACM0 was set as the preferred device, even though no other device was present, and because of that it was unable to connect. It's odd that it was still able to write to it just fine without that set, but I am no longer getting that error after the change.