OMAP35x DVSDK 3 00 01 to DVSDK 3 00 02 Migration Guide

From Texas Instruments Embedded Processors Wiki

Jump to: navigation, search

Translate this page to

Introduction

This topic walks you through component-level modifications in the DVSDK v3.00.02 release from DVSDK v3.00.01 and serves as an aid for migrating existing applications.

Platform Support Package

Version

PSP has migrated from OMAP35x Linux PSP GIT v2.01.02 (Linux kernel version 2.6.29-rc3)to OMAP35x Linux PSP GIT v2.01.03 (Linux kernel version 2.6.29-rc3). For installation please refer Installing the Target Linux Software in GSG.

Kernel Interface Compatibility

There is no interface level impact on the applications using the kernel system APIs as well as driver IOCTLs, that were built with PSP v2.01.02.

User Libraries Interface Compatibility

The prebuilt target file systems (nfs, ramdisk, and jffs2) are based on Arago SDK filesystem v2009.09-rc4. The versions of the cross compiled user libraries packaged in this file system are different and hence interfacing could have changed. There is no impact of this in case of use from DVSDK demos but it may not be case for any other applications built on the top of the previous PSP releases.

UBOOT and X-Loader

It is preferred to update the u-boot and x-loader. Please refer OMAP35x Linux PSP GIT v2.01.03.11/docs/UserGuide-02.01.03.11.pdf for re-flashing the x-loader as well as u-boot. (For re-flashing x-loader Refer Section 2.4.Flashing x-loader and for flashing u-boot refer Section 3.2.Flashing U-Boot.)

Setting the MPU Rate from bootargs

Support for changing the MPU frequency is added in PSP SDK v2.01.03. Refer bootargs options here

Other Changes

For more information on the changes with respect to the OMAP35x Linux PSP GIT v2.01.03 releases. refer PSP migration guide present in OMAP35x Linux PSP GIT v2.01.03.11/docs/MigrationGuide-02.01.03.11.pdf

Codec Server Related Changes

Clock Value Change

The DSP clock value in the codec server configuration file has been modified to 430 MHz instead of 360 MHz used in the previous releases.The server configuration file has been modified as given below.

var params = {
        clockRate: 360,
        catalogName: "ti.catalog.c6000",
        deviceName: "3530",
        regs: device_regs,
        mem: mem_ext
    };

has been modified to

var params = {
        clockRate: 430,
        catalogName: "ti.catalog.c6000",
        deviceName: "3530",
        regs: device_regs,
        mem: mem_ext
    };

Changes to Bootargs

The bootargs have been modified as below:

NOTE: The below commands should be entered as a single line.

For Ramdisk:

setenv bootargs 'mem=99M console=ttyS0,115200n8 root=/dev/ram0 initrd=0x81600000,16M ramdisk_size=40960 mpurate=600 omapfb.rotate=1
                 omapfb.rotate_type=1 omap_vout.vid1_static_vrfb_alloc=y'

For JFFS filesystem:

setenv bootargs 'mem=99M console=ttyS0,115200n8 noinitrd root=/dev/mtdblock4 rw rootfstype=jffs2 mpurate=600 omapfb.rotate=1 
                 omapfb.rotate_type=1 omap_vout.vid1_static_vrfb_alloc=y'

For NFS Filesystem

setenv bootargs 'mem=99M console=ttyS0,115200n8 noinitrd ip=dhcp rw root=/dev/nfs
                 nfsroot=<nfsserver_ip>:/home/<useracct>/workdir/filesys,nolock mpurate=600 omapfb.rotate=1 
                 omapfb.rotate_type=1 omap_vout.vid1_static_vrfb_alloc=y'

Version differences

See the OMAP35x DVSDK Version Log for details on component version changes throughout the development cycle of the DVSDK.

Note: All components are modified to work with the OMAP35x Linux PSP GIT v2.01.02(Linux kernel version 2.6.29-rc3)

For technical support on OMAP please post your questions on The OMAP Forum. Please post only comments about the article OMAP35x DVSDK 3 00 01 to DVSDK 3 00 02 Migration Guide here.