Dear ST team,
We have verified the following issues on the STM32MP257-EV1 platform, following the official guidance:
While creating a new project using STM32CubeIDE for the MP2 series, we encountered several issues and inconsistencies:
1. OpenAMP code generation failure
When enabling OpenAMP middleware via STM32CubeIDE, the tool does not generate the expected or necessary source files correctly, resulting in incomplete or non-functional projects.
2. Unexpected resource_table requirement
Even when creating a default Cortex-M33 project (non-secure) with minimal settings, the build process seems to expect a resource_table, which is typically associated with Linux-side communication. However, the generated ELF and source files are not intended for OpenAMP communication, causing confusion.
3. Project structure mismatch
The automatically generated project structure from STM32CubeIDE differs significantly from the official reference project provided in the wiki documentation above. This discrepancy makes it difficult to align custom firmware with the example workflows or integrate with the Linux remoteproc framework.
