Unleash your creative potential with MI9639BO-B2 and PIC18LF46K42
Shine brighter with monochrome
Published Sep 15, 2023
Click board™
OLED B Click
Dev. board
EasyPIC v8
Compiler
NECTO Studio
MCU
PIC18LF46K42
See how our OLED solution empowers you to push the boundaries of design, functionality, and energy efficiency, making your products stand out in the market
A
A
Hardware Overview
How does it work?
OLED B Click is based on the MI9639BO-B2, a 19.3x7.8mm 96x39px light blue monochrome passive matrix OLED display from Multi-Inno Technology. The MI9639BO-B2 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, vertical and horizontal scrolling functions, and much more accessible through the I2C serial 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 loss of contrast due to bleed-through of the backlight in the "off" pixels. OLEDs, being emissive, have a consistent contrast ratio greater than 100:1 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-B2 is made from a thin film of an organic compound that emits light when exposed to a current. A small monochrome display like this represents an ideal solution for displaying text or icons. The MI9639BO-B2 display is bright, has a wide viewing angle, and has low power consumption. In addition to the display's main power supply, taken from the +3.3V microBUS™ power rail, the MI9639BO-B2 has another power pin, more precisely, the power supply for the DC/DC converter circuit. This pin is the power supply pin for the internal buffer of the DC/DC voltage converter. Therefore, for this pin, the Click board™ uses a low dropout linear regulator AP7331 from Diodes Incorporated, providing a 3.6V power supply out of 5V mikroBUS™ rail. OLED B Click communicates with MCU using the standard I2C 2-Wire interface to read data and configure settings. It allows the communication-enable
feature to be routed to the CS pin of the mikroBUS™ socket, enabling the OLED B Click for MCU communication only when the CS pin is pulled to a low logic state. In addition, it has two more pins. The first is related to the reset function, routed to the RST pin on the mikroBUS™ socket (when the pin is in a low logic state, the initialization of the chip is executed), and the second is labeled as D/C and routed to the PWM pin on the mikroBUS™ socket is I2C slave address selection pin. 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 AP7331 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
EasyPIC v8 is a development board specially designed for the needs of rapid development of embedded applications. It supports many high pin count 8-bit PIC microcontrollers from Microchip, regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer. 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, EasyPIC v8 provides a fluid and immersive working experience, allowing access anywhere and under any
circumstances at any time. Each part of the EasyPIC v8 development board contains the components necessary for the most efficient operation of the same board. In addition to the advanced integrated CODEGRIP programmer/debugger module, which offers many valuable programming/debugging options and seamless integration with the Mikroe software environment, the board 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 DEVICE, and CAN are also included, including the well-established mikroBUS™ standard, two display options (graphical and character-based LCD), and several different DIP sockets. These sockets cover a wide range of 8-bit PIC MCUs, from the smallest PIC MCU devices with only eight up to forty pins. EasyPIC 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
Architecture
PIC
MCU Memory (KB)
64
Silicon Vendor
Microchip
Pin count
40
RAM (Bytes)
4096
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 EasyPIC v8 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 B Click driver.
Key functions:
oledb_display_picture- This function allows user to display picture for on the screenoledb_clear_display- This function clears SSD1306 controller displayoledb_write_string- This function writes a text string from the selected position in a 5x7 or 6x8 font size
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 OLEDB Click example
*
# Description
* This example demonstrates the use (control) of the OLED B 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 "oledb.h"
#include "resources.h"
static oledb_t oledb;
static log_t logger;
void application_init ( void ) {
log_cfg_t log_cfg; /**< Logger config object. */
oledb_cfg_t oledb_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.
oledb_cfg_setup( &oledb_cfg );
OLEDB_MAP_MIKROBUS( oledb_cfg, MIKROBUS_1 );
err_t init_flag = oledb_init( &oledb, &oledb_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 ( ; ; );
}
oledb_default_cfg ( &oledb );
log_info( &logger, " Application Task " );
}
void application_task ( void ) {
uint8_t i;
oledb_display_picture( &oledb, oledb_img );
Delay_ms( 500 );
oledb_send( &oledb, OLEDB_INVERTDISPLAY, OLEDB_COMMAND );
Delay_ms( 500 );
oledb_send( &oledb, OLEDB_NORMALDISPLAY, OLEDB_COMMAND );
Delay_ms( 500 );
oledb_send( &oledb, OLEDB_INVERTDISPLAY, OLEDB_COMMAND );
Delay_ms( 500 );
oledb_send( &oledb, OLEDB_NORMALDISPLAY, OLEDB_COMMAND );
Delay_ms( 300 );
for (i = 0xAF; i > 0x00; i--) {
oledb_set_contrast( &oledb, i );
Delay_ms( 5 );
}
for (i = 0x00; i < 0xAF; i++) {
oledb_set_contrast( &oledb, i );
Delay_ms( 5 );
}
oledb_scroll_right( &oledb, 0x00, 0x05 );
Delay_ms( 1000 );
oledb_stop_scroll( &oledb );
oledb_display_picture( &oledb, oledb_img );
oledb_scroll_left( &oledb, 0x00, 0x05 );
Delay_ms( 1000 );
oledb_stop_scroll( &oledb );
oledb_display_picture( &oledb, oledb_img );
oledb_scroll_diag_right( &oledb, 0x00, 0x05 );
Delay_ms( 1000 );
oledb_stop_scroll( &oledb );
oledb_display_picture( &oledb, oledb_img );
oledb_scroll_diag_left( &oledb, 0x00, 0x05 );
Delay_ms( 1000 );
oledb_stop_scroll( &oledb );
}
void main ( void ) {
application_init( );
for ( ; ; ) {
application_task( );
}
}
// ------------------------------------------------------------------------ END
