Issue with RCC on flashing a blank project for STM32MP257F-DK

[MrVym]

Hello,
I have a stm32mp257f-dk and I would like to create an STM32Cube project for my board.
To be able to use the board, I have put in the eMMC the tsv file provided in the starter pack:
`en.FLASH-stm32mp2-openstlinux-6.6-yocto-scarthgap-mpu-v24.12.05/stm32mp2-openstlinux-6.6-yocto-scarthgap-mpu-v24.12.05/images/stm32mp2/flashlayout_st-image-weston/optee/FlashLayout_emmc_stm32mp257f-dk-optee.tsv`

My project aims to use the OpenAMP stack. I was able to flash the example which works very well but it does not have a .ioc file (which is necessary for my project).
So I used the STM32CubeMX Board Selector to generate an empty project.
First problem (screen 1), CubeMX tells me that DSIHOST, MDF1, and RCC are in conflict.
Since I don't need the Digital Filter and the screen, I disabled them.
I still have the RCC conflict. My code compiles but when flashing the project on the Cortex-M33, it crashes and here are the logs:
```
[ 34.029164] vddio3: disabling
[ 34.029233] vddio4: disabling
[ 34.029495] vdda18adc: disabling
[ 34.032767] v5v_vconn: disabling
[ 62.456994] ucsi-stm32g0-i2c 1-0035: i2c write 35, 08 error: -110
[ 62.481724] remoteproc remoteproc0: stopped remote processor m33
[ 65.806346] remoteproc remoteproc0: powering up m33
[ 65.892818] remoteproc remoteproc0: Booting fw image Project_PFE_CM33.elf, size 3320304
[ 65.895709] remoteproc remoteproc0: header-less resource table
[ 65.901623] remoteproc remoteproc0: no resource table found for this firmware
[ 65.908885] remoteproc remoteproc0: header-less resource table
[ E/TC:1 stm32_iac_itr:192 IAC exceptions [159:128]: 0x10000000
E/TC:1 stm32_iac_itr:197 IAC exception ID: 156
E/TC:1 Panic at /usr/src/debug/optee-os-stm32mp/4.0.0-stm32mp-r1/core/drivers/firewall/stm32_iac.c:212 <stm32_iac_itr>
E/TC:1 TEE load address @ 0x82000000
E/TC:1 Call stack:
E/TC:1 0x82007ed8
E/TC:1 0x82041b44
E/TC:1 0x8202c2c0
E/TC:1 0x8203f678
E/TC:1 0x82013cf4
E/TC:1 0x820017dc
I/TC: Halting CPU 0

```
I checked the IAC exception 156 in the documentation and indeed it is related to RCC (screen 2). I see some logs inside the `/sys/kernel/debug/stm32_firewall/` directory.
I don’t really know what to do, I feel like I’m not heading in the right direction.
Would you have any idea knowing that I have not modified any code yet?

[Christophe Guibout]

Hi @MrVym,

It seems the M33 firmware executes a piece of code related to RCC which is forbiden by the RIF configuration.

I would suggested to find which RCC access generates the IAC (with debugger, or put under comment RCC related code untill issue is resolved).

Then, update the access related to the RCC RIF resource number (table 183 of the Reference Manual) in op-tee configuration (see &rcc entry in stm32mp257f-dk*-rif.dtsi DT configuration).

BR,

Christophe