ST Nucleo F103RB

Overview

The STM32 Nucleo-64 development board with STM32F103RB MCU, supports Arduino and ST morpho connectivity.

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

The Arduino* Uno V3 connectivity support and the ST morpho headers allow easy functionality expansion of the STM32 Nucleo open development platform with a wide choice of specialized shields.

The STM32 Nucleo board integrates the ST-LINK/V2-1 debugger and programmer.

The STM32 Nucleo board comes with the STM32 comprehensive software HAL library together with various packaged software examples.

Nucleo F103RB

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

Hardware

Nucleo F103RB provides the following hardware components:

  • STM32 microcontroller in QFP64 package
  • Two types of extension resources:
    • Arduino* Uno V3 connectivity
    • ST morpho extension pin headers for full access to all STM32 I/Os
  • ARM* mbed*
  • On-board ST-LINK/V2-1 debugger/programmer with SWD connector:
    • Selection-mode switch to use the kit as a standalone ST-LINK/V2-1
  • Flexible board power supply:
    • USB VBUS or external source (3.3V, 5V, 7 - 12V)
    • Power management access point
  • Three LEDs:
    • USB communication (LD1), user LED (LD2), power LED (LD3)
  • Two push-buttons: USER and RESET
  • USB re-enumeration capability. Three different interfaces supported on USB:
    • Virtual COM port
    • Mass storage
    • Debug port
  • Support of wide choice of Integrated Development Environments (IDEs) including:
    • IAR
    • ARM Keil
    • GCC-based IDEs

More information about STM32F103RB can be found here:

Supported Features

The Zephyr nucleo_f103rb board configuration supports the following hardware features:

Interface Controller Driver/Component
NVIC on-chip nested vector interrupt controller
UART on-chip serial port-polling; serial port-interrupt
PINMUX on-chip pinmux
GPIO on-chip gpio
CLOCK on-chip reset and clock control
FLASH on-chip flash memory
IWDG on-chip independent watchdog

Other hardware features are not yet supported in this Zephyr port.

The default configuration can be found in the defconfig file: boards/arm/nucleo_f103rb/nucleo_f103rb_defconfig

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.

Board connectors:

Nucleo F103RB connectors

Default Zephyr Peripheral Mapping:

  • UART_1_TX : PA9
  • UART_1_RX : PA10
  • UART_2_TX : PA2
  • UART_2_RX : PA3

For mode details please refer to STM32 Nucleo-64 board User Manual [4].

Programming and Debugging

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

Flashing

Nucleo F103RB board includes an ST-LINK/V2-1 embedded debug tool interface. This interface is supported by the openocd version included in the Zephyr SDK.

Flashing an application to Nucleo F103RB

Here is an example for the Blinky Application application.

# On Linux/macOS
cd $ZEPHYR_BASE/samples/basic/blinky
mkdir build && cd build

# On Windows
cd %ZEPHYR_BASE%\samples\basic\blinky
mkdir build & cd build

# Use cmake to configure a Ninja-based build system:
cmake -GNinja -DBOARD=nucleo_f103rb ..

# Now run ninja on the generated build system:
ninja
ninja 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 Blinky Application application.

# On Linux/macOS
cd $ZEPHYR_BASE/samples/basic-blinky
# If you already made a build directory (build) and ran cmake, just 'cd build' instead.
mkdir build && cd build

# On Windows
cd %ZEPHYR_BASE%\samples\basic-blinky
# If you already made a build directory (build) and ran cmake, just 'cd build' instead.
mkdir build & cd build

# Use cmake to configure a Ninja-based build system:
cmake -GNinja -DBOARD=nucleo_f103rb ..

# Now run ninja on the generated build system:
ninja debug