DSS Colorbar Test

Table of Contents

• Introduction
• Supported Combinations
• Steps to Run the Example
• See Also
• Sample Output

Introduction

This example tests the inbuilt colorbar generation of overlay manager of DSS. DSS has two overlay managers OVR1 and OVR2. Each overlay manager supports a simple internal color bar insertion in each display output path to enable testing of display output interface without using the frame buffer data from the memory.

The colors are: White, Yellow, Cyan, Green, Magenta, Red, Blue, Black. When internal colorbar is enabled, the overlay output data is replaced by the predefined ARGB48 color bar data .The example configures Video Port and Overlay managers using DSS driver IOCTLS. Since the colorbar is internal to DSS, there is no Video pipeline configuration required. The example configures Overlay Manager OVR1 to enable internal colorbar enable feature.

The example configures OLDI LVDS panel for Video Port 1. Please refer SK-LCD1 for panel details. The Video port timinng parameters are configured with respect to SK-LCD1. Timing parameters can be configured using sysconfig option.

The example integrates bootloading funtionality with SBL on OSPI bootmedia. It also integrates Device manager functionality. The SBL stage 2 thread boots all the cores along with HLOS like Linux. Refer SBL Booting Linux From OSPI for boot flow sequence.

Supported Combinations

Parameter	Value
CPU + OS	wkup-r5fss0-0 freertos
Toolchain	ti-arm-clang
Board	am62px-sk
Example folder	examples/drivers/dss/dss_colorbar_test

Steps to Run the Example

• This example integrates SBL on OSPI bootmedia which needs to be flashed on the EVM flash, along with sample application images for MCU R5 CPUs, HSM M4F and Linux Appimage.
• There is a default flash config file as shown below which flashes this SBL and the IPC RPMsg Linux echo applications

    ${SDK_INSTALL_PATH}/tools/boot/sbl_prebuilt/am62px-sk/default_sbl_ospi_linux_hs_fs.cfg
  

• Update the wkup-r5 image in the flash config with dss_colorbar_test image.

    # 2nd stage bootloader with DM is flashed at 0x80000 or to whatever offset your bootloader is configured for
    --file=../../examples/drivers/dss/dss_colorbar_test/am62px-sk/wkup-r5fss0-0_freertos/ti-arm-clang/dss_colorbar_test.release.appimage.hs_fs --operation=flash --flash-offset=0x80000
  

• To flash to the EVM, refer to Flash a Hello World example . Only when giving the flash config file, point to the default_sbl_ospi_linux_hs_fs.cfg shown above.
• Example, assuming SDK is installed at C:/ti/mcu_plus_sdk and this example and IPC application is built using makefiles, and Linux Appimage is already created, in Windows,

      cd C:/ti/mcu_plus_sdk/tools/boot
      python uart_uniflash.py -p COM13 --cfg=C:/ti/mcu_plus_sdk/tools/boot/sbl_prebuilt/am62px-sk/default_sbl_ospi_linux_hs_fs.cfg
  

• If Linux PC is used, assuming SDK is installed at ~/ti/mcu_plus_sdk

    cd ~/ti/mcu_plus_sdk
    python uart_uniflash.py -p /dev/ttyUSB0 --cfg=~/ti/mcu_plus_sdk/tools/boot/sbl_prebuilt/am62px-sk/default_sbl_ospi_linux_hs_fs.cfg
  

• Switch to OSPI NOR BOOT MODE and power on the EVM.

Attention

As the wake-up R5 is the device manager, it needs to be started by the SBL. So it can not be loaded through CCS. It should be flashed and booted through SBL.

See Also

DSS

Sample Output

Sciserver Testapp Built On: Dec  7 2023 14:12:00
Sciserver Version: v2023.11.0.0REL.MCUSDK.MM.NN.PP.bb
RM_PM_HAL Version: vMM.NN.PP
Starting Sciserver..... PASSED
DispApp_init() - DONE !!!
DSS colorbar application started...
Display create complete!!
Starting display ... !!!
Display in progress ... DO NOT HALT !!!
Display delete complete!!
DispApp_deInit() - DONE !!!
DSS colorbar test Passed!!

Display Output