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
Curiosity PIC32 MZ EF development board is a fully integrated 32-bit development platform featuring the high-performance PIC32MZ EF Series (PIC32MZ2048EFM) that has a 2MB Flash, 512KB RAM, integrated FPU, Crypto accelerator, and excellent connectivity options. It includes an integrated programmer and debugger, requiring no additional hardware. Users can expand
functionality through MIKROE mikroBUS™ Click™ adapter boards, add Ethernet connectivity with the Microchip PHY daughter board, add WiFi connectivity capability using the Microchip expansions boards, and add audio input and output capability with Microchip audio daughter boards. These boards are fully integrated into PIC32’s powerful software framework, MPLAB Harmony,
which provides a flexible and modular interface to application development a rich set of inter-operable software stacks (TCP-IP, USB), and easy-to-use features. The Curiosity PIC32 MZ EF development board offers expansion capabilities making it an excellent choice for a rapid prototyping board in Connectivity, IOT, and general-purpose applications.
Microcontroller Overview
MCU Card / MCU

Architecture
PIC32
MCU Memory (KB)
2048
Silicon Vendor
Microchip
Pin count
100
RAM (Bytes)
524288
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Click board™ Schematic

Step by step
Project assembly
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 );
}
int main ( void )
{
/* Do not remove this line or clock might not be set correctly. */
#ifdef PREINIT_SUPPORTED
preinit();
#endif
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END
Additional Support
Resources
Category:OLED































