STM32MP257F-DK CM33 peripheral initialization crashes A35

[partha_sarathi1000]

I generated the M33 code using CubeIDE by following the lab manual.

During the driver initializations:
MX_ADC1_Init();
MX_I2C1_Init();
MX_ICACHE_Init();
MX_RTC_Init();

The A35 halts CPU1 and resets after sometime.

E/TC:0 stm32_iac_itr:192 IAC exceptions [159:128]: 0x10000000
E/TC:0 stm32_iac_itr:197 IAC exception ID: 156
E/TC:0 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:0 TEE load address @ 0x82000000
E/TC:0 Call stack:
E/TC:0 0x82007ed8
E/TC:0 0x82041b44
E/TC:0 0x8202c2c0
E/TC:0 0x8203f678
E/TC:0 0x82013cf4
E/TC:0 0x820017dc
I/TC: Halting CPU 1

Unfortunately I failed to create astable functional M33 for my MPU project yet. Are there no proper manual of code generation and configuration?

[partha_sarathi1000]

Attached is the ioc file.

[Olivier GALLIEN]

Hi @partha_sarathi1000 ,

You are facing issue related to RIFF configuration. 

If you generate project using CubeMX you might carefully consider the RIFF configuration pane. ( RIFSC for peripheral assignement, RISAB and RISAF for memory ) 

Refer the related documentation on Wiki and in RM : 

https://wiki.st.com/stm32mpu/wiki/RIFSC_internal_peripheral

https://wiki.st.com/stm32mpu/wiki/RISAB_internal_peripheral

https://wiki.st.com/stm32mpu/wiki/RISAF_internal_peripheral

Olivier 

[partha_sarathi1000]

Thanks @Olivier GALLIEN for the reply.

But did config RIF as per manual.

What I have found that its crashing during GPIO RCC enable macros, like:
__HAL_RCC_GPIOI_CLK_ENABLE();

So in any peripheral initialization, wherever there is any GPIO RCC clock enable statement in its respective _MspInit() function, I commented them out and then the initialization passed without any issue.

I tested UART is working with that. But I don't think its a solution.

Regards
Partha