Hello,
For a new project, we are evaluating the suitability of the STM32MP257 SoC. Using an STM32MP257F-DK board, the Starter Pack and the STM32Cube_FW_MP2_V1.2.0 examples,
we successfully tested the M33 core controlling several peripherals. However, we've encountered a persistent issue with I2C8.
With the default Starter Pack Linux image and no modifications to the I2C_TwoBoards_ComIT example project, the M33 core fails to initialize I2C8.
This failure leads to a Linux watchdog reset. The problem occurs specifically within the HAL_I2CEx_ConfigAnalogFilter() function when attempting to disable I2C8 (__HAL_I2C_DISABLE(hi2c)).
Our debugging efforts indicate that after I2C8 is enabled in HAL_I2C_Init() (__HAL_I2C_ENABLE(hi2c)), any subsequent reads or writes to the I2C8 CR1 register trigger the issue.
We have successfully tested I2C1 without any initialization problems. While we have experimented with modifications to the Linux device tree, we haven't observed any improvements.
Could you offer any suggestions regarding what might be causing this issue or what we might be overlooking?
Kind regards
