SNVU849A May   2023  – September 2024 LP5890 , LP5891 , LP5891-Q1 , TLC6983 , TLC6984

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
  5. 2Software Setup
  6. 3Sample Code Structure
    1. 3.1 Design Parameters
    2. 3.2 Flow Diagram
    3. 3.3 System Setup
    4. 3.4 Diagnostics
    5. 3.5 Demo
  7. 4Revision History

Introduction

The sample code showcases the ability to light up the LEDs on the LP5891Q1EVM, LP5891EVM, LP5890EVM, TLC6984EVM, and TLC6983EVM. Each EVM has its own sample code. However, the only difference is in the file led_driver.h to select the used LED driver IC. This helps the user to be able to light up the EVM without any modification to the sample code.

There are two modes in the code: animation and simple test. The animation mode is selected by default. Section 3.3 describes how to change between the modes. In the animation mode two frames are used to scroll left, right, up, and down and to fade in and fade out according to a predefined sequence. The first frame is a Texas Instruments logo of 32x32 RGB pixels and the second frame a rainbow pattern of 48x32 RGB pixels. This means that not always the full frame is shown on the LED display of the EVM. Examples of this can be seen in Section 3.5. It is outside the scope of this document to explain how the frames in the sample code are generated.

In the simple test mode, the user can use some predefined APIs to light up the LED board, perform diagnostics, or build custom Continuous Clock Serial Interface (CCSI) commands. The sample code comes with turning on all RGB LEDs which results in a white display. In addition, every frame, diagnostics is executed. For more information about diagnostics see Section 3.4.

The LP5891Q1EVM, LP5891EVM, and LP5890EVM can be paired with LP5899DYYEVM. Section 3.3 describes how to enable the pairing. After enabling, the LAUCHXL-F280039C's SPI is used to communicate to LP5899DYYEVM instead of the LAUCHXL-F280039C's CLB (Configurable Logic Block) to communicate to LP589X(Q1)EVM. Moreover, additional diagnostics is enabled.

The predefined APIs in the sample code automatically adjust to the specified system. More detail about the system specification can be found in Section 3.3.