Unleash your creativity and showcase your content in style with MI9639BO-W and STM32F031K6
Illuminating possibilities
Published Oct 01, 2024
Click board™
OLED W Click
Dev. board
Nucleo 32 with STM32F031K6 MCU
Compiler
NECTO Studio
MCU
STM32F031K6
Capture attention and engage your audience with our mesmerizing 96x39px OLED solution, delivering stunning visuals in a compact form
A
A
Hardware Overview
How does it work?
OLED W Click is based on the MI9639BO-W, a 19.3x7.8mm 96x39px white light monochrome passive matrix OLED display from Multi-Inno Technology. The MI9639BO-W display features an SSD1306, a 128x64 dot-matrix OLED/PLED segment/common driver with a controller. The controller has built-in functionalities like contrast control (256-step brightness control), normal or inverse image display, and vertical and horizontal scrolling functions, and more accessible through the configurable host interface. OLEDs are emissive and don't require a separate backlight as LCD technology does, reducing the OLED display's overall power consumption compared to LCDs. It also does not suffer from contrast loss due to the backlight's bleed-through in the "off" pixels. OLEDs, being emissive, have a consistent contrast ratio with no limitation in viewing angle. In addition, they don't suffer from temperature-
related response time delays and contrast changes. Like any OLED display, the MI9639BO-W is made from a thin film of an organic compound that emits bright light when exposed to a current with a wide viewing angle and low power consumption, representing an ideal solution for displaying text or icons. OLED W Click allows using both I2C and SPI interfaces. The selection can be made by positioning SMD jumpers labeled SEL COMM in an appropriate position. Note that all the jumpers' positions must be on the same side, or the Click board™ may become unresponsive. In addition, it uses two more pins. The first is related to the reset function, routed to the RST pin on the mikroBUS™ socket. When this pin is in a low logic state, the initialization of the SSD1306 is executed. The second pin is labeled as D/C and routed to the PWM pin on the mikroBUS™ socket representing the I2C slave address selection pin in a case of
selected I2C communication. In addition to the display's main power supply, taken from the +3.3V microBUS™ power rail, the MI9639BO-W has another power pin, more precisely, the power supply for its DC/DC converter circuit. This pin represents the power supply pin for the internal buffer of the DC/DC voltage converter, which is why this Click board™ uses a low dropout linear regulator AP7331 from Diodes Incorporated, providing a 3.6V power supply out of 5V mikroBUS™ rail. This Click board™ is designed to be operated only with a 3.3V logic voltage level, while 5V is used as a supply voltage of the LDO. The board must perform appropriate logic voltage level conversion before use with MCUs with different logic levels. However, the Click board™ comes equipped with a library containing easy-to-use functions and an example code that can be used, as a reference, for further development.
Features overview
Development board
Nucleo 32 with STM32F031K6 MCU board provides an affordable and flexible platform for experimenting with STM32 microcontrollers in 32-pin packages. Featuring Arduino™ Nano connectivity, it allows easy expansion with specialized shields, while being mbed-enabled for seamless integration with online resources. The
board includes an on-board ST-LINK/V2-1 debugger/programmer, supporting USB reenumeration with three interfaces: Virtual Com port, mass storage, and debug port. It offers a flexible power supply through either USB VBUS or an external source. Additionally, it includes three LEDs (LD1 for USB communication, LD2 for power,
and LD3 as a user LED) and a reset push button. The STM32 Nucleo-32 board is supported by various Integrated Development Environments (IDEs) such as IAR™, Keil®, and GCC-based IDEs like AC6 SW4STM32, making it a versatile tool for developers.
Microcontroller Overview
MCU Card / MCU
Architecture
ARM Cortex-M0
MCU Memory (KB)
32
Silicon Vendor
STMicroelectronics
Pin count
32
RAM (Bytes)
4096
You complete me!
Accessories
Click Shield for Nucleo-32 is the perfect way to expand your development board's functionalities with STM32 Nucleo-32 pinout. The Click Shield for Nucleo-32 provides two mikroBUS™ sockets to add any functionality from our ever-growing range of Click boards™. We are fully stocked with everything, from sensors and WiFi transceivers to motor control and audio amplifiers. The Click Shield for Nucleo-32 is compatible with the STM32 Nucleo-32 board, providing an affordable and flexible way for users to try out new ideas and quickly create prototypes with any STM32 microcontrollers, choosing from the various combinations of performance, power consumption, and features. The STM32 Nucleo-32 boards do not require any separate probe as they integrate the ST-LINK/V2-1 debugger/programmer and come with the STM32 comprehensive software HAL library and various packaged software examples. This development platform provides users with an effortless and common way to combine the STM32 Nucleo-32 footprint compatible board with their favorite Click boards™ in their upcoming projects.
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Click board™ Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the Nucleo 32 with STM32F031K6 MCU as your development board.
Track your results in real time
Application Output
1. Application Output - In Debug mode, the 'Application Output' window enables real-time data monitoring, offering direct insight into execution results. Ensure proper data display by configuring the environment correctly using the provided tutorial.
2. UART Terminal - Use the UART Terminal to monitor data transmission via a USB to UART converter, allowing direct communication between the Click board™ and your development system. Configure the baud rate and other serial settings according to your project's requirements to ensure proper functionality. For step-by-step setup instructions, refer to the provided tutorial.
3. Plot Output - The Plot feature offers a powerful way to visualize real-time sensor data, enabling trend analysis, debugging, and comparison of multiple data points. To set it up correctly, follow the provided tutorial, which includes a step-by-step example of using the Plot feature to display Click board™ readings. To use the Plot feature in your code, use the function: plot(*insert_graph_name*, variable_name);. This is a general format, and it is up to the user to replace 'insert_graph_name' with the actual graph name and 'variable_name' with the parameter to be displayed.
Software Support
Library Description
This library contains API for OLED W Click driver.
Key functions:
oledw_send- This function sends commands or data to OLED W click.oledw_display_picture- This function allows user to display picture for page addressing mode.oledw_set_contrast- This function sets the display contrast level (0 to 255).
Open Source
Code example
The complete application code and a ready-to-use project are available through the NECTO Studio Package Manager for direct installation in the NECTO Studio. The application code can also be found on the MIKROE GitHub account.
/*!
* @file main.c
* @brief OLEDW Click example
*
# Description
* This example demonstrates the use (control) of the OLED W display.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Configures the microcontroller for communication and initializes the click
* board to default state.
*
* ## Application Task
* This section contains the main program that is executed showing a practical
* example on how to use the implemented functions.
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "oledw.h"
#include "resources.h"
static oledw_t oledw;
static log_t logger;
void application_init ( void ) {
log_cfg_t log_cfg; /**< Logger config object. */
oledw_cfg_t oledw_cfg; /**< Click config object. */
/**
* Logger initialization.
* Default baud rate: 115200
* Default log level: LOG_LEVEL_DEBUG
* @note If USB_UART_RX and USB_UART_TX
* are defined as HAL_PIN_NC, you will
* need to define them manually for log to work.
* See @b LOG_MAP_USB_UART macro definition for detailed explanation.
*/
LOG_MAP_USB_UART( log_cfg );
log_init( &logger, &log_cfg );
Delay_ms( 100 );
log_info( &logger, " Application Init " );
// Click initialization.
oledw_cfg_setup( &oledw_cfg );
OLEDW_MAP_MIKROBUS( oledw_cfg, MIKROBUS_1 );
err_t init_flag = oledw_init( &oledw, &oledw_cfg );
if ( ( I2C_MASTER_ERROR == init_flag ) || ( SPI_MASTER_ERROR == init_flag ) ) {
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
oledw_default_cfg ( &oledw );
log_info( &logger, " Application Task " );
}
void application_task ( void ) {
uint8_t i;
oledw_display_picture( &oledw, oledw_img );
Delay_ms( 500 );
oledw_send( &oledw, OLEDW_INVERTDISPLAY, OLEDW_COMMAND );
Delay_ms( 500 );
oledw_send( &oledw, OLEDW_NORMALDISPLAY, OLEDW_COMMAND );
Delay_ms( 500 );
oledw_send( &oledw, OLEDW_INVERTDISPLAY, OLEDW_COMMAND );
Delay_ms( 500 );
oledw_send( &oledw, OLEDW_NORMALDISPLAY, OLEDW_COMMAND );
Delay_ms( 300 );
for (i = 0xAF; i > 0x00; i--) {
oledw_set_contrast( &oledw, i );
Delay_ms( 5 );
}
for (i = 0x00; i < 0xAF; i++) {
oledw_set_contrast( &oledw, i );
Delay_ms( 5 );
}
oledw_scroll_right( &oledw, 0x00, 0x05 );
Delay_ms( 1000 );
oledw_stop_scroll( &oledw );
oledw_display_picture( &oledw, oledw_img );
oledw_scroll_left( &oledw, 0x00, 0x05 );
Delay_ms( 1000 );
oledw_stop_scroll( &oledw );
oledw_display_picture( &oledw, oledw_img );
oledw_scroll_diag_right( &oledw, 0x00, 0x05 );
Delay_ms( 1000 );
oledw_stop_scroll( &oledw );
oledw_display_picture( &oledw, oledw_img );
oledw_scroll_diag_left( &oledw, 0x00, 0x05 );
Delay_ms( 1000 );
oledw_stop_scroll( &oledw );
}
void main ( void ) {
application_init( );
for ( ; ; ) {
application_task( );
}
}
// ------------------------------------------------------------------------ END
