TOP Contributors

  1. MIKROE (2784 codes)
  2. Alcides Ramos (405 codes)
  3. Shawon Shahryiar (307 codes)
  4. jm_palomino (133 codes)
  5. Bugz Bensce (97 codes)
  6. S P (73 codes)
  7. dany (71 codes)
  8. MikroBUS.NET Team (35 codes)
  9. NART SCHINACKOW (34 codes)
  10. Armstrong Subero (27 codes)

Most Downloaded

  1. Timer Calculator (142055 times)
  2. FAT32 Library (75281 times)
  3. Network Ethernet Library (59487 times)
  4. USB Device Library (49510 times)
  5. Network WiFi Library (45284 times)
  6. FT800 Library (44908 times)
  7. GSM click (31423 times)
  8. mikroSDK (30434 times)
  9. microSD click (27795 times)
  10. PID Library (27619 times)
Libstock prefers package manager

Package Manager

We strongly encourage users to use Package manager for sharing their code on Libstock website, because it boosts your efficiency and leaves the end user with no room for error. [more info]

< Back
mikroSDK Library

eINK 2.13 inch display

Rating:

0

Author: MIKROE

Last Updated: 2022-05-24

Package Version: 2.0.0.4

mikroSDK Library: 2.0.0.0

Category: Electronic Paper Display

Downloaded: 201 times

Not followed.

License: MIT license  

eINK click is an adapter Click boardâ„¢, used to interface a compatible eINK display with the host MCU.

No Abuse Reported

Do you want to subscribe in order to receive notifications regarding "eINK 2.13 inch display" changes.

Do you want to unsubscribe in order to stop receiving notifications regarding "eINK 2.13 inch display" changes.

Do you want to report abuse regarding "eINK 2.13 inch display".

  • mikroSDK Library 1.0.0.0
  • Comments (0)

mikroSDK Library Blog


eINK 2.13 inch display

eINK click is an adapter Click boardâ„¢, used to interface a compatible eINK display with the host MCU.

eink_click_bundle213inch.png

click Product page


Click library

  • Author : MikroE Team
  • Date : Feb 2020.
  • Type : SPI type

Software Support

We provide a library for the eInk213Inch Click as well as a demo application (example), developed using MikroElektronika compilers. The demo can run on all the main MikroElektronika development boards.

Package can be downloaded/installed directly form compilers IDE(recommended way), or downloaded from our LibStock, or found on mikroE github account.

Library Description

This library contains API for eInk213Inch Click driver.

Standard key functions :

  • Config Object Initialization function.

    void eink_213inch_cfg_setup ( eink_213inch_cfg_t *cfg );

  • Initialization function.

    EINK213INCH_RETVAL eink_213inch_init ( eink_213inch_t ctx, eink_213inch_cfg_t cfg );

Example key functions :

  • Set LUT table

    void eink_213_set_lut ( eink_213inch_t ctx, const uint8_t lut, uint8_t n_bytes );

  • Function for draw text on the screen

    void eink_213_text ( eink_213inch_t ctx, char text, eink_213inch_set_text_t *text_set );

  • Display image function

    void eink_213_display_image ( eink_213inch_t ctx, const uint8_t image_buffer );

Examples Description

This application demonstrates the use of eINK click board.

The demo application is composed of two sections :

Application Init

Initializes the driver and configures the click board for 2.13 inch eINK display. After that, if the TEXT mode is supported, shows a desired text messages on the display.


