Error using CubeIDE ro run an example application for the STM32MP257F-EV1

[Carson]

Hello,

 

I am currently trying to being up the STM32MP257F-EV1 development board and running into a problem. I am using CubeIDE following the following guide: https://wiki.st.com/stm32mpu/wiki/Getting_started/STM32MP2_boards/STM32MP257x-EV1/Develop_on_Arm%C2%AE_Cortex%C2%AE-M33/Modify,_rebuild_and_reload_the_firmware.

Specifically I am on step 8 when you have to create the run and debug configurations. I followed the guide and created the configurations correctly but now when I run the example application (OpenAMP_ttyecho_CM33_NonSecure) I get the following error:

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

 

Any help would be greatly appreciated. Thanks!

 

Carson

[Kevin HUBER]

Hello @Carson ,

 

by looking at the error, I think you are not trying to launch the signed image.

If you follow the step 8, you can see that the application to launch is: "OpenAMP_TTY_echo_CM33_NonSecure_sign.bin".

 

It is specified at the second line of the step8

• With the arrow right of the hammer sign, choose the project configuration with "_sign" in the name, then it is going to build it

To verify what was copied and if something was really copied on the target, please can you go on the target and share with me the names of all the files in "/lib/firmware".

 

Best Regards,

Kevin

[Carson]

Hello Kevin, 

 

I am trying to launch the signed image. I set up my run configuration as follows: 

Project:

OpenAMP_TTY_echo_CM33_NonSecure

C/C++ Application:

CA35TDCID_m33_sign/OpenAMP_TTY_echo_CM33_NonSecure_sign.bin

Build Configuration:

Use Active

And use workspace settings is checked while Enable/Disable auto build are both unchecked. 

 

When I go into the file of /lib/firmware the files I see are LICENCE.cypress_bcm4343, WHENCE, regulatory.db.p7s, OpenAMP_TTY_echo_CM33_NonSecure_sign.bin, brcm, rtl_nic, USBPD_DRP_UCSI_CM33_NonSecure.elf, regulatory.db

 

Thanks,

Carson

[BtEddy]

Hello,

I also had the same issue with 

 

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

 

By following these steps, I got it running.

I assume that both configurations, OpenAMP_TTY_echo_CM33_NonSecure_Run and OpenAMP_TTY_echo_CM33_NonSecure_Debug, have been created.

 

Run Configuration

- Select OpenAMP_TTY_echo_CM33_NonSecure project

- Click on 'Run Configurations...'

- Select OpenAMP_TTY_echo_CM33_NonSecure_Run configuration

- Click on 'Search Project...' at the 'Main' tab for selection the C/C++ Application. 

- In the 'Program Selection' Window select 

Binaries: the 'OpenAMP_TTY_echo_CM33_NonSecure.elf'

Qualifier: armle - /OpenAMP_TTY_echo_CM33_NonSecure/CA35TDCID_m33_ns_sign/OpenAMP_TTY_echo_CM33_NonSecure.elf

 

Attention: It must be selected the Qualifier with '_sign' !

- Configure the 'Startup' tab according step 8 in 'Modify, rebuild and reload the firmware' Wiki (Download:true Load symbols:true)

 

Debug Configuration

- Select OpenAMP_TTY_echo_CM33_NonSecure project

- Click on 'Debug Configurations...'

- Select OpenAMP_TTY_echo_CM33_NonSecure_Debug configuration

- Click on 'Search Project...' at the 'Main' tab for selection the C/C++ Application. 

- In the 'Program Selection' Window selct (same as for the 'Run Configuration')

Binaries: the 'OpenAMP_TTY_echo_CM33_NonSecure.elf'

Qualifier: armle - /OpenAMP_TTY_echo_CM33_NonSecure/CA35TDCID_m33_ns_sign/OpenAMP_TTY_echo_CM33_NonSecure.elf

- Configure the 'Startup' tab according step 8 in 'Modify, rebuild and reload the firmware' Wiki (Download:false Load symbols:true)

 

----------------------

 

I'm not sure if this is the way STM intended it. I would therefore appreciate if @Kevin HUBER  could check this.

 

Thanks

 

[Carson]

Hi BtEddy, That worked! Thank you!

[Maurawani]

I run into the same problem by creating a new project with default settings. Are there any instructions to deal with the problem and what are the reasons causing these error messages? I also added a postbuild where sign the .elf file with the default key. Are there any other steps that have to be considered?

 

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

 

My second question is:

What is the difference between those two directories /CA35TDCID_m33_ns_sign/ and /CA35TDCID_m33_ns/

Is it only the signature in postbuild? In my point of view the output of the ..._sign.bin is not used for downloading to the eval_board, it is only created.

 

 

Any hint would help me a lot. Thank you in advance.