cancel
Showing results for 
Search instead for 
Did you mean: 

Nucleo User Manuals don't show the VCP UART connection

eg, UM2179 STM32 Nucleo-144 boards (MB1312):

AndrewNeil_0-1709117250441.png

Related:

https://community.st.com/t5/stm32-mcus-products/printf-causes-terminal-to-stay-just-empty/m-p/644954/highlight/true#M236811

@mƎALLEm 

 

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.
10 REPLIES 10

Also UM1724 for the Nucleo-64s:

AndrewNeil_1-1709117759233.png

 

 

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

UM1956 (Nucleo-32) just doesn't label the connection at all:

AndrewNeil_2-1709117930110.png

 

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

But UM1974 for Nucleo-144 boards (MB1137) does show it!

AndrewNeil_3-1709118074009.png

 

 

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.
mƎALLEm
ST Employee

An internal Ticket 174798 has been raised to fix the issue.
Thank you @Andrew Neil  for raising this.

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.

Reported also for UM1956 and UM1724 

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.

Probably also worth a general check on Discovery and other boards ...

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

@mƎALLEm wrote:

An internal Ticket 174798 has been raised to fix the issue.
Thank you @Andrew Neil  for raising this.


@mƎALLEm Any update on this?

The manuals have not been corrected yet, and this continues to cause confusion:

https://community.st.com/t5/stm32-mcus-products/communication-between-nucleo-f411re-and-raspberry-pi-using-st/m-p/721545/highlight/true#M261177

 

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

@Andrew Neil 

Unfortunately not yet and I don't have a visibility on this fix.

The only info is just this will be applied to the new Boards' UMs. For the old ones I cannot confirm.

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.

Another one - F429-DISCO:

https://community.st.com/t5/stm32-mcus-products/problems-with-data-reception-via-usart3-on-stm32f429-disco-board/m-p/741827#M265971

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.