Question about ST-Nucleo

[Vyacheslav Azarov]

Posted on December 10, 2015 at 16:18

Hello, 

I develop power conversion controller and have one question. STM32-Nucleo have internally asynchronous serial junction between debugger MCU and target MCU. In ST-LINK/V2(-1) this feature not present. I can to use this extension for debugging? How it use? Thank you.

[Tesla DeLorean]

Posted on December 10, 2015 at 16:49

All DISCO/NUCLEO(64) boards supporting mbed have an VCP implementation. On the Nucleo's this is typically USART2 PA2/PA3, and at 115200 8N1. If you load the drivers a VCP/COM should appear in Device Manager under Windows and be accessible via a Terminal application.

Cortex-M3/M4 parts also have connectivity (sometimes via a solder bridge) of SWO (PB3) this provides for the SWV (Serial Wire Viewer) which is a debug com channel, and viewable in Keil/IAR of with the SWV window in the ST-LINK Utilities. The stand-alone ST-LINK pod supports the SWV method, not the VCP one.

[Vyacheslav Azarov]

Posted on December 13, 2015 at 22:47

Got it. Thank you very much.

From: clive1Posted: Thursday, December 10, 2015 4:50 PMSubject: Question about ST-Nucleo

All DISCO/NUCLEO(64) boards supporting mbed have an VCP implementation. On the Nucleo's this is typically USART2 PA2/PA3, and at 115200 8N1. If you load the drivers a VCP/COM should appear in Device Manager under Windows and be accessible via a Terminal application.

Cortex-M3/M4 parts also have connectivity (sometimes via a solder bridge) of SWO (PB3) this provides for the SWV (Serial Wire Viewer) which is a debug com channel, and viewable in Keil/IAR of with the SWV window in the ST-LINK Utilities.The stand-alone ST-LINK pod supports the SWV method, not the VCP one.