NOTICE: The Processors Wiki will End-of-Life in December of 2020. It is recommended to download any files or other content you may need that are hosted on processors.wiki.ti.com. The site is now set to read only.

GSG: Executing the Graphics SDK Demos

From Texas Instruments Wiki
Jump to: navigation, search
{{#switchcategory:MSP430=<McuHitboxHeader/>|C2000=<McuHitboxHeader/>|Stellaris=<McuHitboxHeader/>|TMS570=<McuHitboxHeader/>|MCU=<McuHitboxHeader/>|MAVRK=<MAVRKHitboxHeader/>|<HitboxHeader/>}}

Content is no longer maintained and is being kept for reference only!

^ Up to main OMAP35x Graphics SDK Getting Started Guide Table of Contents

This section explains how to run the graphics demos provided with the OMAP35x Graphics SDK.

Building and Setting Up NFS based target file system[edit]

Refer Rebuilding Software:Installing_the_NFS_Target_File_System_with_Graphics_SDK_Demos for setting up the NFS target file system for executing the Graphics SDK Demos

Default Boot Parameter Settings[edit]

The boot parameter settings for OMAP35x EVM are similar to the settings as described in the OMAP35x EVM Getting Started Guide. Use the bootargs as mentioned below to execute the Graphics SDK demos. This is different from the bootargs used for running the OMAP3530 DVSDK demos and does not enable rotation and the memory available for linux operating system is 128MB or 256MB depending on the LPDDR part used in the processor board.

Boot parameter settings for NFS[edit]

Kindly note that the bootargs are required to be set as below while running the OMAP35x Graphics SDK demos from NFS file system

 OMAP3EVM # setenv bootargs console=ttyS0,115200n8 noinitrd rw ip=dhcp  root=/dev/nfs nfsroot=<nfshost>:<rootpath>,nolock mem=128M 

NOTE: Make sure that the size of the frame buffer is greater than 4MB. If not add omapfb.vram=”4M” to bootargs. You could check this by executing the following command

target$ cat /sys/devices/platform/omapfb/framebuffers

Running the Standalone Demos[edit]

Currently the demos do not start automatically on EVM power on. They need to be executed from the command line.

Running the Demos from Command Line[edit]

You can run the OMAP35x Graphics SDK demo applications from the Linux shell in a terminal window connected to the EVM board’s serial port.

Before running your graphics SDK demo application from the command line, it is necessary to install the appropriate SGX user libraries as well as kernel modules, based on the OMAP35x silicon version used in EVM and the debug or release version of the build being used. This is done by default, on DVEVM power up, when using the NFS based target file system built using the steps mentioned here.

In case the omap-demo script is not executed, kindly execute the following commands, after linux boot

target $ cd /etc/init.d
target $ ./omap-demo

This will install all the necessary SGX user modules and kernel modules as well as performs the necessary initializations. Executing omap-demo in turn calls the appropriate install.sh on the target, based on the silicon version and the build type (debug or release version) used. This will also execute the rc.pvr script to load kernel modules and initialize the relevant SGX modules.

In order to get the animations working for some of the OpenGLES1.x demos (ShadowTechniques and Optimized Mesh OGLES Demo), it is necessary to set the date and year appropriately as given below

target $ date -s 1970.01.01-01:01:01


Running Graphics SDK Sample Applications[edit]

These are standard Graphics SDK tests that are used to check the basic functionality of the graphics drivers. To run standard graphics SDK tests, perform the following steps:

target $ cd /usr/local/bin
target $ ./gles1test1 –t
target $ ./gles2test1 –t
target $ ./ovg_unit_test –t

To stop the above graphics SDK tests, press ctrl+c

Execute the ES1 texture stream test using the command given below. To stop gles1_texture_stream test, press ‘q’

target $ ./gles1_texture_stream

Execute the following commands given below to test the SGX feature tests. These tests end on their own except for the sgx_render_flip_test. In this case, press ctrl+c to stop the test.

target $ ./sgx_blit_test
target $ ./sgx_flip_test
target $ ./sgx_render_flip_test
target $ ./sgx_render_test

Running Graphics SDK OpenGL ES1.x Demos[edit]

To run OpenGL ES1.x demos, perform the following steps:

target $ cd /opt/gfxsdkdemos/ogles
target $ ./OGLESChameleonMan

This will execute the OGLESChameleonMan demo. Press ‘q’ on the host machine console window (TeraTerm or HyperTerminal or Minicom) to stop the demo.

Similarly, the user could execute other OpenGL ES1.x demos.

For more information and command line options on the demos, refer to the OpenGL ES1.x SDK user guide available under OMAP35x_Graphics_SDK_#_##_##_##\GFX_Linux_SDK\OGLES\SDKPackage

Running Graphics SDK OpenGL ES2.0 Demos[edit]

To run OpenGLES2.0 demos, perform the following steps:

target $ cd /opt/gfxsdkdemos/ogles2
target $ ./OGLES2Shaders

This will execute the OGLES2Shaders demo. Press ‘q’ on the host machine console window (TeraTerm or HyperTerminal or Minicom) to stop the demo.

Similarly, the user could execute other OpenGL ES2.0 demos.

For more information and command line options on the demos, refer to the OpenGL ES2.x SDK user guide available under OMAP35x_Graphics_SDK_#_##_##_##\GFX_Linux_SDK\OGLES2\SDKPackage

E2e.jpg {{
  1. switchcategory:MultiCore=
  • For technical support on MultiCore devices, please post your questions in the C6000 MultiCore Forum
  • For questions related to the BIOS MultiCore SDK (MCSDK), please use the BIOS Forum

Please post only comments related to the article GSG: Executing the Graphics SDK Demos here.

Keystone=
  • For technical support on MultiCore devices, please post your questions in the C6000 MultiCore Forum
  • For questions related to the BIOS MultiCore SDK (MCSDK), please use the BIOS Forum

Please post only comments related to the article GSG: Executing the Graphics SDK Demos here.

C2000=For technical support on the C2000 please post your questions on The C2000 Forum. Please post only comments about the article GSG: Executing the Graphics SDK Demos here. DaVinci=For technical support on DaVincoplease post your questions on The DaVinci Forum. Please post only comments about the article GSG: Executing the Graphics SDK Demos here. MSP430=For technical support on MSP430 please post your questions on The MSP430 Forum. Please post only comments about the article GSG: Executing the Graphics SDK Demos here. OMAP35x=For technical support on OMAP please post your questions on The OMAP Forum. Please post only comments about the article GSG: Executing the Graphics SDK Demos here. OMAPL1=For technical support on OMAP please post your questions on The OMAP Forum. Please post only comments about the article GSG: Executing the Graphics SDK Demos here. MAVRK=For technical support on MAVRK please post your questions on The MAVRK Toolbox Forum. Please post only comments about the article GSG: Executing the Graphics SDK Demos here. For technical support please post your questions at http://e2e.ti.com. Please post only comments about the article GSG: Executing the Graphics SDK Demos here.

}}

Hyperlink blue.png Links

Amplifiers & Linear
Audio
Broadband RF/IF & Digital Radio
Clocks & Timers
Data Converters

DLP & MEMS
High-Reliability
Interface
Logic
Power Management

Processors

Switches & Multiplexers
Temperature Sensors & Control ICs
Wireless Connectivity

{{#switchcategory:MSP430=<McuHitboxFooter/>|C2000=<McuHitboxFooter/>|Stellaris=<McuHitboxFooter/>|TMS570=<McuHitboxFooter/>|MCU=<McuHitboxFooter/>|MAVRK=<MAVRKHitboxFooter/>|<HitboxFooter/>}}