video decode demo not working

Could you post the boot arguments you are using in U-Boot? Often a failure like this could be rooted in how the kernel was booted.

I have not seen this error myself but for an allocation failuire it may be worth checking RAM memory space, do you have plenty of free RAM when using a command like top or free?

HI Thompson,

Thanks for responding. The following is the bootargs parameter

setenv bootargs_rd mem=88M console=ttyS0,115200n8 root=/dev/ram0 initrd=0x81600000,40M ramdisk_size=40960 video=omap24xxfb:rotation=90

the following arguments are showing while giving to and free command

[root@OMAP3EVM /]# top

PID  PPID USER     STAT   VSZ %MEM %CPU COMMAND
  321   319 root     R     3156   4%   0% top
  319     1 root     S     3156   4%   0% -/bin/sh
    1     0 root     S     3152   4%   0% init
  316     1 root     S     3152   4%   0% /sbin/syslogd
  318     1 root     S     3152   4%   0% /usr/sbin/telnetd
  268     2 root     SW<      0   0%   0% [kmmcd]
    2     0 root     SW<      0   0%   0% [kthreadd]
    3     2 root     SWN      0   0%   0% [ksoftirqd/0]
    4     2 root     SW<      0   0%   0% [watchdog/0]
    5     2 root     SW<      0   0%   0% [events/0]
    6     2 root     SW<      0   0%   0% [khelper]
   57     2 root     SW<      0   0%   0% [kblockd/0]
   63     2 root     SW       0   0%   0% [twl4030-irq]
   64     2 root     SW       0   0%   0% [twl4030-gpio]
   65     2 root     SW<      0   0%   0% [omap2_mcspi/0]
   72     2 root     SW<      0   0%   0% [ksuspend_usbd]
   75     2 root     SW<      0   0%   0% [khubd]
  100     2 root     SW       0   0%   0% [pdflush]
  101     2 root     SW       0   0%   0% [pdflush]
  102     2 root     SW<      0   0%   0% [kswapd0]


[root@OMAP3EVM /]# free
              total         used         free       shared      buffers
  Mem:        85232        42652        42580            0         8192
 Swap:            0            0            0
Total:        85232        42652        42580

The following shows the memory on board

[root@OMAP3EVM /]# df -h
Filesystem                Size      Used Available Use% Mounted on
rootfs                    7.7M      4.0M      3.3M  55% /
/dev/root                 7.7M      4.0M      3.3M  55% /
mdev                     41.6M         0     41.6M   0% /dev
none                     41.6M         0     41.6M   0% /tmp


How to check the RAM memory available on OMAP board?Why the video demos are not working? where am I going wrong? How to make it work? Why the OMAP default images as well as filesystem was write-enable and how to revert it back. The earlier memory on OMAP board before flashing new images were as follows:-

[root@OMAP3EVM/]# df -h
Filesystem                Size      Used Available Use% Mounted on
rootfs                  120.5M     20.7M     99.8M  17% /
/dev/root               120.5M     20.7M     99.8M  17% /
mdev                     61.5M         0     61.5M   0% /dev
none                     61.5M         0     61.5M   0% /tmp

Regards,

Vineet

Hi Thompson,

We had recompiled the kernel and enabled video(.ko) files as a module and now decode and encode application is working but it is failed to create display

[root@OMAP3EVM decode]# ./decode -v /mnt/data/videos/davincieffect_ntsc_1.264
Decode demo started.
Error: Failed to create display device
[root@OMAP3EVM decode]#

Now I am able to decode and encode the files but not able to display on LCD. Is there any fix for the display video to LCD or do I need to enable some driver while compiling the kernel? How to play the .yuv files and .264 files to LCD? However ./interface -l 0 is working and displaying buttons on LCD screen.

Regards,

Vineet

The free command shows how much RAM you have available and it appears you have plenty.

I setup the DVSDK version you are using and the video worked in my case, though I am setup to do a TFTP kernel with NFS filesystem. As a debugging step if you have not already could you try setting up your board to boot your kernel and filesystem over NFS as discussed in the getting started guide? This should narrow down where the problem is, if it is something specific to your ramdisk flash boot or if there is overall something wrong with your software install or board.

The failure to create display device is a somewhat generic error, it means for some reason the demo could not access the display driver, which could stem from the driver not being instantiated to the driver not supporting the mode the decode demo is asking for, or some other driver level failure. The fact that the OSD shows up properly when you run interface is a good sign though, that should prove the display driver is at least in place.