Skip to main content
OKN
Associate III
Nov 11, 2026 6:15 AM UTC
Question

OP-TEE panic due to IAC exception ID 156 on custom STM32MP255F board

Hello,

I am currently porting OpenSTLinux to a custom board based on the STM32MP255F.

I successfully built all the required images, wrote them to an SD card, and attempted to boot the board. However, OP-TEE OS crashes just before U-Boot starts, with the following error:

E/TC:0 0 stm32_iac_itr:192 IAC exceptions [159:128]: 0x10000000
E/TC:0 0 stm32_iac_itr:197 IAC exception ID: 156
E/TC:0 0 Panic at /usr/src/debug/optee-os-stm32mp/4.0.0-stm32mp-r3.1/core/drivers/firewall/stm32_iac.c:212 <stm32_iac_itr>

As far as I understand, IAC exception ID 156 is related to RCC.

I checked the corresponding OP-TEE source code (stm32_iac.c) as well as the RCC-related Device Tree definitions, but so far I have not been able to determine what is causing the IAC exception.

 

Environment

- SoC: STM32MP255F
- Board: Custom board
- OpenSTLinux: openstlinux-6.6-yocto-scarthgap-mpu-v26.06.10
- OP-TEE: 4.0.0-stm32mp-r3.1
- STM32CubeMX: V6.18.1
- STM32Cube FW_MP2: V1.3.2

 

Device Tree background

The Device Tree used for this build is based on the one that I previously ported for this custom board using:

        openstlinux-6.6-yocto-scarthgap-mpu-v24.11.06

 

For the current build, I updated STM32CubeMX to V6.18.1 and selected FW_MP2 V1.3.2 .

I suspect that there may be some differences in the RCC, firewall/IAC, or resource isolation configuration between the previous and current OpenSTLinux releases.

Could you please help me clarify the following points?

1. What exactly does IAC exception ID 156 correspond to on the STM32MP255F?
2. Which RCC or firewall configuration could cause this exception during early OP-TEE initialization?
3. Are there any RCC/firewall Device Tree changes between the v24.11.06 and v26.06.10 OpenSTLinux releases that need to be reflected when porting an existing custom board?
4. Are there any STM32CubeMX-generated OP-TEE Device Tree settings that should be regenerated or updated rather than reused from the previous release?

Any suggestions for identifying the peripheral or register access that triggered this IAC violation would be greatly appreciated.

 

Below is the complete console log from power-on until the OP-TEE panic:

