OMAP35x DVSDK Build v3.01.00.03 Known Issues and Limitations

^ Up to main OMAP35x DVSDK Known Issues and Limitations Table of Contents

This page lists issues and limitations that are known to exist in the OMAP35x DVSDK software for build v3.01.00.03.

Known Issues

1. SDOCM00065773 : In order to enable run time switch from LCD to DVI, it is required to specify "omapfb.mode=dvi:720x480MR-16@60" in the bootargs. If the default display is LCD with the above setting in the bootargs the frame buffer does not allocate memory equivalent to 720x480x(colorformat_bytesperpixel). It allocates only 720x438x(colorformat_bytesperpixel)
2. SDOCM00065771 : Keypad entries changed from previous version. The S7 and S13 keys have been swapped. This affects the behavior of the key presses in the DVSDK demos.
3. SDOCM00065749 : OMAP3530: udev error messages are thrown during boot sometimes
4. SDOCM00041241 : SVIDEO: Video quality issue on TV With SVIDEO interface
5. SDOCM00041259 : DVTB: Control-C causes stack-trace to be dumped on to terminal in case of DVTB decode.
6. SDOCM00050734 : While using DVTB application for video playback, video stream display becomes faster at the end of the stream
7. SDOCM00056814 : Video decode demo hangs in stress: Behaviour observed in ES2.1 EVM The video decode demo fails (hangs) in stress after runninng 1055 iterations with error message "Error: Failed to create loader thead" for OMAP EVM 2.1. The same behaviour is not observed in OMPA EVM 3.1(with memory hole configuration) even after running 2850 iterations
8. SDOCM00056890 : Video/Image decode uisng DVTB application fails in stress: Behaviour observed in ES2.1 EVM The DVTB video decode and display fails in stress for OMPA EVM 2.1 after some 1150 itaration. It throws the error message "Thread_create: Cannot allocate memory" and "Segmentation fault". The same behaviour is not observed in OMPA EVM 3.1(with memory hole configuration) even after running 3000 iterations
9. SDOCM00057149 : SDMA performance is not enough to perform framecopies of VGA video @30FPS
10. SDOCM00057184 : OSD flicker observed when switching between decode demo and third party demo menu buttons in main menu screen
11. SDOCM00051616 : CE examples cause TLB error with default DVSDK demo loadmodules.sh
12. SDOCM00053887 : Specific stream issue: Issue with playing Video (Mpeg2) and Audio (Mp3) together. When streams from the container are extracted and use these as elementary streams with both Decode Demo and DVTB and if video and audio are played out, then the audio thread will not exit in both the cases
13. SDOCM00056334 : Static IP is getting overwritten by DHCP call in initialization script for NFS. This is a known issue. If static IP needs to be used, then the initialization script needs to be modified to comment the dhcp server initiation.
14. SDOCM00057319 : A mild click is heard at the end of the audio playback.
15. SDOCM00055964 : A mild beep is heard at the beginning of audio playback.
16. SDOCM00059851 : Video decode demo:OMAP3530:Demo hangs the target if control-c is pressed, board needs to be reset
17. SDOCM00060835 : System won't boot if mem= kernel option is not specified.
18. SDOCM00052712 : DVTB does not remove spurious data from the non standard MP3 streams.DVTB does not remove remove these bytes and gives it to codec for processing. It can cause codec to fail with extended error.
19. SDOCM00056242 : MMC Detection: OMAP fails to detect 8-bit MMC cards.
20. SDOCM00057547 : Decode demo throws the warning message about clock recieved during first run with DVI interface.
21. SDOCM00060903 : System hangs when playing an AVI clip from an SD card using GStreamer. This is observerd on ES2.1 EVM and not on ES3.1 EVM. Errors reported on the console such as "mmcblk0: retrying using single block read". This is due to a silicon defect in ES2.1 which was subsequently fixed in OMPA3 silicon version ES3.1
22. SDOCM00062098 : Mem copies in CMEM space takes 10x more than memory copies of Os allocated memory.Performing a memory copy of a CMEM allocated buffer takes 10 times more than a memory copy of malloc'ed pointers. While a 2MB copy in CMEM space takes 220ms, it's OS allocated buffer counterpart takes only 25ms.

Limitations

