Nucleo G031K8

Overview

The STM32 Nucleo-32 board provides an affordable and flexible way for users to try out new concepts and build prototypes by choosing from the various combinations of performance and power consumption features, provided by the STM32 microcontroller.

The Arduino™ Nano V3 connectivity support allows the easy expansion of the functionality of the STM32 Nucleo open development platform with a wide choice of specialized shields.

The STM32 Nucleo-32 board does not require any separate probe as it integrates the ST-LINK debugger/programmer.

The STM32 Nucleo-32 board comes with the STM32 comprehensive free software libraries and examples available with the STM32Cube MCU Package.

More information about the board can be found at the Nucleo G031K8 website [1].

Hardware

Nucleo G031K8 provides the following hardware components:

  • STM32 microcontroller in 32-pin package featuring 64 Kbytes of Flash memory and 8 Kbytes of SRAM.

  • Extension resource:

    • Arduino* Nano V3 connectivity

  • On-board ST-LINK/V2-1 debugger/programmer with SWD connector:

  • Flexible board power supply:

    • USB VBUS or external source (3.3V, 5V, 7 - 12V)

    • Current consumption measurement (IDD)

  • Four LEDs:

    • USB communication (LD1), power LED (LD2), user LED (LD3), USB power fault LED (LD4)

  • One push-button: RESET

  • USB re-enumeration capability. Three different interfaces supported on USB:

    • Virtual COM port

    • Mass storage

    • Debug port

More information about STM32G031K8 can be found in the STM32G0x1 reference manual [2]

Supported Features

The nucleo_g031k8 board supports the hardware features listed below.

on-chip / on-board
Feature integrated in the SoC / present on the board.
2 / 2
Number of instances that are enabled / disabled.
Click on the label to see the first instance of this feature in the board/SoC DTS files.
vnd,foo
Compatible string for the Devicetree binding matching the feature.
Click on the link to view the binding documentation.

nucleo_g031k8/stm32g031xx target

Type

Location

Description

Compatible

CPU

on-chip

ARM Cortex-M0+ CPU1

arm,cortex-m0+

ADC

on-chip

STM32 ADC1

st,stm32-adc

Clock control

on-chip

STM32F0/G0 RCC (Reset and Clock controller)1

st,stm32f0-rcc

on-chip

STM32 HSE Clock1

st,stm32-hse-clock

on-chip

STM32G0 HSI Clock1

st,stm32g0-hsi-clock

on-chip

STM32 LSE Clock1

st,stm32-lse-clock

on-chip

Generic fixed-rate clock provider1

fixed-clock

on-chip

STM32G0 main PLL1

st,stm32g0-pll-clock

Counter

on-chip

STM32 counters5

st,stm32-counter

DMA

on-chip

STM32 DMA controller (V2)1

st,stm32-dma-v2

on-chip

STM32 DMAMUX controller1

st,stm32-dmamux

Flash controller

on-chip

STM32 Family flash controller1

st,stm32-flash-controller

GPIO & Headers

on-chip

STM32 GPIO Controller5

st,stm32-gpio

on-board

GPIO pins exposed on Arduino Nano (R3) headers1

arduino-nano-header-r3

I2C

on-chip

STM32 I2C V2 controller2

st,stm32-i2c-v2

Interrupt controller

on-chip

ARMv6-M NVIC (Nested Vectored Interrupt Controller) controller1

arm,v6m-nvic

on-chip

STM32G0 External Interrupt Controller1

st,stm32g0-exti

LED

on-board

Group of GPIO-controlled LEDs1

gpio-leds

Memory controller

on-chip

STM32 Battery Backed RAM1

st,stm32-bbram

MTD

on-chip

STM32 flash memory1

st,stm32-nv-flash

Pin control

on-chip

STM32 Pin controller1

st,stm32-pinctrl

PWM

on-chip

STM32 PWM6

st,stm32-pwm

Reset controller

on-chip

STM32 Reset and Clock Control (RCC) Controller1

st,stm32-rcc-rctl

RTC

on-chip

STM32 RTC1

st,stm32-rtc

Sensors

on-chip

STM32 family TEMP node for production calibrated sensors with two calibration temperatures1

st,stm32-temp-cal

on-chip

STM32 VREF+1

st,stm32-vref

on-chip

STM32 VBAT1

st,stm32-vbat

Serial controller

on-chip

STM32 USART1 1

st,stm32-usart

on-chip

STM32 LPUART1

st,stm32-lpuart

SMbus

on-chip

STM32 SMBus controller2

st,stm32-smbus

SPI

on-chip

STM32 SPI controller with embedded Rx and Tx FIFOs1 1

st,stm32-spi-fifo

SRAM

on-chip

Generic on-chip SRAM description1

mmio-sram

Timer

on-chip

ARMv6-M System Tick1

arm,armv6m-systick

on-chip

STM32 low-power timer (LPTIM)1

st,stm32-lptim

on-chip

STM32 timers6

st,stm32-timers

Watchdog

on-chip

STM32 watchdog1

st,stm32-watchdog

on-chip

STM32 system window watchdog1

st,stm32-window-watchdog

Connections and IOs

Each of the GPIO pins can be configured by software as output (push-pull or open-drain), as input (with or without pull-up or pull-down), or as peripheral alternate function. Most of the GPIO pins are shared with digital or analog alternate functions. All GPIOs are high current capable except for analog inputs.

Default Zephyr Peripheral Mapping:

  • UART_2 TX/RX : PA2/PA3 (ST-Link Virtual Port Com)

  • I2C2 SCL/SDA : PA9/PA10 (Arduino I2C)

  • SPI1 SCK/MISO/MOSI : PB3/PB4/PB5 (Arduino SPI)

  • LD3 : PC6

For more details please refer to STM32 Nucleo-32 board User Manual [3].

Programming and Debugging

Nucleo G031K8 board includes an ST-LINK/V2-1 embedded debug tool interface.

Applications for the nucleo_g031k8 board configuration can be built and flashed in the usual way (see Building an Application and Run an Application for more details).

Flashing

The board is configured to be flashed using west STM32CubeProgrammer [4] runner, so its installation is required.

Alternatively, OpenOCD or JLink can also be used to flash the board using the --runner (or -r) option:

$ west flash --runner openocd
$ west flash --runner jlink

Flashing an application to Nucleo G031K8

Here is an example for the Blinky application.

# From the root of the zephyr repository
west build -b nucleo_g031k8 samples/basic/blinky
west flash

You will see the LED blinking every second.

Debugging

You can debug an application in the usual way. Here is an example for the Hello World application.

# From the root of the zephyr repository
west build -b nucleo_g031k8 samples/hello_world
west debug

Restriction

On some boards, the board reset line is not used by the controller. Therefore the reset button, reset-pin and the ST-Link reset have no effect. To enable those functionalities, the option byte NRST_mode in the User Configuration needs to be changed from 2 to 1 or 3 - depending on the requirements.

References