STM32MP2 MCU DEBUG

[Enes_]

Hi Community Members,

We are using a MYB-LD25X development board and are able to boot Linux successfully on the A-core. However, we are facing issues when debugging Cortex-M33 code generated by STM32CubeMX. Although we assign the required peripherals exclusively to the M33 core, the initialization code generated by CubeMX does not work as expected. When the M33 firmware starts, it consistently enters a HardFault. Has anyone experienced a similar issue with the MYB-LD25X / STM32MP2 platform? Any guidance on correct peripheral assignment, resource management (RIF/ResMgr), or CubeMX configuration for M33 debugging would be greatly appreciated.

Thank you in advance.

[Kevin HUBER]

Hello @Enes_ ,

It will be hard to help you without more detail. Which peripheral is concerned and what is the RIF configuration than you applied for it?

An HardFault error in this context is often due to a wrong RIF configuration of the peripheral or its clock.

This can be an IAC error due to a peripheral not well assigned or a SERC error due to a missing clock.

The most interesting wiki page on this topic is this one: https://wiki.st.com/stm32mpu/wiki/STM32MP2_firewall_configuration

and especially this part: https://wiki.st.com/stm32mpu/wiki/STM32MP2_firewall_configuration#RIF_attributes_of_OSTL_software_components

which summarize the RIF configuration to apply for each context.

Hope it helps,

BR,

Kevin

[PatrickF]

Hi @Enes_ 

Debugging Cortex-M33 code in step by step could help to identify in which situation an hardfault is generated.
This page could help for settings CubeIDE: 

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 

Regards,