1. OMAP3530: (Interface Demo) GUI interface keyboard showing incorrect Active/Passive mode of keys.
2. OMAP3530: Encoder support D1-NTSC and D1-PAL resolution. It should support other also.
3. OMAP3530: For encode demo, when no input is connected, the error message is not user friendly.
4. The maximum sample rate supported by the ALSA Audio driver included in the PSP release is 48KHz.
5. DSP Link kernel object is not re-built in the top level makefile.
6. Maximum of 16M memory can only be provided for double buffering when rotation is enabled.
7. The Audio Capture for Speech encode is not set by default,we can set this value using the amixer utility.Steps for enabling Audio Capture for Speech encode are mentioned in the OMAP35x DVEVM Getting Started Guide
8. The path for audio capture for speech encode is not set by default in the ALSA driver. Use the amixer utility for checking the audio capture. This utility enables the required path in the ALSA driver for audio capture.
9. SDMA performance is not enough to perform framecopies of VGA video @30FPS. There is no burst mode support in the SDMA copy APIs in the SCPY interface provided by framework components
10. PumpKIN server included in \OMAP35x-PSP-SDK-#_##_##_##\host-tools\windows has reported hang while transfering data.It is recommened to use other tftp utilitied like tftpd32.
11. The Mpeg4 encode and H264 Decode combinations fails.This is due to the codec server as per DDRALGHEAP#What_are_the_limitations_of_the_OMAP35x_Codec_Server.3F. The DDRALGHEAP needs to be increased.
12. In NAND Filesystem(JFFS2 Filesystem) the video stops after 40-50 seconds while audio plays on.Once audio has finished both the drivers close and restart.Reason why you see this is since the streams present in JFFS2 truncated so that the size of the file could be adjusted to fit jffs2 without disturbing the quality. These streams are of 40-50 seconds duration only. The original streams size(present in NFS filesystem) were about 76MB per steam so we could not package it in JFFS2.

Defects Fixed

1. SDOCM00027745 : H264 OMAP3530 not returning proper error code when it receives unsupported content
2. SDOCM00034484 : Documentation errors
3. SDOCM00034490 : <Video Capture> Cropping and scaling operations and their correspoing V4L2 IOCTLs
4. SDOCM00036527 : Wrong error codes are returned from the Codec
5. SDOCM00057794 : OMAP3530: <4>Spurious irq 95: 0xffffffdf, please flush posted write for irq 26
6. SDOCM00060864 : Ghostly negative-like rotated images appear on the DVI screen when playing something in the internal LCD
7. SDOCM00061024 : OMAP3530: Needs update in Graphics SDK getting started Guide
8. SDOCM00061073 : OMAP3530:Graphics SDK :Not able to load the kernel modules after following the steps mentioned in GSG
9. SDOCM00061129 : OMAP3530:Graphics SDK: Demos hang on 2.1 EVM
10. SDOCM00061519 : x-loader and u-boot tar version file name has mismatch with extracted folder.
11. SDOCM00062264 : OMAP - Manifest in DVSDK docs folder has incorrect URL
12. SDOCM00062540 : OMAP3530: Video decode demo play out sometimes throws error messages
13. SDOCM00063073 : decode.txt: Does not mention copyright year
14. SDOCM00064575 : Audio capture gives overrun error, when running in background, with suspend/resume
15. SDOCM00065473 : OMAP35x:Resizer: highlight document for Memory to Memory Resizer: buffer size alignment
16. SDOCM00065738 : OMAP3530:Some help message for Encode demo is not proper.
17. SDOCM00065739 : OMAP3530: Initial few frames (3-5) of encoded content are not proper.
18. SDOCM00065741 : OMAP3530: The statistics are not correct for NTSC encode.
19. SDOCM00065745 : OMAP3530: Encode command line option for time, accepts any character not just numeric value.
20. SDOCM00065748 : OMAP3530: Encode demo preview start with flicker using OOBE interface.
21. SDOCM00065751 : OMAP3530: Encode.txt change log refers to DM355 and DM6446 instead of OMAP3530
22. SDOCM00065752 : OMAP3530: For encode demo, when no input is connected, the error message is not user friendly.
23. SDOCM00065767 : OMAP3530:Encode Demo:Encode demo exits when display is switched from LCD to DVI while OSD is enabled
24. SDOCM00065828 : OMAP3530:Overlays: OOBE demos fail to comeup if rebuilt nfs/jffs2 image is used as rootfs
25. SDOCM00065831 : OMAP3530: OOBE encode demo OSD shows file size overwriting name of encoder
26. SDOCM00065985 : OMAP3530: Video decode demo ends with flicker
27. SDOCM00065986 : OMAP3530: Decode + display hangs after first few frames with video decode demo. (Observed for specific streams)
28. SDOCM00066001 : OMAP3530: Docs folder is not present for dmai_2_05_00_02 component
29. SDOCM00066005 : OMAP3530:OOBE Demos: Streams encoded with OOBE Interface does not appear in OOBE decode demo menu
30. SDOCM00066039 : OMAP3530:Video encode demo: Encode demo does not support PAL input
31. SDOCM00066057 : OMAP3530: OOBE interface Video decode demo shows Video resolution as N/A.
32. SDOCM00066061 : OMAP3530: OOBE Interface encode demo: In standalone mode encode, preview is flickering and content has frame drops
33. SDOCM00066257 : OMAP3530: (Encode demo application) Left side black strip is observed while decoding (Tektronix MTS4EA) the encoded stream.

See Also

• OMAP35x_DVSDK_Build_v3.00.00.40_Known_Issues_and_Limitations
• OMAP35x_DVSDK_Build_v3.00.01.42_Known_Issues_and_Limitations
• OMAP35x_DVSDK_Build_v3.00.02.44_Known_Issues_and_Limitations