USART3 not available to use in CubeMX

[AShetty]

I am trying to generate code using CubeMX (version 6.11.1), using the NUCLEO-H563ZI board to start the project. But, I am getting the following pop-up when trying to use the USART3 peripheral which seems to be unavailable:

Because of this, I had to downgrade the version of CubeMX to 6.10.0 to use USART3. However, I observed that even after saving the ioc file, later when we opened the file again CubeMX had overwritten the pins to the default state.

Why is this happening and is there any workaround for it?

[Andrew Neil]

Did you look at the "Details & documentation":

[AShetty]

That is just the data sheet and the reference manual.

[AScha.3]

This is the VCP , on USART3 on this board connected, so its already used - so it shows this to you.

If you wnat to use it, you have to cut the connections on the board and make your hardware then to the rx/tx PD8/9 .

Why not using it as intended for VCP (or debug printf(...) ) ?

see circuit of this board:

[AShetty]

The application I am using is not using these pins for debugging purposes but rather to send data from the board to the PC. 

I am able to generate code by unlocking the pins and enabling USART3 in CubeMX 6.10.0. But CubeMX seems to overwrite it again to VCP when I open the file again.

One workaround I found was to use STM32H563ZIT6 MCU instead of the NUCLEO board before starting the project in CubeMX. Is there no resolution to this in the NUCLEO-H563ZI board project?

[STTwo-32 · Accepted solution]

Hello @AShetty 

When you start your project, you have to disable the generation of the Human Machine Interface using the Button "Unselect All" then ok to open you .ioc file.

Best Regards.

STTwo-32

[Andrew Neil]

It would be really helpful if the  "Details & documentation" link in the pop-up actually told you that!

Just linking to the data sheet and the reference manual is useless - neither of those documents would be any help at all in this situation!

:face_with_rolling_eyes:

[Al-E-Bags]

I had the same issue with a new H503RC NUCLEO board I have just received.  Thankfully, this was the very first post I came across whilst looking for a fix.  Trawling the available documentation for the answer is logical but frustrating, a little daunting and very time consuming for such a simple resolution. As @Andrew Neil  suggests, this information could have been displayed on the pop-up.