The STM32 Nucleo-64 board, based on the MB1717 reference board (NUCLEO-C031C6 order code) provides an affordable
and flexible way for users to try out new concepts and build prototypes with various combinations of performance, power
consumption, and features.
The ARDUINO® Uno V3 connectivity support and the ST morpho headers provide an easy means of expanding the functionality
of the STM32C0 Nucleo open development platform with a wide choice of specialized shields.
The STM32 Nucleo-64 board does not require any separate probe, as it integrates the ST-LINK/V2-1 debugger/programmer.
The STM32 Nucleo-64 board comes with the comprehensive free STM32 software libraries and examples that are available with
the STM32CubeC0 MCU Package.
Figure 1. NUCLEO-C031C6 board (Top view)
Picture is not contractual.
UM2953 - Rev 1 - February 2022
For further information contact your local STMicroelectronics sales office.
www.st.com
Page 2
1Features
•STM32C031C6 microcontroller based on the Arm® Cortex®-M0+ processor with 32-Kbyte Flash memory
and 12-Kbyte SRAM, in an LQFP48 package
•User LED shared with ARDUINO
•User and reset push-buttons
•32.768 kHz crystal oscillator
•Board connectors:
–ARDUINO® Uno V3 expansion connector
–ST morpho extension pin headers for full access to all STM32C0 I/Os
•Flexible power-supply options: ST-LINK USB V
•On-board ST-LINK/V2-1 debugger/programmer with USB re-enumeration capability: mass storage, Virtual
COM port, and debug port
•Comprehensive free software libraries and examples available with the STM32CubeC0 MCU Package
•Support of a wide choice of Integrated Development Environments (IDEs) including IAR Embedded
Workbench®, MDK-ARM, and STM32CubeIDE
Note:Arm is a registered trademark of Arm Limited (or its subsidiaries) in the US and/or elsewhere.
®
or external sources
BUS
UM2953
Features
UM2953 - Rev 1
page 2/32
Page 3
2Ordering information
To order the NUCLEO-C031C6 Nucleo-64 board, refer to Table 1. Additional information is available from the
datasheet and reference manual of the target STM32.
Order codeBoard referenceTarget STM32
NUCLEO-C031C6MB1717STM32C031C6T6
2.1Codification
The meaning of the codification is explained in Table 2.
NUCLEO-XXYYTZDescriptionExample: NUCLEO-C031C6
XXMCU series in STM32 32-bit Arm Cortex MCUsSTM32C0 Series
YYProduct line in the SeriesSTM32C0x1 product line
T
Z
STM32 package pin count:
•C for 48 pins
STM32 Flash memory size:
•6 for 32 Kbytes
UM2953
Ordering information
Table 1. Ordering information
Table 2. Codification explanation
48‑pin package
32‑Kbyte Flash memory
UM2953 - Rev 1
page 3/32
Page 4
3Development environment
3.1System requirements
•Multi‑OS support: Windows® 10, Linux® 64-bit, or macOS
•USB Type-A or USB Type-C® to Micro-B cable
Note:
macOS® is a trademark of Apple Inc., registered in the U.S. and other countries and regions.
Linux® is a registered trademark of Linus Torvalds.
All other trademarks are the property of their respective owners.
UM2953
Development environment
®
3.2
Development toolchains
•IAR Systems® - IAR Embedded Workbench
•Keil® - MDK-ARM
•STMicroelectronics - STM32CubeIDE
1.
On Windows® only.
(1)
3.3Demonstration software
The demonstration software, included in the STM32Cube MCU Package corresponding to the on-board
microcontroller, is preloaded in the STM32 flash memory for easy demonstration of the device peripherals in
standalone mode. The latest versions of the demonstration source code and associated documentation can be
downloaded from www.st.com.
®(1)
UM2953 - Rev 1
page 4/32
Page 5
4Conventions
Table 3 provides the conventions used for the ON and OFF settings in the present document.
ConventionDefinition
Jumper JPx ONJumper fitted
Jumper JPx OFFJumper not fitted
Jumper JPx [1-2]Jumper fitted between Pin 1 and Pin 2
Solder bridge SBx ONSBx connections closed by 0 Ω resistor
Solder bridge SBx OFFSBx connections left open
Resistor Rx ONResistor soldered
Resistor Rx OFFResistor not soldered
Capacitor Cx ONCapacitor soldered
Capacitor Cx OFFCapacitor not soldered
UM2953
Conventions
Table 3. ON/OFF convention
UM2953 - Rev 1
page 5/32
Page 6
5Quick start
This section describes how to quickly start development using NUCLEO-C031C6.
To use the product, the user must accept the Evaluation Product License Agreement from the www.st.com/epla
webpage.
For more information on the STM32 Nucleo-64 board and demonstration software, visit the www.st.com/
stm32nucleo webpage.
UM2953
Quick start
5.1
Getting started
Follow the sequence below to configure the STM32 Nucleo-64 board and launch the demonstration application
(Refer to Figure 3 for component location):
1.Check jumper positions on board: CN2 ST-LINK [1-2] and [3-4], JP5 PWR [1-2], and JP6 ON.
2.For correct identification of all device interfaces from the host PC, install the Nucleo USB driver available on
the www.st.com/stm32nucleo web page, before connecting the board.
3.To power the board, connect the STM32 Nucleo-64 board to a PC with a USB Type-A or USB Type-C® to
Micro-B cable through the CN1 USB connector. Once powered on, the LD3 PWR green LED lights up and
LD1 COM LED blinks.
4.Press the B1 blue user button.
5.Observe that the blinking frequency of the LD4 three green LEDs changes, by clicking on the B1 button.
6.The demonstration software and several software examples showing how to use the STM32 Nucleo features
are available from the NUCLEO-C031C6 product location.
UM2953 - Rev 1
page 6/32
Page 7
6Hardware layout and configuration
The NUCLEO-C031C6 Nucleo-64 board is designed around the STM32C031C6T6 microcontroller in a 48-pin
LQFP package.
The hardware block diagram in Figure 2 illustrates the connections between the NUCLEO-C031C6
microcontroller and its peripherals, such as the ARDUINO® Uno V3 connector, ST morpho connector,
push‑button, and embedded ST-LINK/V2-1).
Figure 3 and Figure 4 help the user to locate these features on the STM32 Nucleo-64 board. The mechanical
dimensions of the NUCLEO-C031C6 product are shown in Figure 5.
Figure 2. Hardware block diagram
UM2953
Hardware layout and configuration
ST-LINK part
SWD
B1
USER
IO
USB
Micro-B
Embedded
ST-LINK/V2-1
STM32
microcontroller
UART
IO
UM2953 - Rev 1
ST morpho extension header
MCU part
connector
®
ARDUINO
IO
RESET
B2
RESET
IO
LED
LD4
connector
®
ARDUINO
ST morpho extension header
page 7/32
Page 8
Figure 3. NUCLEO-C031C6 PCB top side
UM2953
Hardware layout and configuration
UM2953 - Rev 1
page 8/32
Page 9
Figure 4. NUCLEO-C031C6 PCB bottom side
UM2953
Hardware layout and configuration
UM2953 - Rev 1
page 9/32
Page 10
6.1STM32 Nucleo-64 board mechanical drawing
Figure 5. STM32 Nucleo-64 board mechanical dimensions (in millimeters)
UM2953
STM32 Nucleo-64 board mechanical drawing
UM2953 - Rev 1
page 10/32
Page 11
6.2Default board configuration
JumperDefinitionDefault positionComment
CN2SWD interface
JP55 V power selection[1-2]5 V from ST-LINK
JP1STLK resetOFFNo STLK reset
JP6IDD measurementONSTM32 VDD current measurement
6.3Cuttable PCB
The STM32 Nucleo-64 board is divided into two parts: the ST-LINK part and the target MCU part. The ST-LINK
PCB part is cuttable to reduce the board size. In this case, the remaining target MCU part is only powered by VIN,
E5V, and 3.3V on CN7 morpho connectors, or VIN and 3.3V on CN6 ARDUINO® connector. And it is still possible
to use the ST-LINK part to program the main MCU using wires between CN7 and SWD signals available on the
ST morpho connectors.
6.4Embedded ST-LINK/V2-1
The ST-LINK/V2-1 programming and debugging tool is integrated into the NUCLEO-C031C6 Nucleo-64 board.
The additional features supported on the ST-LINK/V2-1 are:
•USB software re-enumeration
•Virtual COM port interface on USB
•Mass storage interface on USB
•Registers read/write interface on USB (Not available on Nucleo)
•USB power management request for more than 100 mA power on USB
The following features are no more supported on the ST-LINK/V2-1:
•SWIM interface
•Minimum application voltage supported by Nucleo limited to 3 V
•Standalone version does not exist. Only Nucleo and future discovery support V2-1.
For information about debugging and programming features, refer to the user manual ST-LINK/V2 in-circuitdebugger/programmer for STM8 and STM32 (UM1075), which describes in detail all the ST-LINK/V2 and ST-
LINK/V2-1 common features.
The embedded ST-LINK/V2-1 is usable in two different ways according to the jumper states (Refer to Table 5):
•Program/debug the on‑board STM32,
•Or program/debug an STM32 in an external application board using a cable connected to the SWD
connector.
Table 4. Default jumper settings
[1-2]
[3-4]
On-board ST-LINK/V2-1 debugger
UM2953
Default board configuration
Jumper
CN2T_SWCLK / T_SWDIO
6.4.1Drivers
ST-LINK/V2-1 requires a dedicated USB driver, which, for Windows 7®, Windows 8® and Windows 10®, is
available from www.st.com.
UM2953 - Rev 1
Table 5. ST-LINK jumper configuration
DefinitionDefault positionComment
[1-2]
[3-4]
OFF
OFF
ST-LINK/V2-1 functions enabled for on-board
programming (Default setting)
ST-LINK/V2-1 functions enabled from external
connector (SWD supported)
page 11/32
Page 12
In cases where the STM32 Nucleo-64 board is connected to the PC before the driver is installed, some STM32
Nucleo-64 interfaces might be declared as “Unknown” in the PC device manager. In this case, the user must
install the dedicated driver files and update the driver of the connected device from the device manager, as shown
in Figure 6.
Note:It is preferable to use the USB Composite Device handle for a full recovery.
Figure 6. USB composite device
UM2953
Embedded ST-LINK/V2-1
6.4.2ST-LINK/V2-1 firmware upgrade
ST-LINK/V2-1 embeds a firmware mechanism for the in-situ upgrade through the USB port. As the firmware may
evolve during the lifetime of the ST-LINK/V2-1 product (for example new functionalities, bug fixes, support for
new microcontroller families), visiting the www.st.com website is recommended before starting to use the STM32
Nucleo-64 board, then periodically to stay up-to-date with the latest firmware version.
6.4.3Using ST-LINK/V2-1 to program/debug the on-board STM32
To program the on‑board STM32, plug in the two jumpers on CN2, as shown in Figure 3 but do not use the CN3
connector as that may disturb communication with the on‑board STM32 microcontroller.
6.4.4Using ST-LINK/V2-1 to program/debug an external STM32 application
It is easy to use ST-LINK/V2-1 to program the STM32 on an external application. Remove the two jumpers from
CN2 as shown in Figure 3, and connect the application to the CN3 debug connector according to Table 6.
Note:SB23 must be OFF if CN3 pin 5 is used in the external application.
Table 6. CN3 SWD debug connector
Pin numberSignal nameDesignation
1VDD_TARGETVDD from the application
2SWCLKSWD clock
3GNDGround
4SWDIOSWD data I/O
5NRSTTarget MCU reset
6SWOReserved
UM2953 - Rev 1
page 12/32
Page 13
UM2953
Power supply and power selection
6.5Power supply and power selection
6.5.1External power supply input
The STM32 Nucleo-64 board is designed to be powered by several DC power supplies. It is possible to supply the
STM32 Nucleo-64 board with any of the following sources:
•5V_USB_STLK from the ST-LINK USB connector
•VIN (7 to 12 V) from the ARDUINO® or ST morpho connector
•E5V from the ST morpho connector
•5V_USB_CHG from the ST-LINK USB connector
•3.3 V from the ARDUINO® or ST morpho connector
Note:If an external 5 V DC power source is used, the Nucleo board must be powered by a power supply unit or by
a piece of auxiliary equipment complying with the EN-60950-1: 2006+A11/2009 standard and must be safety
extra
‑
low voltage (SELV) with limited power capability.
The power supply capabilities are shown in Table 7.
Table 7. Power supply capabilities
Input power
5V_USB_STLKCN1 pin 14.75 to 5.25 V500 mA
VIN
E5VCN7 pin 64.75 to 5.25 V500 mA-
5V_USB_CHGCN1 pin 14.75 to 5.25 V500 mA
3V3
Connector
pins
CN6 pin 8
CN7 pin 24
CN6 pin 4
CN7 pin 16
JP6 pin 1
Voltage range
7 to 12 V800 mA
3.0 to 3.6 V-
Maximum
current
Limitation
The maximum current depends on the USB
enumeration:
•100 mA without enumeration
•500 mA with good enumeration
From 7 to 12 V only and the input current capability
is linked to the input voltage:
•800 mA input current when VIN = 7 V
•450 mA input current when 7 V < VIN < 9 V
•300 mA input current when 9 V < VIN < 10V
•Less than 300 mA input current when
10 V < VIN
Maximum current depends on the USB wall charger
used to power the Nucleo board.
Used when the PCB ST-LINK part is not used or
remove SB2 and SB23
5V_ST_LINK is a DC power with limitations from the ST-LINK USB connector (USB type Micro-B connector of
ST-LINK/V2-1). In this case, the JP5 jumper must be on pins 1 and 2 to select the STLK power source on the JP5
silkscreen. This is the default setting. If the USB enumeration succeeds, the STLK power is enabled, by asserting
the PWR_ENn signal coming from the STM32F103CBT6 ST-LINK microcontroller. This pin is connected to an
STMPS2141STR power switch, which powers the board. This power switch also features a current limitation to
protect the PC in case of a short-circuit on board, detected with current higher than 750 mA.
The STM32 Nucleo-64 board and its shield are powerable from the CN1 ST-LINK USB connector, but only the
ST-LINK circuit is powered before USB enumeration because the host PC only provides 100 mA to the board
at that time. During the USB enumeration, the STM32 Nucleo-64 board requires 500 mA of current from the
host PC. If the host can provide the required power, the enumeration ends by a SetConfiguration command
and then, the STMPS2141STR power transistor is switched ON, the LD3 green LED is turned ON, thus the
STM32 Nucleo-64 board and its shield request no more than 500 mA current. If the host is not able to provide
the required current, the enumeration fails. Therefore the power switch transistor stays OFF and the MCU part
including the extension board is not powered. As a consequence, the LD3 green LED stays turned OFF. In this
case, it is mandatory to use an external power supply.
USB power: STLK configuration: Jumper JP5 [1-2] (STLK silkscreen) must be connected as shown in Figure 3
and Table 9.
UM2953 - Rev 1
page 13/32
Page 14
VIN is the 7 to 12 V DC power from CN6 pin 8 named VIN on ARDUINO® connector silkscreen or from pin 24
of CN7 ST morpho connector. In this case, the JP5 jumper must be [3-4] to select the VIN power source on the
JP5 silkscreen. In that case, the DC power comes from the power supply through the ARDUINO® Uno V3 battery
shield and is compatible with Adafruit® PowerBoost 500 shield.
VIN configuration: The JP5 jumper [3-4] (VIN silkscreen) must be connected as shown in Figure 3 and Table 9.
E5V is the DC power coming from an external source (5V DC power from pin 6 of the CN7 ST morpho
connector). In this case, the JP5 jumper must be [5-6] to select the E5V power source on the JP5 silkscreen.
E5V configuration: The JP5 jumper [5-6] (E5V silkscreen) must be connected as shown in Figure 3 and Table 9.
5V_USB_CHARGER is the DC power charger connected to the CN1 USB ST-LINK connector. To select the CHG
power source on the JP5 silkscreen, the JP5 jumper must be [7-8]. In this case, if the STM32 Nucleo-64 board is
powered by an external USB charger the debug is not available. If the PC is connected instead of the charger, the
limitation is no more effective and the PC can be damaged.
CHG configuration: The JP5 jumper [7-8] (CHG silkscreen) must be connected as shown in Figure 3 and Table 9.
6.5.2External power supply output
•5V: The 5V present on CN6 pin 5 or CN7 pin 18 is usable as a power supply output for an ARDUINO® shield
or an extension board when the STM32 Nucleo-64 board is powered by USB, VIN, or E5V. In this case, the
maximum current allowed is shown in Table 7.
•3.3V: The 3V3 present on CN6 pin 4 or CN7 pin 16 is usable as a power supply output. The current is
limited by the maximum current capability of the U6 regulator (LDL112PV33R from STMicroelectronics). In
this condition, the maximum consumption of the STM32 Nucleo-64 board and the connected shield current
must be lower than 500 mA.
UM2953
Programming/debugging when the power supply is not from ST-LINK
6.6
Programming/debugging when the power supply is not from ST-LINK
VIN or E5V is usable as an external power supply in case the current consumption of the STM32 Nucleo-64 board
and its extension boards exceed the allowed current on the USB. In such a condition, it is still possible to use
the USB for communication, programming, or debugging only. In this case, it is mandatory to power the board
first using VIN or E5V then to connect the USB cable to the PC. Proceeding this way the enumeration succeeds,
thanks to the external power source. The following power sequence procedure must be respected:
•Connect the JP5 jumper [3-4] for VIN or [5-6] for E5V,
•Connect the external power source to VIN or E5V,
•Power ON the external power supply 7 V < VIN < 12 V to VIN, or 5 V for E5V,
•Check that the LD3 green LED is turned ON,
•Connect the PC to the CN1 USB connector.
If this sequence is not respected, the board may be powered by V
•If a higher than 500 mA current is needed by the board, the PC may be damaged or the current supplied
may be limited by the PC. As a consequence, the board is not powered correctly.
•500 mA is requested at the enumeration since SB1 must be OFF. This request is rejectable and the
enumeration does not succeed if the PC does not provide such current. Consequently, the board is not
power supplied and LD3 LED remains OFF.
6.7OSC clock sources
Three clock sources are listed below:
•LSE which is the 32.768 kHz crystal for the STM32 embedded RTC,
•MCO which is the 8 MHz clock from the ST-LINK MCU for the STM32 microcontroller,
•HSE which is the 48 MHz oscillator for the STM32 microcontroller.
first from ST-LINK, with the following risks:
BUS
UM2953 - Rev 1
page 14/32
Page 15
6.7.1LSE clock reference
There are three ways to configure the pins corresponding to the low-speed clock (LSE):
1.LSE on-board X2 crystal (Default configuration). Refer to the application note Oscillator design guide forSTM8AF/AL/S, STM32 MCUs and MPUs (AN2867) for crystal design guide for STM32 microcontrollers.
2.Oscillator from external to PC14 input, from external oscillator through pin 25 of the CN7 connector. The
following configuration is needed:
–SB3 ON
–R31 and R32 OFF
3.LSE not used. PC14 and PC15 are used as GPIOs instead of low‑speed clocks. The following configuration
is needed:
–SB3 and SB4 ON
–R31 and R32 OFF
6.7.2HSE clock reference
There are four ways to configure the pins corresponding to the external high‑speed clock (HSE):
1.HSE not used: PF0 and PF1 are used as GPIOs instead of clocks. The configuration must be:
–SB5 and SB6 ON
–SB29 (MCO) OFF
–R33 and R34 OFF
2.MCO from ST-LINK: MCO output of ST-LINK is used as an input clock. This frequency cannot be changed,
it is fixed at 8 MHz and connected to the PF0-OSC_IN of the STM32 microcontroller. The configuration must
be:
–SB29 ON
–SB5 and SB6 OFF
–R33 and R34 OFF
3.HSE on-board oscillator from X3 crystal (default). For typical frequencies, capacitors, and resistors, refer to
the STM32 microcontroller datasheet and the application note Oscillator design guide for STM8AF/AL/S,STM32 MCUs and MPUs (AN2867) for the oscillator design guide. The X3 crystal has the following
characteristics: 48 MHz, 7 pF, and 20 ppm. The configuration must be:
–SB5 and SB6 OFF
–R33 and R34 ON
–C25 and C26 ON with 4.3 pF capacitors
–SB29 OFF
4.Oscillator from external PF0, from an external oscillator through pin 29 of the CN7 connector. The
configuration must be:
–SB5 ON
–SB29 OFF
–R33 and R34 OFF
UM2953
Reset sources
6.8
UM2953 - Rev 1
Reset sources
The STM32 Nucleo-64 reset signal is active LOW and the reset sources include:
•B2 reset push‑button
•Embedded ST-LINK/V2-1
•CN6 ARDUINO® connector pin 3
•CN7 ST morpho connector pin 14
page 15/32
Page 16
6.9VCP communication
The two UART interfaces of the STM32 are used for VCP communication:
1.UART2 from PA2/PA3
2.UART1 from PB6/PB7
UM2953
VCP communication
Table 8. VCP communication
Pin nameFunction
PA2USART2 TXSB27 ONSB27 OFF
PA3USART2 RXSB32 ONSB32 OFF
PB6USART1 TXSB31 ONSB31 OFF
PB7USART1 RXSB33 ONSB33 OFF
6.10LEDs
Four LEDs are available on the STM32 Nucleo-64 board. The four LEDs are located on the top side of the board:
1.LD1 COM: LD1 is a bi-colored LED. the LD1 default status is red. LD1 turns to green to indicate that
communication is in progress between the PC and the ST-LINK/V2-1 as follow:
–Slow blinking red and OFF: At power-on before USB initialization
–Fast blinking red and OFF: After the first correct communication between the PC and the ST-LINK/V2-1
–Red LED ON: When initialization between the PC and the ST-LINK/V2-1 successfully ends
–Green LED ON: After successful STM32 communication initialization
–Blinking red and green: During communication with STM32
–Green ON: Communication successfully ends.
–Orange ON: Communication ends with failure.
2.LD2 5V_USB_CHG: This red LED is ON when overcurrent is detected on USB V
information that more than 500 mA is requested on V
board with E5V, VIN, or in USB_CHARGER mode.
3.LD3 5V_PWR: This green LED is ON when the STM32 Nucleo-64 board is powered by a 5 V source.
4.
LD4 USER: This green LED is a user LED connected to D13 ARDUINO® signal corresponding to PA5
STM32 I/O. To light the LED a HIGH logic state must be written in the corresponding GPIO. A transistor is
used to drive the LED when the I/O voltage is 1.8 V. LD4 consumption does not impact the VDD STM32
power measurement, since LD4 is isolated from it.
(enumeration)
Virtual COM port
(Default configuration
. In this case, it is recommended to supply the
BUS
ST morpho connection
. The LED gives the
BUS
6.11Push‑buttons
Two push‑buttons:
1.B1 USER: User and wake-up button connected to the PC13 I/O pin 3 of the STM32 microcontroller
2.B2 RESET: Push‑button connected to NRST is used to reset the STM32 microcontroller.
The blue and black plastic hats placed on these push‑buttons are removable if necessary when a shield or an
application board is plugged on top of the Nucleo board. This avoids pressure on the buttons and consequently a
possible permanent target MCU reset.
6.12IDD measurement
The JP6 IDD‑labeled jumper allows the consumption of the STM32 microcontroller measurement by removing the
jumper and connecting an ammeter:
•Jumper ON: STM32 Microcontroller is powered (Default configuration)
•Jumper OFF: An ammeter must be connected to measure the STM32 microcontroller current. If there is no
ammeter, the STM32 microcontroller is not powered.
UM2953 - Rev 1
page 16/32
Page 17
6.13Jumper configuration
The default jumper positions are shown in Table 4. Table 9 describes the other available jumper settings
JumperDefinition
CN2
JP2/JP3GNDONGND probe
JP55 V power selection
JP1STLK reset
JP6IDD measurement
1. Default jumper state is shown in bold.
T_SWCLK
T_SWDIO
Table 9. Jumper configuration
State
[1-2]
[3-4]
OFF
OFF
[1-2]5V from ST-LINK
[3-4]5 V from VIN 7 to 12 V
[5-6]5 V from E5V
[7-8]5 V from USB_CHG
OFFNo 5 V power
OFFNo STLK reset
[1-2]STLK reset
[1-2]VDD = 3.3 V
OFF
UM2953
Jumper configuration
(1)
ST-LINK/V2-1 enable for
on‑board MCU debugger
ST-LINK/V2-1 enable for
external MCU debugger
To connect the external
source
(ULPBench probe as an
example)
Comment
6.14
Solder bridge configuration
Table 10 describes the solder bridge settings.
Table 10. Solder bridge configuration and settings
Solder bridgeDefinition
SB11/SB13/SB15/SB17
SB12/SB14/SB16/SB18
SB21/SB22
SB1
SB20MCO
SWD interface
(Default)
SWD interface
(Reserved)
VCP interface
(Default)
VCP interface
(Reserved)
Allowed current through CN1
setting
State
(1)
Comment
ONReserved, do not modify.
OFFReserved, do not modify.
ON
VCP connects ST-LINK and
on‑board MCU.
OFFVCP interface used as GPIOs
ON
OFF
ON
100 mA maximum allowed
current through CN1
300 mA maximum allowed
current through CN1
MCO from STLK provides
8 MHz CLK to MCU.
OFFMCO from STLK floating
UM2953 - Rev 1
page 17/32
Page 18
UM2953
Solder bridge configuration
Solder bridgeDefinition
SB23.3 V LDO output
SB27/SB31/
SB32/SB33
UART for VCP
SB30AVDD
SB28AGND
SB5/SB6HSE CLK selection
SB3/SB4LSE CLK selection
SB7/SB8
SB9/SB10
ADC/I2C
SB26User LED
SB25AVDD
1. Default solder bridge state is shown in bold.
(1)
State
ON
OFF
SB27/SB32 ON,
SB31/SB33 OFF
SB27/SB32 OFF,
SB31/SB33 ON
ON
OFF
U6 LDO output provides
3.3 V.
U6 LDO output does not
provide 3.3 V.
USART2 from PA2/PA3
USART1 from PB6/PB7
VDD provides power to
AVDD.
VDD does not provide power
to AVDD.
Comment
ONAGND is connected to GND.
OFF
AGND is not connected to
GND.
ON (R33/R34 OFF)PF0 and PF1work as GPIOs.
OFF
ON (R31/R32 OFF)
OFF
SB8/SB9 ON
SB7/SB10 OFF
PF0 and PF1work as HSE
pins.
PC14 and PC15 work as
GPIOs.
PC14 and PC15 work as LSE
pins.
CN8 pins 5 and 6 work as
ADC.
SB8/SB9 OFF
SB7/SB10 ON
CN8 PIN5/6 works as I2C.
ONPA5 controls LD4.
OFFLD4 is isolated.
ON
OFF
AVDD is connected to CN5
pin 8.
AVDD is disconnected from
CN5 pin 8.
UM2953 - Rev 1
page 18/32
Page 19
7Connectors
10
9
8
7
6
5
4
3
2
1
8
7
6
5
4
3
2
1
1
3
5
7
9
11
13
15
17
19
21
23
25
27
29
31
33
35
37
2
4
6
8
10
12
14
16
18
20
22
24
26
28
30
32
34
36
38
1
2
3
4
5
6
1
2
3
4
5
6
7
8
1
3
5
7
9
11
13
15
17
19
21
23
25
27
29
31
33
35
37
2
4
6
8
10
12
14
16
18
20
22
24
26
28
30
32
34
36
38
1 0
9
8
7
6
5
4
3
2
1
8
7
6
5
4
3
2
1
1
3
5
7
9
1 1
1 3
1 5
1 7
1 9
2 1
2 3
2 5
2 7
2 9
3 1
3 3
3 5
3 7
2
4
6
8
1 0
1 2
1 4
1 6
1 8
2 0
2 2
2 4
2 6
2 8
3 0
3 2
3 4
3 6
3 8
1
2
3
4
5
6
1
2
3
4
5
6
7
8
1
3
5
7
9
1 1
1 3
1 5
1 7
1 9
2 1
2 3
2 5
2 7
2 9
3 1
3 3
3 5
3 7
2
4
6
8
1 0
1 2
1 4
1 6
1 8
2 0
2 2
2 4
2 6
2 8
3 0
3 2
3 4
3 6
3 8
ARDUINO
®
Uno
ST morpho
PD0
PD3
PD1NC
PD2
PB8
PD2NC
VDD
PB9
AVDD
GND
E5VNC
PA14GND5V-USB-CHG
NCNC
IOREF
NRST
+3V3
+5V
GND
GND
VIN
PA3
NC
PA5
PC15
PA13
PA6
PB12
NC
PA7
PB12
PC6
PB0
PB2
GND
PC7
GND
NC
PA9
PF3
PC13PA15PA8
PC14PB5NCPB15
NCPB4PA0PB14
PF0PB10PA1PB13
PF1PB3PA4AGND
NCPA10PB1PB0
PB11PB6PA11/PB9NC
PA2PB7PA12/PB8NC
NUCLEO-C031C6
CN7 CN6
CN8CN9
CN5 CN10
D8
D9
D1 0
D1 1
D1 2
D1 3
GND
AVDD
D1 4
D1 5
D0
D1
D2
D3
D4
D5
D6
D7
A5
A4
A3
A2
A1
A0
VIN
GND
GND
+ 5 V
+ 3 V3
NRS T
IOREF
NC
Seven connectors are implemented on the STM32 Nucleo-64 board:
•CN1 ST-LINK USB Micro-B connector
•CN5, CN6, CN8, and CN9 ARDUINO® Uno V3 connector
•CN7 and CN10 ST morpho connectors
UM2953
Connectors
7.1
ARDUINO® Uno V3 connector
The CN5, CN6, CN8, and CN9 ARDUINO® Uno connectors in Figure 3 are female connectors compatible with the
ARDUINO® standard. Most shields designed for ARDUINO® fit the STM32 Nucleo-64 board.
The ARDUINO® connectors on the STM32 Nucleo-64 board support the ARDUINO® Uno V3.
The related pinout for the ARDUINO® connector is shown in Figure 7 and listed in Table 11.
The CN7 and CN10 ST morpho connectors are male pin headers accessible on both sides of the STM32
Nucleo-64 board (Refer to Figure 3). All STM32 signals and power pins except 1.2 V VDD_CORE are available
on the ST morpho connectors. These connectors can also be probed by an oscilloscope, logical analyzer, or
voltmeter.
The related pinout and the MCU assignment for the ST morpho connectors are listed in Figure 7.
UM2953 - Rev 1
page 20/32
Page 21
8STM32 Nucleo-64 board information
8.1Product marking
The stickers located on the top or bottom side of the PCB provide product information:
•Product order code and product identification for the first sticker
•Board reference with revision, and serial number for the second sticker
On the first sticker, the first line provides the product order code, and the second line the product identification.
On the second sticker, the first line has the following format: “MBxxxx-Variant-yzz”, where “MBxxxx” is the board
reference, “Variant” (optional) identifies the mounting variant when several exist, "y" is the PCB revision and "zz"
is the assembly revision, for example B01. The second line shows the board serial number used for traceability.
Evaluation tools marked as “ES” or “E” are not yet qualified and therefore not ready to be used as reference
design or in production. Any consequences deriving from such usage will not be at ST charge. In no event, ST will
be liable for any customer usage of these engineering sample tools as reference designs or in production.
“E” or “ES” marking examples of location:
•On the targeted STM32 that is soldered on the board (For an illustration of STM32 marking, refer to the
STM32 datasheet “Package information” paragraph at the www.st.com website).
•Next to the evaluation tool ordering part number that is stuck or silk-screen printed on the board.
Some boards feature a specific STM32 device version, which allows the operation of any bundled commercial
stack/library available. This STM32 device shows a "U" marking option at the end of the standard part number
and is not available for sales.
In order to use the same commercial stack in his application, a developer may need to purchase a part number
specific to this stack/library. The price of those part numbers includes the stack/library royalties.
UM2953
STM32 Nucleo-64 board information
8.2NUCLEO-C031C6 product history
8.2.1Product identification NUC031C6$KU1
This product identification is based on the MB1717-C031C6-B01 board.
It embeds the STM32C031C6 microcontroller with revision code "A". The limitations of this revision are detailed in
the errata sheet STM32C031 device errata (ES0568).
Product limitations
No limitation identified for this product identification.
8.3
8.3.1Board MB1717 revision B01
Board revision history
The revision B01 is the initial release of the MB1717 board.
This revision B01 is produced with the STM32C031C6T6 microcontroller.
Federal Communications Commission (FCC) and Innovation, Science and Economic Development Canada (ISED) Compliance Statements
10Federal Communications Commission (FCC) and Innovation,
Science and Economic Development Canada (ISED) Compliance
Statements
10.1FCC Compliance Statement
Part 15.19
This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this
device may not cause harmful interference, and (2) this device must accept any interference received, including
interference that may cause undesired operation.
Part 15.21
Any changes or modifications to this equipment not expressly approved by STMicroelectronics may cause
harmful interference and void the user's authority to operate this equipment.
Part 15.105
This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part
15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference
in a residential installation. This equipment generates uses and can radiate radio frequency energy and, if not
installed and used in accordance with the instruction, may cause harmful interference to radio communications.
However, there is no guarantee that interference will not occur in a particular installation. If this equipment does
cause harmful interference to radio or television reception which can be determined by turning the equipment off
and on, the user is encouraged to try to correct interference by one or more of the following measures:
•Reorient or relocate the receiving antenna.
•Increase the separation between the equipment and receiver.
•Connect the equipment into an outlet on circuit different from that to which the receiver is connected.
•Consult the dealer or an experienced radio/TV technician for help.
Note:Use only shielded cables.
10.2
Responsible party (in the USA)
Terry Blanchard
Americas Region Legal | Group Vice President and Regional Legal Counsel, The Americas
STMicroelectronics, Inc.
750 Canyon Drive | Suite 300 | Coppell, Texas 75019
USA
Telephone: +1 972-466-7845
IC Compliance Statement
This device complies with FCC and Industry Canada RF radiation exposure limits set forth for general population
for mobile application (uncontrolled exposure). This device must not be collocated or operating in conjunction with
any other antenna or transmitter.
Compliance Statement
Notice: This device complies with Industry Canada licence-exempt RSS standard(s). Operation is subject to
the following two conditions: (1) this device may not cause interference, and (2) this device must accept any
interference, including interference that may cause undesired operation of the device.
Industry Canada ICES-003 Compliance Label: CAN ICES-3 (B) / NMB-3 (B).
UM2953 - Rev 1
page 24/32
Page 25
UM2953
IC Compliance Statement
Déclaration de conformité
Avis: Le présent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts
de licence. L'exploitation est autorisée aux deux conditions suivantes : (1) l'appareil ne doit pas produire de
brouillage, et (2) l'utilisateur de l'appareil doit accepter tout brouillage radioélectrique subi, même si le brouillage
est susceptible d'en compromettre le fonctionnement.
Étiquette de conformité à la NMB-003 d'Industrie Canada : CAN ICES-3 (B) / NMB-3 (B).
UM2953 - Rev 1
page 25/32
Page 26
11CE conformity
11.1Warning
EN 55032 / CISPR32 (2012) Class B product
Warning: this device is compliant with Class B of EN55032 / CISPR32. In a residential environment, this
equipment may cause radio interference.
Avertissement : cet équipement est conforme à la Classe B de la EN55032 / CISPR 32. Dans un environnement
résidentiel, cet équipement peut créer des interférences radio.
UM2953
CE conformity
11.2
Simplified CE declaration of conformity
Hereby, STMicroelectronics declares that the radio equipment types NUCLEO-C031C6 and NUCLEO-G071RB
comply with the applicable CE requirements stated below:
STMicroelectronics NV and its subsidiaries (“ST”) reserve the right to make changes, corrections, enhancements, modifications, and improvements to ST
products and/or to this document at any time without notice. Purchasers should obtain the latest relevant information on ST products before placing orders. ST
products are sold pursuant to ST’s terms and conditions of sale in place at the time of order acknowledgement.
Purchasers are solely responsible for the choice, selection, and use of ST products and ST assumes no liability for application assistance or the design of
Purchasers’ products.
No license, express or implied, to any intellectual property right is granted by ST herein.
Resale of ST products with provisions different from the information set forth herein shall void any warranty granted by ST for such product.
ST and the ST logo are trademarks of ST. For additional information about ST trademarks, please refer to www.st.com/trademarks. All other product or service
names are the property of their respective owners.
Information in this document supersedes and replaces information previously supplied in any prior versions of this document.