NOTICE: The Processors Wiki will End-of-Life on January 15, 2021. 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: AM35x and OMAP35x Graphics SDK Additional Procedures

From Texas Instruments Wiki
Jump to: navigation, search

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

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

Using the PIXMAP surface for Drawing[edit]

Using Pixmap needs CMEM module to be inserted. CMEM is part of Linuxutils and can be downloaded from the appropriate DVSDK packages.

Buffers can be exchanged with the SGX rendering system using specific pixmap structure format, and is described in SGXPERF example code (Refer TEST8) at,

https://gforge.ti.com/gf/project/gleslayer/scmsvn/?action=browse&path=%2Ftrunk%2FPackages%2FOMAP3_Graphics_SDK%2F

Switching between FrontEGL and FlipEGL Modes[edit]

When using FrontEGL, SGX fb updates happen directly on single framebuffer (front buffer). Not really recommended except for SGX benchmarking as it will result tearing artifacts at high resolution and frame rates.

FlipEGL uses ping-pong scheme for graphics updates and this is the default EGL library used if /etc/powervr.ini is not present.

Modify the powervr.ini file under the <your_target_file_system>/etc/ to select between the FrontEGL or FlipEGL mode.

Flip support requires increasing the virtual yres size in fb0 plane and allocating appropriate memory for framebuffer.

Use the following command to increase the virtual yres size in fb0 plane. The vyres size needs to be set to three times the height of the screen size for triple buffering. For eg:- OMAP3 EVM LCD fb with dimensions 480x640

target $ fbset -vyres 1920 

Switching the display output from LCD to DVI[edit]

NOTE :DVI output for AM35x is not supported in PSP release 03.

Switching the display output from LCD to DVI during boot time[edit]

This can be done by changing in the bootargs to include the following

omapdss.def_disp="dvi" 

For example, in case of NFS mount

OMAP3EVM # setenv bootargs 'console=ttyS0,115200n8=noinitrd=rw ip=dhcp 
root=/dev/nfs nfsroot=<your nfs_path>,nolock, mem=128M vram=8M 
omapfb.vram=0:4M,1:3M,2:3M omapdss.def_disp="dvi"'

Switching the display output from LCD to DVI during run time after boot[edit]

Once the EVM is booted, you can change the output display from LCD to DVI from the Linux shell in a terminal window connected to the EVM board’s serial port.

Issue following commands to switch output device from LCD to DVI

Step 1:

target $ echo 0 > /sys/devices/platform/omapdss/display0/enabled
target $ echo "" > /sys/devices/platform/omapdss/manager0/display
target $ fbset -fb /dev/fb0 -xres 640 -yres 480 -vxres 640 -vyres 480
target $ echo "dvi" > /sys/devices/platform/omapdss/manager0/display
target $ echo 1 > /sys/devices/platform/omapdss/display2/enabled
target $ fbset -fb /dev/fb0 -xres 640 -yres 480 -vxres 640 -vyres 480


Step 2:

target $ fbset -depth 32 -rgba 8/16,8/8,8/0,8/24
target $ /etc/init.d/rc.pvr stop
target $ /etc/init.d/rc.pvr start

After this, the demos should run properly on DVI.

Testing the support for ARGB8888 in Frame Buffer Driver[edit]

The ARGB8888 is supported by default in DVI mode.For DVI mode boot bootargs need to be changed as given below.

OMAP3EVM # setenv bootargs 'console=ttyS0,115200n8=noinitrd=rw ip=dhcp 
root=/dev/nfs nfsroot=<your nfs_path>,nolock, mem=128M vram=8M 
omapfb.vram=0:4M,1:3M,2:3M omapdss.def_disp="dvi"'

Note that if you are switching to ARGB8888 mode after bootup it is mandatory to reload omaplfb.ko kernel module

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: AM35x and OMAP35x Graphics SDK Additional Procedures 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: AM35x and OMAP35x Graphics SDK Additional Procedures here.

C2000=For technical support on the C2000 please post your questions on The C2000 Forum. Please post only comments about the article GSG: AM35x and OMAP35x Graphics SDK Additional Procedures here. DaVinci=For technical support on DaVincoplease post your questions on The DaVinci Forum. Please post only comments about the article GSG: AM35x and OMAP35x Graphics SDK Additional Procedures here. MSP430=For technical support on MSP430 please post your questions on The MSP430 Forum. Please post only comments about the article GSG: AM35x and OMAP35x Graphics SDK Additional Procedures here. OMAP35x=For technical support on OMAP please post your questions on The OMAP Forum. Please post only comments about the article GSG: AM35x and OMAP35x Graphics SDK Additional Procedures here. OMAPL1=For technical support on OMAP please post your questions on The OMAP Forum. Please post only comments about the article GSG: AM35x and OMAP35x Graphics SDK Additional Procedures here. MAVRK=For technical support on MAVRK please post your questions on The MAVRK Toolbox Forum. Please post only comments about the article GSG: AM35x and OMAP35x Graphics SDK Additional Procedures here. For technical support please post your questions at http://e2e.ti.com. Please post only comments about the article GSG: AM35x and OMAP35x Graphics SDK Additional Procedures 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