Skip to main content
Associate III
August 2, 2025
Solved

STM32CubeMX 6.15.0 claims "DCMI and PSSI are in exclusive choice" for STM32H753ZITx (and others).

  • August 2, 2025
  • 1 reply
  • 319 views

I cannot enable DCMI for STM32H753ZIT in STM32CubeMX version 6.15.0.

PhucXDoan_0-1754107193106.png

 

I'd assume DCMI can be indeed used and that this is just a bug on CubeMX's part, but I'd like to verify before I do any orders.

 

Related:

https://community.st.com/t5/stm32-mcus-products/minimum-clock-speed-and-enabling-pssi-problem/td-p/709772

https://community.st.com/t5/stm32cubeide-mcus/dcmi-cannot-be-used-on-the-latest-revision-cubeide-1-15-1-with/td-p/691876

Best answer by PhucXDoan

Now would you believe me if I told you that I slept and woke up to the DCMI option available now?

PhucXDoan_0-1754145166587.png

I think what I did was try to generate code so that STM32CubeMX would download the MCU series package (e.g. STM32CubeH7) like the related thread vaguely mentioned. I then retried configuring the MCU, but the DCMI option was still grayed out. I restarted STM32CubeMX, still the same thing. I guess I didn't try *restarting* my entire computer, but I did that for virtual machine reasons and I guess now DCMI is working fine.

Glad I'm the person that's finally documenting this wacky behavior.

1 reply

Associate
August 2, 2025

Sometimes (especially when it comes to boards and not bare MCUs/MPUs) , some peripherals can be used simultaneously but require more advanced configurations, which CubeMx has yet to support. (At least from my experience) 

PhucXDoanAuthorBest answer
Associate III
August 2, 2025

Now would you believe me if I told you that I slept and woke up to the DCMI option available now?

PhucXDoan_0-1754145166587.png

I think what I did was try to generate code so that STM32CubeMX would download the MCU series package (e.g. STM32CubeH7) like the related thread vaguely mentioned. I then retried configuring the MCU, but the DCMI option was still grayed out. I restarted STM32CubeMX, still the same thing. I guess I didn't try *restarting* my entire computer, but I did that for virtual machine reasons and I guess now DCMI is working fine.

Glad I'm the person that's finally documenting this wacky behavior.