NOTICE: CPU: STM32MP255FAK Rev.Y
NOTICE: Model: >>>DDL<<< ddlskp board STM32MP255F-AK - openstlinux-6.6-yocto-scarthgap-mpu-v26.06.10
NOTICE: Reset reason: Power-on reset (por_rstn) (0x2035). Cold boot.
INFO: PMIC2 version = 0x11
INFO: PMIC2 product ID = 0x21
INFO: FCONF: Reading TB_FW firmware configuration file from: 0xe011000
INFO: FCONF: Reading firmware configuration information for: stm32mp_io
INFO: FCONF: Reading firmware configuration information for: stm32mp_fuse
INFO: Using SDMMC
INFO: Instance 1
INFO: Boot used partition fsbl1
NOTICE: BL2: v2.10-stm32mp2-r2.0(debug):devtool-patched(1cac55a1)
NOTICE: BL2: Built : 09:32:50, Nov 10 2026
INFO: BL2: Loading image id 26
INFO: Loading image id=26 at address 0xe041000
INFO: Image id=26 loaded: 0xe041000 - 0xe049650
INFO: BL2: Doing platform setup
INFO: RAM: LPDDR4 32bits 1220000kHz
INFO: Memory size = 0x80000000 (2048 MB)
INFO: BL2: Loading image id 1
INFO: Loading image id=1 at address 0xe000000
INFO: Image id=1 loaded: 0xe000000 - 0xe000326
INFO: FCONF: Reading FW_CONFIG firmware configuration file from: 0xe000000
INFO: FCONF: Reading firmware configuration information for: dyn_cfg
INFO: FCONF: Reading firmware configuration information for: risaf_config
INFO: RISAF2: No configuration in DT, use default
INFO: BL31 max size = 0x17000 (94208B)
INFO: BL2: Loading image id 3
INFO: Loading image id=3 at address 0xe000000
INFO: Image id=3 loaded: 0xe000000 - 0xe0169f8
INFO: BL2: Loading image id 19
INFO: Loading image id=19 at address 0x81fc0000
INFO: Image id=19 loaded: 0x81fc0000 - 0x81fc3a8c
INFO: BL2: Loading image id 4
INFO: Loading image id=4 at address 0x82000000
INFO: Image id=4 loaded: 0x82000000 - 0x8200001c
INFO: OPTEE ep=0x82000000
INFO: OPTEE header info:
INFO: magic=0x4554504f
INFO: version=0x2
INFO: arch=0x1
INFO: flags=0x0
INFO: nb_images=0x1
INFO: BL2: Loading image id 8
INFO: Loading image id=8 at address 0x82000000
INFO: Image id=8 loaded: 0x82000000 - 0x820f87b8
INFO: BL2: Loading image id 2
INFO: Loading image id=2 at address 0x84400000
INFO: Image id=2 loaded: 0x84400000 - 0x84419200
INFO: BL2: Loading image id 5
INFO: Loading image id=5 at address 0x84000000
INFO: Image id=5 loaded: 0x84000000 - 0x841c5b80
NOTICE: BL2: Booting BL31
INFO: Entry point address = 0xe000000
INFO: SPSR = 0x3cd
INFO: ARM GICv2 driver initialized
NOTICE: BL31: v2.10-stm32mp2-r2.0(debug):devtool-patched(1cac55a1)
NOTICE: BL31: Built : 09:32:50, Nov 10 2026
INFO: BL31: Initializing runtime services
INFO: BL31: Initializing BL32
I/TC: Early console on UART#2
I/TC:
I/TC: Embedded DTB found
I/TC: OP-TEE version: devtool-patched (gcc version 13.4.0 (GCC)) #3 Tue Nov 10 08:11:41 UTC 2026 aarch64
I/TC: WARNING: This OP-TEE configuration might be insecure!
I/TC: WARNING: Please check https://optee.readthedocs.io/en/latest/architecture/porting_guidelines.html
I/TC: Primary CPU initializing
I/TC: WARNING: All debug access are allowed
I/TC: Override the OTP 124: 0 to 0x18db6
I/TC: WARNING: Embeds insecure stm32mp_provisioning driver
E/TC:0 0 stm32_iac_itr:192 IAC exceptions [159:128]: 0x10000000
E/TC:0 0 stm32_iac_itr:197 IAC exception ID: 156
E/TC:0 0 Panic at /usr/src/debug/optee-os-stm32mp/4.0.0-stm32mp-r3.1/core/drivers/firewall/stm32_iac.c:212 <stm32_iac_itr>
E/TC:0 0 TEE load address @ 0x82000000
E/TC:0 0 Call stack:
E/TC:0 0 0x82007f30
E/TC:0 0 0x82043bec
E/TC:0 0 0x8202da58
E/TC:0 0 0x82041718
E/TC:0 0 0x82014368
E/TC:0 0 0x820046ac

Best Regards,
--
okn
 

2 replies

Christophe Guibout
ST Technical Moderator
Nov 12, 2026 8:51 AM UTC

Hello ​@OKN,

I would recommand to enable debug logs in Op-Tee to identify where issue comes from : wiki link.

Nevertheless, I would suggest to check if the I²C of the PMIC is secured : In a normal boot, the log after:

I/TC: WARNING: Embeds insecure stm32mp_provisioning driver

Should be (with my STM32MP257F-EV1 board) :

I/TC: PMIC STPMIC REFID:2.@ V1.1

So this makes me think the PMIC initialization fails, so I would check that the RIF_RCC_RESOURCE providing the I2C you selected for the PMIC is RIF_SEC:

  • The RIF_RCC_RESOURCE number can be found in clk-stm32mp25.c

BR,

Christophe

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
OKN
OKNAuthor
Associate III
Nov 12, 2026 9:43 AM UTC

Hello, ​@Christophe Guibout 

Thank you for your reply.

I created a project for the STM32MP257F-DK using STM32CubeMX, compared the .ioc file with the generated device tree,
and made various configuration adjustments—after which Linux booted successfully.

Main changes:

- Adjusted the RIF settings to match -DK
- Added `st,ck_gpu{}` to `&rcc{}`
- Set `pmic2{}` in `&i2c7{}` to match the -DK configuration

I also fixed the PMIC-related issues you pointed out.

This time, I was able to resolve the issue by modifying the device tree, but I plan to proceed with my work while also referring to the optee debugging methods on the wiki.


Best Regards,
--
okn