OMAP35x DVSDK Power Benchmarks PSPGIT03000003
From Texas Instruments Embedded Processors Wiki
Contents |
Power Benchmark Numbers on OMAP35x DVEVM
Scenario-Power Matrix
SID = Scenario ID
Scenarion Description
Environment Setup
Hardware details
1. OMAP3x EVM, ES3.1 Rev G board, ARM clocked at 125MHz and DSP clocked at 90MHz
2. National Instruments DAQPad with shunt for power measurment, details NI DAQPad-6015
3. Speakers
Software details
1. Linux Operating System, PSP version - 03.00.00.03
2. Third Party Tools such as arm-2009q1 toolchain
3. DVSDK, version 03.01.00.03
Power Measurement
Power Measurement Setup
This section provides the details of the OMAP35x power measurement setup. The instrument used for measuring the power of OMAP35x is National Instruments DAQPad-6015 with manual shunt for calibration.
Hardware Setup
The system consists of:
1. One National Instruments 6036E PCI Data Acquisition Card (16 bit A/D for PCI) or National Instruments DAQPad-6015 (16 bit A/D for USB)
2. One external Shunt assembly for sensing the current.
Shunt connection procedure to OMAP3x.
- a. Ground pin of the Shunt is connected to the ground pin of OMAP3x
- b. Shunt has two calibration circuits one with 0.5ohm capable and other is 0.1ohm. Connect one of the terminals to OMAP3x jumper J6 for VDD1 power measurement.
- c. Connect the same terminals to OMAP3x jumper J5 for VDD2 power measurement.
Software Setup
1. Install the NI software along with DAQPad-6015 product
2. Install TI Power consumption – Measurement and Analysis Tool (PC-MAT)
Measurement
Steps for running the Low power DVSDK demos
1. Boot the board with minimum kernel configured uImage by using these boot arguments
- a. Boot arguments for NFS file system:
- setenv netmask <<Net Mask>>
- setenv ipaddr <<NFS server running IP>>
- setenv serverip <<Host Machine IP>>
- setenv gatewayip <<Gateway IP>>
- setenv bootfile uImage
- setenv bootcmd ‘tftp 0x80000000 uImage;bootm’
- setenv bootargs ‘mem=100M@0x80000000 mem=128M@0x88000000 console=ttyS0,115200n8 noinitrd ip=dhcp rw root=/dev/nfs nfsroot=172.24.190.141:/home1/anil/workdir/filesys/power,nolock mpurate=125
- b. Boot arguments for RAMDISK:
- setenv netmask <<Net Mask>>
- setenv ipaddr <<NFS server running IP>>
- setenv serverip <<Host Machine IP>>
- setenv gatewayip <<Gateway IP>>
- setenv bootfile uImage
- setenv bootcmd 'tftp 0x80000000 uImage;tftp 0x81600000 ramdisk.gz;bootm 80000000'
- setenv bootargs mem=100M@0x80000000 mem=128M@0x88000000 console=ttyS0,115200n8 root=/dev/ram0 initrd=0x81600000,36M ramdisk_size=36864 mpurate=125'
- c. Boot arguments for JFFS2:
- setenv netmask <<Net Mask>>
- setenv ipaddr <<NFS server running IP>>
- setenv serverip <<Host Machine IP>>
- setenv gatewayip <<Gateway IP>>
- setenv bootfile uImage
- setenv bootcmd ‘tftp 0x80000000 uImage;bootm’
- setenv bootargs ‘mem=100M@0x80000000 mem=128M@0x88000000 console=ttyS0,115200n8 noinitrd root=/dev/mtdblock4 rw rootfstype=jffs2 mpurate=125’
2. Enable these modules in kernel configuration for CPU idle framework
- a. Enable Power Management Debug Support
- b. CPU idle PM support
3. Run these commands after bootup for enabling CPU idle framework
- a. mkdir /dfs
- b. mount -t debugfs debugfs /dfs
- c. echo 1 > /dfs/pm_debug/sleep_while_idle
4. Run these commands after bootup for enabling Smart Reflex framework
- a. echo 1 > /sys/power/sr_vdd1_autocomp (during VDD1 power measurement)
- b. echo 1 > /sys/power/sr_vdd2_autocomp (during VDD2 power measurement)
5. Run the application
- a. cd /opt/power/omap3530
- b. ./loadmodules.sh (which will initialize dsplink, cmem, sdma and lpm)
- c. ./decode -a data/sounds/davincieffect_LC.aac
Note: For direct execution run pwr_optimal_setting_audio.sh script
6. Run PC-MAT.exe from your host machine then PC-MAT GUI will display the power values
| For technical support on OMAP please post your questions on The OMAP Forum. Please post only comments about the article OMAP35x DVSDK Power Benchmarks PSPGIT03000003 here. |