void application_init ( void )
{
    eink_213inch_cfg_t cfg;
    eink_213inch_font_t cfg_font;
    eink_213inch_set_text_t set_text;

    //  Click initialization.

    eink_213inch_cfg_setup( &cfg );
    EINK213INCH_MAP_MIKROBUS( cfg, MIKROBUS_1 );
    eink_213inch_init( &eink_213inch, &cfg );

    eink_213_start_config( &eink_213inch );
    eink_213_set_lut( &eink_213inch, &EINK213_BIG_LUT_TABLE[ 0 ], 70 );
    Delay_ms( 1000 );

#ifndef IMAGE_MODE_ONLY
    cfg_font.p_font = &guiFont_Tahoma_18_Regular[ 0 ]; 
    cfg_font.color = EINK213_SCREEN_COLOR_WHITE;
    cfg_font.orientation = EINK213_FO_HORIZONTAL;  
    eink_213_set_font( &eink_213inch, &cfg_font );

    set_text.n_char = 4;
    set_text.text_x = 5;
    set_text.text_y = 50;
    eink_213_text( &eink_213inch, &demo_text[ 0 ], &set_text );

    cfg_font.p_font = &guiFont_Tahoma_10_Regular[ 0 ]; 
    cfg_font.color = EINK213_SCREEN_COLOR_WHITE;
    cfg_font.orientation = EINK213_FO_HORIZONTAL; 
    eink_213_set_font( &eink_213inch, &cfg_font );

    set_text.n_char = 7;
    set_text.text_x = 5;
    set_text.text_y = 90;
    eink_213_text( &eink_213inch, &demo_text1[ 0 ], &set_text );

    cfg_font.p_font = &guiFont_Tahoma_8_Regular[ 0 ]; 
    cfg_font.color = EINK213_SCREEN_COLOR_WHITE;
    cfg_font.orientation = EINK213_FO_HORIZONTAL; 
    eink_213_set_font( &eink_213inch, &cfg_font );

    set_text.n_char = 9;
    set_text.text_x = 5;
    set_text.text_y = 120;
    eink_213_text( &eink_213inch, &demo_text2[ 0 ], &set_text );
#endif
    Delay_ms( 1000 );
}

Application Task

Draws four demo images to the display with a one-second delay between each drawing.


void application_task ( void )
{
    eink_213_display_image( &eink_213inch, &demoImage_light[ 0 ] );
    Delay_1sec( );
    eink_213_display_image( &eink_213inch, &demoImage_dark[ 0 ] );
    Delay_1sec( );
    eink_213_display_image( &eink_213inch, &demoImage_light_180[ 0 ] );
    Delay_1sec( );
    eink_213_display_image( &eink_213inch, &demoImage_dark_180[ 0 ] );
    Delay_1sec( );
} 

Note

Due to insuficient RAM memory, only the IMAGE mode is supported with 8-bit PIC microcontrollers.

The full application code, and ready to use projects can be installed directly form compilers IDE(recommneded) or found on LibStock page or mikroE GitHub accaunt.

Other mikroE Libraries used in the example:

  • MikroSDK.Board
  • MikroSDK.Log
  • Click.eInk213Inch

Additional notes and informations

Depending on the development board you are using, you may need USB UART click, USB UART 2 Click or RS232 Click to connect to your PC, for development systems with no UART to USB interface available on the board. The terminal available in all Mikroelektronika compilers, or any other terminal application of your choice, can be used to read the message.


ALSO FROM THIS AUTHOR

nvSRAM 2 Click

0

nvSRAM 2 Click is a compact add-on board that contains the most reliable nonvolatile memory. This board features the CY14B101Q, a 1Mbit nvSRAM organized as 128K words of 8 bits each with a nonvolatile element in each memory cell from Cypress Semiconductor. The embedded nonvolatile elements incorporate the QuantumTrap technology and provide highly reliable nonvolatile storage of data. Data transfer, initiated by the user through SPI commands, from SRAM to the nonvolatile elements takes place automatically at Power-Down. On the other hand, during the Power-Up, data is restored to the SRAM from the nonvolatile memory. This Click board™ is suitable for all applications that require fast access and high reliability of stored data, and unlimited endurance.

[Learn More]

Smart DOF 2 Click

0

Smart DOF 2 Click is a compact add-on board with a highly advanced integrated 6-axis IMU measurement unit. This board features the LSM6DSV16XTR, a high-performance 6-axis IMU with sensor fusion, ASC, MLC, Qvar, and OIS/EIS paths from STMicroelectronics. The IMU unit features an accelerometer and gyroscope that can be turned off independently of each other, still allowed to have different ODRs and power modes. The unit can be configured as a finite state machine (FSM), machine learning core (MLC), and Qvar sensing.

[Learn More]

MCP251863 Click

0

MCP251863 Click is a compact add-on board representing a complete CAN solution used as a control node in a CAN network. This board features the MCP251863, IC representing a compact solution with a controller and a transceiver in one package, the MCP2518FD and ATA6563 from Microchip. The ATA6563, a low-level physical layer IC (PHY), provides a physical connection with the CAN bus itself, while the CAN controller MCP2518FD represents an interface between the MCU and the PHY. It features three operating modes with dedicated fail-safe features, remote wake-up via CAN, and ideally passive behavior when powered off on the CAN bus. This Click board™ is suitable for developing a wide range of automotive diagnostic applications, even on MCUs that don’t support CAN interface.

[Learn More]