Unleash your creativity and showcase your content in style with MI9639BO-W and TM4C129ENCPDT
Illuminating possibilities
Published Jun 21, 2023
Click board™
OLED W Click
Dev Board
Fusion for Tiva v8
Compiler
NECTO Studio
MCU
TM4C129ENCPDT
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
Fusion for TIVA v8 is a development board specially designed for the needs of rapid development of embedded applications. It supports a wide range of microcontrollers, such as different 32-bit ARM® Cortex®-M based MCUs from Texas Instruments, regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer over a WiFi network. The development board is well organized and designed so that the end-user has all the necessary elements, such as switches, buttons, indicators, connectors, and others, in one place. Thanks to innovative manufacturing technology, Fusion for TIVA v8 provides a fluid and immersive working experience, allowing access
anywhere and under any circumstances at any time. Each part of the Fusion for TIVA v8 development board contains the components necessary for the most efficient operation of the same board. An advanced integrated CODEGRIP programmer/debugger module offers many valuable programming/debugging options, including support for JTAG, SWD, and SWO Trace (Single Wire Output)), and seamless integration with the Mikroe software environment. Besides, it also includes a clean and regulated power supply module for the development board. It can use a wide range of external power sources, including a battery, an external 12V power supply, and a power source via the USB Type-C (USB-C) connector.
Communication options such as USB-UART, USB HOST/DEVICE, CAN (on the MCU card, if supported), and Ethernet is also included. In addition, it also has the well-established mikroBUS™ standard, a standardized socket for the MCU card (SiBRAIN standard), and two display options for the TFT board line of products and character-based LCD. Fusion for TIVA v8 is an integral part of the Mikroe ecosystem for rapid development. Natively supported by Mikroe software tools, it covers many aspects of prototyping and development thanks to a considerable number of different Click boards™ (over a thousand boards), the number of which is growing every day.
Microcontroller Overview
MCU Card / MCU
Type
8th Generation
Architecture
ARM Cortex-M4
MCU Memory (KB)
1024
Silicon Vendor
Texas Instruments
Pin count
128
RAM (Bytes)
262144
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 Fusion for Tiva v8 as your development board.
Track your results in real time
Application Output via UART Mode
1. Once the code example is loaded, pressing the "FLASH" button initiates the build process, and programs it on the created setup.
2. After the programming is completed, click on the Tools icon in the upper-right panel, and select the UART Terminal.
3. After opening the UART Terminal tab, first check the baud rate setting in the Options menu (default is 115200). If this parameter is correct, activate the terminal by clicking the "CONNECT" button.
4. Now terminal status changes from Disconnected to Connected in green, and the data is displayed in the Received data field.
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
